Quote, serve, and save — every call, every hour

Common questions from Insurance operators

More general questions are answered on the full FAQ page.

What can the AI actually do on a Sunday night when my office is closed?#

It answers in your branded greeting, captures the request, and either handles it directly or texts you depending on what you've authorized. Standard self-serve items — sending dec pages, emailing ID cards, taking billing questions, accepting COI requests, capturing add/remove vehicle or driver requests, updating mailing addresses — get logged and queued for your next business morning, with the client texted a confirmation. Quote intakes get a same-evening text with your quote form link. Claims and "I want to cancel" calls escalate to you in real time.

I'm appointed with a dozen carriers — each has its own claims number. Can the AI handle that?#

Yes. During onboarding you load your carrier list with each carrier's claims phone number. When a client calls for a claim, the AI asks which carrier the policy is with, confirms, and either reads the number out + texts it, or warm-transfers to the carrier's claims line directly — your choice per carrier. If the client uses an emergency trigger word you've defined (fire, injury, total loss, etc.), it skips that flow and dials you or the carrier's emergency line first.

Can the AI bind a policy, or just take the lead?#

It captures the lead and pushes it into your quote form (we support any URL-based form — your AMS quote intake, EZLynx, a Google Form, whatever). It does not bind policies — binding requires producer judgment, underwriting, and your e-sig flow, which is your job. The AI's job is making sure a real human-quality intake lands in your inbox at 6am Monday from a call that came in at 11pm Saturday.

Does it integrate with my agency management system — EZLynx, Vertafore, AMS360, HawkSoft, QQCatalyst?#

Lead and servicing-request data lands in the portal immediately and can be pushed to your AMS via the platform integration we build per customer. EZLynx and Vertafore are the most-requested today and quoted as a separate setup project — they're real engineering work, not a checkbox. If you're on HawkSoft, AMS360, or QQCatalyst, we'll scope it during the demo. If you don't want an integration, the daily digest email + portal export covers it.

What happens when a client says they want to cancel?#

By default, the AI immediately texts and calls you so you can attempt a save while the client is still on the line — most agents tell us they save 30-50% of cancellation calls that reach a producer in time. You can change the trigger words (cancel, switch, shopping, GEICO, Progressive, anything else), change the escalation channel (text-only, call-only, or both), or have the AI itself attempt a soft retention pitch first if you'd rather. Whatever you pick, it's logged so you can review and tune.

Most of my book is bilingual. Does this work in Spanish?#

Yes — English and Spanish are both standard. The AI detects the language from the caller's first words and continues in whichever they chose, including reading dec page details, ID card content, and carrier claims numbers in Spanish. The same flow is available for any other language during onboarding (Vietnamese, Tagalog, Portuguese, etc.) — each additional language is a small add-on for the prompt engineering and QA.

What about call recording, state licensing, and TCPA compliance?#

Every call gets a recording-disclosure played at the start (configurable per state to match two-party-consent rules in California, Florida, etc.). Recordings are stored for the standard 7-year insurance retention by default and are exportable. The AI is configured with your licensed states so it won't promise quotes outside your appointed footprint — it tells the caller you're not licensed there and offers to take a referral. TCPA SMS consent is captured before any outbound text. If your state DOI has specific disclaimers required, we add them to the opening greeting.