In billing and invoicing software, texts work best as a short nudge with a link: an invoice is ready, a payment is due or a card failed. Send from each business's own sub-account and number, keep amounts and account details out of the text, and stop the moment someone replies STOP.
A text gets read quickly, and it's the right channel for a time-sensitive nudge. It's the wrong place for a statement. Debt collection has its own strict rules, so a platform that serves collectors needs legal advice before it texts at all. This post is about ordinary business invoicing. For templates, see payment and invoice text templates.
Message plan
| Moment | Text |
|---|---|
| Invoice sent | "Example Co: your invoice is ready. View it: example.com/i/Ab3" |
| Due soon | "Reminder: an invoice is due Friday. Pay or view: example.com/i/Ab3" |
| Payment received | "Thanks, we got your payment." |
| Card failed | "Your card was declined. Update it here: example.com/u/Ab3" |
| Overdue | "An invoice is past due. View it: example.com/i/Ab3" |
Don't put the amount, the account number or the card's last four digits in a text. A lock screen is public.
Per-business setup
- Create a sub-account per business with
POST /v1/sub-accounts. - Register each business. Most approvals take 2 to 7 days.
- Give each a number, billed at $2 a month.
- Send with
POST /v1/messages. Use an idempotency key likeinvoice-884-due-soon, so retries and re-runs of your reminder job don't send twice. See deterministic idempotency keys. - Respect opt-out. Opted-out numbers are refused up front and not charged, so mark the customer for email or letter instead.
Consent for payment reminders
Agreeing to get invoices by text is separate from agreeing to marketing. Capture it where the customer gives their number, name the type of message, and store it. Keep payment texts on their own registered campaign, apart from promotion. See transactional versus promotional SMS.
Cadence
A gentle schedule: one notice at send, one a few days before due, one on the due date. After that, stop texting and let email or a call take over. Frequent reminders raise opt-outs. SaaS dunning SMS recovery math shows how to test the benefit.
Cost
An invoicing business sending 2,000 invoices a month with three one-segment texts each is 6,000 segments, so 6,000 × ($0.0075 + $0.0045). Compare that with the recovered revenue before you decide on cadence. The numbers are assumptions.
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.
Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.
Frequently asked questions
Can I text a customer who's overdue? For ordinary business invoices, with consent, yes. For consumer debt collection, get legal advice first.
Should I include a payment link? A link to your own domain is fine. Avoid public shorteners, which attract carrier filtering.
What if the text fails? Log the failure with the reason, then fall back to email so the customer still gets the notice.
Next step
Choose one trigger, such as "card failed," and build that single text first, with the idempotency key and opt-out check in place.