Three Quick Answers To A Real Price

This is the text flow from last open enrollment, with ZIP added up front and our quote tool doing the price. respond.io isn't connected and nothing here changes it. What you type goes to the live quote service to get a price, so use made-up details.

3answers before a price, plus county or spouse when needed

5,159new leads studied, Oct 1, 2025 to Jan 31, 2026

56.5%of the 731 people who got the price text booked, per the CRM

86.4%of 206 CRM-sold new leads also match by name on the sales sheet

Play The Lead

Type your own answers, or run one of these made-up leads.

TrueCost Health Insurance

What respond.io Would Do

Each step is a normal workflow step. The blue one is running now.

1
Ask a question: ZIPSaves the answer to a variable.
2
HTTP Request: check the ZIPFinds the county. Asks which one if there's more than one.
3
Ask a question: ages, then incomeOne question per text. Ages first, income second.
4
Ask a question: household sizePlus spouse, only when two adults need coverage.
5
HTTP Request: get the quoteCalls the quote tool, returns a few flat fields.
6
Send message: the priceSends the text the endpoint wrote.
7
Ask: today or tomorrowThen morning or afternoon.
8
Assign to a personThe setter books it. The mock stops here.

Last Tool Call

TimeNo call yet. Limit is 10 seconds.

Fields returnedLimit is 10.

What Last Year's Texts Showed

Each exact staff text, in the order it went out, and what happened to the new leads who got it before booking. 36.5% ever replied before booking. Booked and sold come from CRM records, so read them as close estimates.

BookedSold

Once They Gave A Number

People who answered an income question with a number, split by whether a price text came next, then by whether an agent offer followed the price. These are patterns, not proof of cause: some people got no price text for reasons this data can't show.

BookedSold

Income Alone Or Ages And Income

People who replied to the opener, by which question they got first, and the share who replied with a number within 24 hours. Who got which text wasn't random, so this isn't a test. The two are close, and asking both in one text didn't look worse.

Same Flow, Fewer Steps

Wording comes from texts that went to hundreds of people last year.

Last Year

"We got your request"3,655 new leads
"Is this just for you, or will you be adding a spouse/kids?"3,459 new leads
"What's your estimated household income? (Rough guess is fine.)"884 new leads, 76.4% replied within 24 hours
"Plans starting at just" price text731 new leads
Agent offer with times, then "let me just confirm your appointment"693 and 400 new leads

This Mock

"What's your ZIP code?"New. A text asking for ZIP reached only 12 new leads last year, so there's no real number for it
"Ages of everyone, and your estimated household income"195 new leads last year, 83.1% replied within 24 hours
"How many people are in your household?"New. The quote form asks this too, and it changes the price
Instant estimate from the quote toolReal number, with the deductible and what it assumes
Today or tomorrow, then hand to a personNothing is booked by the chat

What This Proves And What It Doesn't

Proven

A real 2027 price came back in under 3 seconds in live tests on Nov 6, and the endpoint stops itself at 8.5 seconds.
The reply fits respond.io's limit of 10 fields.
Medicare age, low income, states we can't quote and bad answers each go to a person or a re-ask.
Answers split across texts, monthly pay and "family of 3" all read correctly in tests.

Not Proven Yet

That respond.io calls this and reads it back. That needs a real workspace.
That leads answer a ZIP question by text.
That real people's replies read as cleanly as the test replies.
The quote is an estimate. It assumes nobody uses tobacco and doesn't check job coverage, tax filing or Medicaid.
English only. The texts studied are from the English team's CRM.