Speed to lead by text means a new lead gets a first message within minutes of asking, from a number that looks like a person's, and a rep follows up by phone. The text is the fast part. Consent, timing and who picks up the reply are what make it work.
This post is a setup for sales teams, not a pitch for hands-off automation. Nothing in Ready calls a new lead on its own; a rep places each call from the pad, one at a time. For why the first minutes matter, see the 60-second window. For the text-or-call order, see text-first or dial-first.
Start with consent, not speed
A text sent in ten seconds to someone who never agreed to texts is a fast liability. So the form comes first. The lead form needs a clear line saying the business may text them, roughly how often, and that they can reply STOP. A pre-checked box isn't a good habit; an unchecked one is easier to defend.
Ready doesn't store a per-contact consent record. The form or CRM you use is the record, so keep the timestamp and the exact wording there. An API send can carry consent_attested, which records that the sender attested consent for that send (who sent, to how many, when), but it isn't a record of the recipient's opt-in. An API send without it still goes out today, with a warning, and leaves no attestation.
Cold lists are a different case. SMS goes to consented or replied leads. Cold contact is by phone and mail, so don't point a speed-to-lead text at a purchased list.
The first-message window
You can't promise a reply rate, and we won't quote one. In practice replies often come within minutes when the first text arrives fast, and they cool as the lead moves on to the next tab. The goal is to be the first useful message in the lead's day.
A good first text is short, names the person and the business, and asks one easy question. A made-up example for a home services team:
Hi Marcus, it's Priya at Brightline Roofing. Got your request for a quote. Is today or tomorrow better for a quick look at the roof?
That's one segment of plain text. Keep it under 160 characters if you can, because an emoji drops a segment to 70 characters, and every segment is billed. Our sales text message examples have more starting points.
What the rep sees and does
A web form hits your CRM, a first text goes out, and the reply lands in the Ready Inbox. From there a rep answers in the thread, and if the lead calls back, the Dialer's pad rings. A call the rep misses shows as a Missed call card in the Inbox thread, so the text, the call and the reply sit in one place.
For the CRM side, Ready's app library connections (Close, HubSpot, Pipedrive, Salesforce, Zoho CRM) can create or update a contact, add a note, move a deal to a stage and start a Ready flow when a new contact appears in the CRM. With Close connected, Ready logs each delivered and received text on the matching Close lead, and a failed one as a note. For HubSpot, Pipedrive, Salesforce and Zoho CRM, Ready doesn't log texts to the CRM timeline on its own, so reps on those should expect to check the Inbox for the full thread.
Pair the text with a manual call
The strongest order for many teams is text, then call. The text lands in seconds, and the rep dials the lead from the pad a minute or two later, once they're free. Ready calls cost $0.025 a minute, with each started minute billed as a full minute, and only answered time is billed. A ring-out or a busy line costs nothing. A call answered by voicemail counts as answered and bills like any connected call.
Calling hours apply. The Dialer refuses a call outside 8 AM to 9 PM in the contact's local time (8 AM to 8 PM for Florida and Oklahoma area codes, 9 AM to 8 PM for Connecticut), and it warns before a fourth call in 24 hours to a Florida, Maryland or Oklahoma contact, since those states limit sales calls to three a day. Other states have stricter windows that Ready doesn't apply, so check your own.
Quiet hours at 11 PM
A lead who submits a form at 11 PM raises the hardest question in speed to lead. Ready enforces quiet hours by the recipient's area. An automation waits up to 24 hours for the window to open. A text a rep types to one person in the Inbox outside the window is scheduled for when it opens, however far off, and shows in the thread, so nobody retypes it in the morning. A text sent through the API is held only if the window opens within 6 hours.
There's one exception worth knowing. A reply to someone who texted your account in the last 24 hours can go out at any hour. A lead who texts you at 11 PM can get an answer; a lead who only filled in a form gets the held-or-refused treatment. For a plain-language read on timing across time zones, see quiet hours for multi-time-zone campaigns.
A routing setup that works
Speed fails when nobody owns the lead. Decide this before you write a single template:
| Question | A workable answer |
|---|---|
| Who gets the reply? | One named rep per lead, or a rotation with a backup |
| What if they don't answer in 15 minutes? | The next rep sees the thread in the Inbox and takes it |
| Who calls? | The assigned rep, from the pad, one call at a time |
| When does the text stop? | When the lead replies, books or says STOP |
| What happens at night? | Held or refused per the rules above; first message goes out in the morning |
Ready honors a STOP and clear phrases like "please stop texting me" automatically, and the contact can't be messaged again. Odd wording no list catches still needs a person reading replies, which is another reason to assign an owner.
What it costs
Each segment is $0.0075 plus a $0.0045 carrier fee. The all-in rate is $0.012 per segment and leaves out screening, the per-segment charge for the Scrub lists and Number validation switches. Replies you receive bill like a sent text. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.
Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.
For a team, the math is simple. If a lead gets a one-segment first text and two one-segment replies in the thread, that's three segments at the all-in rate, a small amount next to the value of one booked meeting. Every text is charged from the first one, and you need a card and a number of the account's own. The pricing page has the full list.
Send the text from code
If your form posts to your own backend, a single call sends the first text. The Idempotency-Key header keeps a retry from texting the lead twice, and consent_attested should be true only when the form collected consent.
curl -X POST https://api.tryready.com/v1/messages \
-H "X-API-Key: <key>" \
-H "Idempotency-Key: 0b8d3f52-7a1e-4c6b-9d20-5e4a1c7f9b33" \
-H "Content-Type: application/json" \
-d '{"to": "+12125550142", "body": "Hi Marcus, it is Priya at Brightline Roofing. Got your quote request. Is today or tomorrow better?", "consent_attested": true}' The messages API docs cover the rest. If your team uses a different CRM, the connections above start a flow without code.
The short version
Get consent on the form. Send a short, human first text within minutes. Have a named rep own the reply and place the call from the pad. Expect quiet hours to hold a night-time lead until morning. None of this is magic, and compliance stays the sender's responsibility. If you'd like to try it, sign up and send your own number a test lead.