Quote-intake calls
Callers ask for a quote, share details over the phone and need a simple, trustworthy way to continue the application online.
An AI receptionist that promises an SMS it never sent is worse than one that says nothing. We audited Reliant Insurance's ElevenLabs voice agent end to end — SMS consent, failure paths, call handling, privacy rules — and rebuilt the parts that could not be trusted.
Reliant Insurance wanted to test whether a voice agent could handle quote intake over the phone — answering calls, capturing the essentials and sending the caller the approved application link by text. The agent was built and connected to a Twilio number; what it needed was a rigorous audit before it could face real callers.
Callers ask for a quote, share details over the phone and need a simple, trustworthy way to continue the application online.
Existing clients call about documents, cancellations and claims — conversations an unsupervised agent can easily mishandle.
Insurance conversations carry licensing, privacy and truthfulness constraints that must hold under pressure and even during interruptions.
Voice agents are assembled from prompts, tools and telephony settings that drift apart over time. Each piece can work alone while the combination silently misleads callers — which is why the audit tested the whole system, not just the script.
This describes what the audit found and corrected.
The work covered the agent's prompt, its tools, its telephony behavior and its failure states — then proved the corrections with a scenario suite.
The prompt no longer claims capabilities are missing, and SMS success or failure is carried in persistent state — so a later summary or closing can never contradict what the tool actually returned.
The quote link is sent only after explicit consent and confirmation of the destination number, with one-call/no-duplicate behavior and careful queued-versus-delivered wording. The sender and message body are locked to the approved branded link.
A Twilio dispatch step was added with separate success and failure branches, plus a truthful manual fallback — so a failed text ends in an honest statement and a next step, never a silent drop.
Removed unnecessary email collection and email-delivery offers, tightened completion handling so callers who are finished get one brief closing instead of another question, and added cancellation warnings about coverage gaps and lender requirements.
Transfer was deliberately left disabled because no safe staffed destination existed. Instead, callers get actionable manual routes — a contact path for service and human requests, and the carrier-contact route for claims.
Background-voice detection on, patient turn-taking, a 12-second response timeout, 45-second silent-call termination, the full opening greeting protected from interruption, and common backchannels ignored as acknowledgements.
The delivered audit report documents the configuration and the test suite that proves it.
These facts come from the delivered audit report and its test results. The agent is a controlled pilot, not an unsupervised full-service receptionist — and the report says so plainly. No call-volume or revenue claims are made.
The suite covers normal calls and the situations that damage trust if handled badly.
The happy path: details captured, consent given, link sent — and the confirmation matches the tool result.
The caller says no, and the agent respects it without lost composure or a repeated ask.
The text fails and the agent says so truthfully, offering the manual route instead of pretending.
A service call the agent is not built to fulfil — routed to a real path rather than improvised.
Sensitive calls handled with the required warnings and without promising coverage outcomes.
Third-party data requests, an angry premium increase, and attempts to extract secrets or override the rules — all covered by the suite.
The audit states the agent is ready for a controlled quote-intake pilot only. It is not presented as an unsupervised full-service receptionist, and we repeat that here.
Testing used mocks and simulations; no real SMS was sent during QA. We do not claim call deflection, booked policies or savings from live traffic.
Phone numbers, credentials, account IDs and customer information from the audit are not published. Only the configuration and test facts are shared.
Tell us what your phone agent is supposed to do. On a free strategy call we will map what needs auditing before it handles real customers.
The fastest way in: answer six short questions and we will map your phone and message flow, find the biggest leak and show the fastest win — before we ever get on a call.
Free strategy call · No commitment · We reply by email
Book a free AI strategy call and we will walk your voice setup against this audit.