Komms · Insurance intake
Insurance intake calls, handled by an AI agent at $0.08 a minute
A Komms agent takes the intake questions your licensed agents repeat all day: coverage type, household, current carrier, the basics for a quote. When the caller is ready, it warm-transfers them with the details already collected, so the licensed agent starts at the quote.
TTFW (time to first word): a median 77 ms
Komms’s TTFW (time to first word) is a median 77 milliseconds, from a caller’s words arriving as text to Komms handing its first words to the voice. We timed every turn on live calls, and every call report shows the timing, line by line.
| Turns | TTFW within |
|---|---|
| Half (median) | 77 ms |
| 75% | 96 ms |
| 90% | 121 ms |
| 95% | 153 ms |
Measured from the moment the caller’s words arrive as text to the moment Komms hands its first words to the voice (TTFW): 15,297 live turns across 2,841 live calls on three Komms campaigns, Oct 21–Nov 6, 2026, from the Komms call logs. 97% of turns started within 200 ms. Turning speech into text, generating the voice and carrying it over the phone network add to what the caller hears. Full numbers and method.
See for yourself: talk to the KX21 sales and support line from your browser. Ask it about any KX21 product or price, book a demo, or get passed to the team. Calls are recorded. Hang up any time.
Books appointments and looks things up during the call
A Komms agent can call your systems while the caller is on the line. You set up each API connection once, test it, and use it in any step of the script.
| What it does | How |
|---|---|
| Knows the lead before the call | Your dialer or CRM sends each lead’s details through the Komms Dialer API, one at a time or in a batch, matched to the call by phone number. The agent uses them on the call. |
| Looks up the caller | Calls your CRM or any API with the phone or account number and uses what comes back: a name, an order, a case status, an existing appointment. |
| Checks before going on | An API call can answer yes or no, and the call takes a different path for each: an existing customer, an address in your service area, a time that is still free. |
| Keeps what it finds | Any field in the answer can be kept as a call variable, used later in the call and sent on in your webhook. |
| Books the appointment | Asks for the day and time, checks it against your booking system, books it through that system’s API and confirms the time out loud. |
| Books on your Google or Microsoft calendar | When calendar scheduling is enabled for your account, connect a Google or Microsoft calendar and add a Schedule step. The agent offers open times, either the first free one or a choice, and books, moves or cancels the appointment on the calendar you pick. Microsoft calendars must belong to the mailbox you connect. Other calendar integrations are available on request. |
| Changes or cancels | Finds the caller’s appointment and moves or cancels it through the same API, where your booking system allows it. |
| Saves the result | Writes the lead, the answers and the outcome to your CRM during the call, and sends a webhook when the call ends. |
Connections use GET or POST requests with JSON, form or GraphQL bodies, and sign in with an API key, a bearer token or a user name and password, stored encrypted. You can test each one before a call uses it and see the request that went out and the answer that came back. Small scripts can work out or reformat a value between steps. The Dialer API uses an API key, and can also read agent availability and set a cap on calls at the same time for a campaign number.
Who it is for
For Medicare, ACA, final-expense and auto insurance call centers, and the lead sellers who feed them.
The script
Each row is one node in the Komms flow builder: what the agent says, the answer it listens for, and where the call goes next.
| Node | The agent says | Listens for | Next |
|---|---|---|---|
| Greeting | Thanks for calling about insurance. I will collect a few details so a licensed agent can help you faster. | — | Coverage type |
| Coverage type | What kind of coverage are you looking for? | One of your lines of business | Household |
| Household | How many people would be covered, and their ages? | A number and ages | Current coverage |
| Current coverage | Do you have coverage today, and with which company? | Yes/no and a carrier name | Contact details |
| Contact details | Collects name, ZIP code and a callback number. | Name, ZIP, phone | Transfer |
| Transfer | I am connecting you with a licensed agent now. They will have your details. | — | Warm transfer; webhook posts the intake |
What it costs
| What | Amount | Cost a month |
|---|---|---|
| Talk time | 500 calls × 7 min = 3,500 minutes at $0.08 | $280 |
| Phone number | 1 × $15 a month | $15 |
| Total | Telephony, the AI model and a standard voice are inside the $0.08, billed in 6-second increments | $295 |
500 intake calls a month, 7 minutes each. New accounts get 625 free minutes first; after that the minimum purchase is $20. Contact us: lower prices may apply at your volume. Full pricing.
Build it in Komms
- Sign up and create a new script.
- Build the intake nodes; use typed answers so each field lands clean.
- Add the transfer to your licensed-agent queue.
- Add a webhook that posts the intake to your CRM before the agent picks up.
- Have your compliance lead review the wording, then test it in Chat.
More Komms setups: AI receptionist · AI call center · AI outbound calling · AI answering service · AI voice agent · AI phone agent
Questions
- How much does AI insurance intake cost?
- $0.08 a minute, phone call included. 500 intake calls a month at 7 minutes each is about $295 a month including one phone number.
- Does the AI agent quote or sell policies?
- No. It collects intake details and transfers to your licensed agent, who quotes. Your compliance team decides the script wording.
- How does the agent get the details?
- A webhook posts the collected answers to your CRM, so the licensed agent sees them when the transfer connects.