A ClickFunnels SMS integration works the same way as most funnel-to-text builds. The opt-in form captures a phone number and consent, a webhook or automation step forwards the lead, and a texting API sends the first message. The funnel builder doesn't need to know anything about carriers.
This post is for developers, agencies and sales teams who run funnels and want the follow-up to happen by text within minutes. We'll cover consent on the opt-in page, the two common ways to forward a lead, the send request, 10DLC registration and a worked cost example.
Where the text fits in a funnel
A funnel has a few moments when a text earns its place: right after an opt-in, after a booked call, after an abandoned checkout, and when a lead replies. Each of those starts with a funnel event and ends with a message to someone who agreed to hear from you.
ClickFunnels can pass lead data to other tools through its integration options. Which options and triggers your account has depends on your plan and the current product, so confirm them in your account. Ready has no native ClickFunnels connector, so you connect the two with a webhook or a Zapier-style automation tool and one HTTP request.
Capture consent on the opt-in page
The number a lead types into a funnel form isn't proof they want texts. Add a separate checkbox that is unchecked by default, with the disclosure beside it.
Wording to adapt:
Yes, text me about my request. By checking this box I agree to receive texts from Acme Coaching. Msg and data rates may apply. Msg frequency varies. Reply STOP to opt out, HELP for help.
Funnels have a few consent traps worth naming:
- A phone field without a checkbox. Many funnels ask for a number so someone can call. If you plan to text too, the checkbox has to be there.
- Consent hidden in a thank-you page. Agreement must happen at the form, before the first text.
- Bought or rented lead lists pushed into a funnel. Texting purchased lists is barred by Ready's acceptable use policy, and a scrub doesn't make it allowed.
- One checkbox covering everything. Keep texting consent separate from email consent and from the terms of the offer.
Ready stores no per-contact consent record: you keep it in your funnel data or CRM, along with when it was given. (A sign-up on a Ready-hosted opt-in page is the exception, and is stored per contact.) The consent_attested flag on each API send is your statement that the recipient agreed. See SMS opt-in wording and keyword examples for more form language.
Two ways to forward the lead
| Webhook to your endpoint | Automation tool | |
|---|---|---|
| Setup | A small service you write and host | A workflow with a trigger and an HTTP step |
| Control over retries and duplicates | Full | Whatever the tool offers |
| Good for | Developers and platforms | Agencies and sales teams without a backend |
| Failure mode | Your endpoint is down | The workflow hits a task limit or delay |
In either case the step that receives the lead needs the name, the phone number and the consent answer as separate values. Add a filter: continue only if the consent answer is yes. Leads who skipped it go to a call or an email instead.
If you build the endpoint yourself, acknowledge the funnel's webhook quickly and do the sending after. Our guide to SMS API integration covers a clean structure for that.
Send the first text
The sending step is one request:
POST https://api.tryready.com/v1/messages
X-API-Key: <key>
Idempotency-Key: <the lead ID>
{"to": "+12125550199", "body": "Hi Dana, it's Acme Coaching. Thanks for signing up. Want the booking link or a quick call first? Reply STOP to opt out.", "consent_attested": true} - Use the lead's ID as the
Idempotency-Key. Funnel webhooks and automation tools can deliver the same event twice, and a retried request then never sends twice. - Send
toin E.164 form. A 10-digit US number is treated as +1. - Set
consent_attestedto true only on the branch that passed the consent filter. - Leave
fromout, and Ready picks the number the contact already texts with, or your number closest to their area code.
Reference: docs.tryready.com/api/messages. For a funnel that sends the same text to a group, such as a webinar reminder, POST /v1/messages/bulk takes up to 100 recipients per call.
10DLC registration for funnel traffic
Funnel texts to US numbers from a local number go out on a registered 10DLC campaign, and unregistered traffic gets carrier-filtered. Registration is the step that tells carriers who you are and what you'll send. The 10DLC explainer has the background.
Ready handles the filing in the app: registration is $25 a month and covers the brand and its first campaign, each number is $2 a month, and most approvals take 2 to 7 days. Ready registers businesses with an EIN, so a sole proprietor gets an EIN first. Before you register, an account can send up to 500 texts a month at its normal per-text rate, enough to test a funnel end to end. If you build funnels for other businesses, each one gets its own sub-account with its own numbers and registration, which keeps their traffic and opt-outs apart.
The campaign description should match what the funnel really does. If the opt-in page promises appointment reminders and you send promotions, expect trouble.
A worked cost example
These are assumptions, not benchmarks. Say a funnel gets 500 opted-in leads a month. Each gets one 1-segment text from you and sends one 1-segment reply.
- Texts: 500 leads x 2 segments each = 1,000 segments.
- Rate: $0.0075 a segment plus a $0.0045 carrier fee, $0.012 all-in, excluding screening.
- Math: 1,000 x $0.012 = $12.00 a month in texts.
- Fixed costs: $25 for registration and $2 for one number.
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.
Replies are billed like sent texts, so count them. An emoji in the body drops a segment to 70 characters, so keep the text plain if you want it to stay at one segment. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.
Quiet hours and late-night leads
Funnels collect leads at all hours. Quiet hours follow the recipient's area. An API text goes out if the window opens within 6 hours. If it opens later, the API answers 409 QUIET_HOURS_BLOCK and the text isn't sent, unless the request includes hold_until_allowed: true, which holds it up to 24 hours. Without that flag, your workflow has to catch the refusal and send again once the window opens, with a new Idempotency-Key: the refused call's key replays the same refusal.
Frequently asked questions
Does ClickFunnels have a built-in SMS integration with Ready?
No. Ready has no native ClickFunnels connector. You forward leads with a webhook or an automation tool, then call the API.
Can I text everyone on my funnel's opt-in list?
Only those who agreed to texts on the form. A phone number collected for a call isn't consent to text, and compliance is the sender's responsibility. Use calls or email for the rest.
How fast should the first text go out?
Within minutes, while the lead is still looking at your offer. Plan for quiet hours so a late-night opt-in doesn't turn into a failed run.
Next step
Add the consent checkbox to one funnel and forward a single test lead to your own phone. When that works, sign up, add a card and a number, and send it. If you're also wiring Meta ads into the same funnel, the Facebook lead ads SMS integration guide covers that hop.