The usual Kajabi SMS integration is a hop, not a plug-in: something in your Kajabi account fires when a person buys or opts in, an automation tool catches it, and that tool calls a texting API. What Kajabi exposes depends on your plan and changes over time, so check your plan's docs for the exact triggers before you build anything.

The part that decides whether this is safe is not the wiring. It's the consent checkbox on the form and what you do when someone replies STOP. This post covers the flow, the consent wording, and the opt-out loop, using Ready as the texting side. Ready has no native Kajabi connector, so this is the general webhook pattern.

The flow in four steps

  1. A person buys a course or joins a free offer, and a trigger fires in Kajabi (a form submission, a purchase, a tag added). Which of these your plan can send out is something to confirm in Kajabi's own docs.
  2. An automation tool or a small endpoint of yours receives that event. Most tools of this kind have a webhook catch step and an HTTP request step.
  3. That tool sends one request to the texting API with the buyer's phone number and your message.
  4. Replies and opt-outs come back to the texting number, not to Kajabi.

That last point surprises people. Kajabi won't know someone texted STOP unless you copy the opt-out back, so plan for it from day one.

Capture consent on the form, not afterward

A text to a course buyer needs the buyer's agreement to texts, and the checkout or opt-in form is where you get it. Add a phone field and a separate, unchecked checkbox. Don't bundle it into the terms of purchase.

Wording that works as a starting point:

Yes, text me course updates and offers from Acme Academy. Msg and data rates may apply. Msg frequency varies. Reply STOP to opt out, HELP for help. Consent is not a condition of purchase.

Only send to people who ticked it. If a buyer left the box empty, they get email, not texts. For more on wording that carriers accept, see SMS consent language that passes registration.

Keep the proof yourself: the form submission with its timestamp and the exact wording shown. Ready doesn't store a per-contact consent record for API sends. The consent_attested flag records your statement that the recipient agreed, and the proof lives in your form or CRM.

The request your automation sends

One text to one buyer is a single call to POST /v1/messages:

POST https://api.tryready.com/v1/messages
X-API-Key: <key>
Idempotency-Key: <a UUID from the order>

{"to": "+12125550199", "body": "Acme Academy: welcome to the course! Your first lesson is ready. Reply STOP to opt out.", "consent_attested": true}

Two details matter here. First, send an Idempotency-Key built from the purchase, so a retried webhook never texts the same buyer twice. Automation tools retry on timeouts more than you'd expect. Second, set consent_attested to true only on the branch of your automation that checked the consent box. The full request reference is at docs.tryready.com/api/messages.

If your tool can't build a UUID, use the order number or another unique value that stays the same on a retry.

Opt-outs and replies

Ready answers STOP, START and HELP automatically and blocks later texts to someone who opted out. Clear phrases like "please stop texting me" are caught as well.

The gap is the other tools in your stack. If you also email or text from somewhere else, check GET /v1/opt-outs/:phone before a send from that tool. GET /v1/opt-outs lists the opted-out contacts on the account, but it leaves some cases out, so don't treat it as a complete mirror. More on this in handling SMS opt-outs.

Timing and quiet hours

A course buyer who purchases at 11 PM shouldn't get a text at 11 PM. Ready holds an API text only if the recipient's quiet window opens within 6 hours. Otherwise the API answers 409 QUIET_HOURS_BLOCK and the text isn't sent. Add "hold_until_allowed": true to the request and Ready holds it up to 24 hours instead, answers 202 and sends it when their window opens, so you need no retry or delay step. A reply to someone who texted you in the last 24 hours goes out at any hour.

What it costs

Each segment is billed at $0.0075 plus a $0.0045 carrier fee, so $0.012 all-in per segment, which excludes screening. A welcome text of 150 characters is one segment. For 800 new buyers a month with one welcome text and one reply each: 800 sends x $0.012 = $9.60, plus 800 replies x $0.0105 (the segment rate plus a $0.003 inbound carrier fee) = $8.40, or $18.00 in all. A number is $2 a month and registration is $25 a month; most approvals take 2 to 7 days. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing. Current rates are on the pricing page.

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.

Frequently asked questions

Does Ready have a native Kajabi integration?

No. The pattern above uses whatever webhook or automation features your Kajabi plan exposes, plus an HTTP request to Ready. Check Kajabi's docs for what your plan supports.

Can I text everyone on my email list?

No. Text only people who agreed to texts. An email subscription isn't consent to SMS.

Where do I keep proof of consent?

In your form tool or CRM, with the timestamp and the exact wording. Ready's consent_attested flag records your statement, not the individual's opt-in.

Next step

Build it with one test number and one test purchase first. When it works, create an account and try it on real buyers.