Komms · Lead qualification
Qualify every inbound call before a rep picks up
Komms reduces talk time 30–40% vs. your agents on the same script.
- $0.08 a minute, phone call included
- $15/mo per phone number
A Komms agent asks your qualifying questions, records each answer as a typed value (not a transcript someone has to read), routes by the answers, and warm-transfers the qualified caller to a rep or buyer. Unqualified calls end politely without costing a rep’s time.
Starts answering in a typical 162 ms
When a caller stops talking, Komms starts its reply in a median 162 milliseconds. We timed every turn on our live demo line, and every call report shows the timing, line by line.
| Turns | Reply within |
|---|---|
| Half (median) | 162 ms |
| 75% | 181 ms |
| 90% | 211 ms |
| 95% | 283 ms |
Measured from the moment the caller finishes speaking to the moment our reply starts and goes to the voice: 1,048 live turns across 502 calls on the Komms demo line, Oct 6–7, 2026, from the Komms call logs. 86.5% of turns started within 200 ms. Generating the voice and carrying it over the phone network add to what the caller hears.
See for yourself: +1 (618) 228-1183. It is a live Social Security disability (SSDI) intake line: it asks real screening questions and 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 pay-per-call publishers, insurance and legal intake teams, and any call center that pays reps to sit through unqualified calls.
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. I will ask a few quick questions to get you to the right person. | — | Question 1 |
| Question 1 | The first hard filter (for example: are you currently insured?). | Yes or no | Question 2, or Disqualify |
| Question 2 | The second filter (for example: what state do you live in?). | One of your allowed states | Question 3, or Disqualify |
| Question 3 | The value question (for example: how many people in the household?). | A number | Transfer |
| Transfer | Great, I am connecting you with a specialist now. | — | Warm transfer to the rep or buyer line |
| Disqualify | Explains they are not a match and thanks them. | — | End; webhook marks the lead unqualified |
What it costs
| What | Amount | Cost a month |
|---|---|---|
| Talk time | 1,000 calls × 3 min = 3,000 minutes at $0.08 | $240 |
| 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 | $255 |
1,000 inbound calls a month, 3 minutes each. New accounts get 50,000 free tokens first (about 625 minutes); 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.
- Make each question a node with a typed answer (yes/no, a list of values, a number).
- Route each answer to the next node or to Disqualify.
- Add the transfer node with your rep or buyer number; add a webhook so every outcome reaches your system.
- Test it in Chat, then point your tracking number at it.
Questions
- What does AI lead qualification cost per call?
- Komms is $0.08 a minute, phone call included. A 3-minute qualifying call costs about $0.24. 1,000 calls a month is about $255 including one phone number.
- Why typed answers instead of a transcript?
- Each node listens for a specific kind of answer, so routing and reporting use clean values (yes/no, a state, a number) instead of free text someone has to read.
- Can it transfer to my buyer or rep?
- Yes. A transfer node warm-transfers the caller to any number, so qualified calls reach a person and unqualified ones end without using a rep.