Use case
Order and delivery update texts
Text customers when their order's confirmed, and again when it's on its way or ready to collect. They know where things are without ringing to ask, and they know when to be in.
How do order and delivery update texts work?
Your order system sends a text at each step that matters: confirmed, out for delivery, delayed or ready to collect. With CaptiFi Connect it calls the REST API with the customer's number and the update, from a sender name or a number they can reply to, and delivery receipts come back to your system by webhook.
Which updates are worth a text
Not every step needs one. Customers care most about the moments that change what they do, like when to be in, when to come and collect, and when something's gone wrong. An order confirmation by text is handy for phone and in-store orders, but if you already send a detailed email, the text can stay short or be skipped.
- Out for delivery, with a time window if you have one.
- Ready to collect, with opening hours and what to bring.
- Delayed or missed delivery, with what happens next.
- Order confirmed, for phone orders where there's no email address.
Sending updates from your order system
Order updates are usually automated, so the API is the natural fit. When an order changes status, your system calls POST /api/v1/messages with the customer's number and the text. Set client_ref to your order number and it comes back to you in every webhook about that text, which makes matching easy. Send with an Idempotency-Key built from the order number and the status, so a retry can't text the customer twice about the same thing.
Subscribe a webhook to message.delivered and message.failed to see which customers got the update. A failed text is a good prompt to ring or email them before the van sets off. If customers reply, message.received passes the reply to your system too.
CaptiFi Connect doesn't connect to shop platforms or courier systems directly. Whoever runs your order system adds the API calls, and test keys let them build and test it for free.
Name or number?
Updates sent from an approved sender name show your shop's name, which people recognise at a glance. Nobody can reply to a name, though, so if you want customers to answer ('Can you leave it with next door?'), send from a UK mobile number and the replies come into your inbox.
You can mix the two: a name for the order confirmation, and a number for the out-for-delivery text, where a reply is more likely.
Features you'll use
The parts of CaptiFi Connect that order updates use:
- The REST API, with client_ref, Idempotency-Key and test keys.
- Webhooks for message.sent, message.delivered, message.failed and message.received, signed with HMAC SHA-256.
- Approved sender names for one-way updates.
- The two-way inbox for replies about deliveries.
- Message history with status filters and CSV export.
Rules that apply
An update about an order the customer placed is a service message, so marketing consent and the opt-out line don't apply. Keep it that way. 'Your parcel is out for delivery, and here's 10% off your next order' is marketing as far as the ICO is concerned, because a promotion anywhere in a message makes the whole message marketing.
Updates go to UK mobiles only. An overseas number or a landline in the order is refused with a reason and costs nothing, and your system gets that reason in the API response, so it can fall back to email.
If a customer has opted out of your texts by replying STOP, CaptiFi Connect refuses all texts to them, order updates included, until they text START. Your system sees opted_out as the reason.
Who sends order updates
Online shops, takeaways and restaurants that deliver, florists, furniture and appliance retailers booking delivery slots, garden centres with click and collect, and anyone running their own vans.
Sample texts
Merge fields in braces are filled from each contact. The part count is worked out the way the platform bills it.
Out for delivery(service)
Hi {first_name}, your order from Oakley Interiors is out for delivery today between 1pm and 3pm. Not going to be in? Reply to this text before 12.
146 characters, 1 part
Ready to collect(service)
Your order #4821 is ready to collect from Hartley's Garden Centre. We're open 9am to 5pm every day. Bring this text or your order number.
137 characters, 1 part
Delivery delayed(service)
Hi {first_name}, sorry, your sofa delivery from Oakley Interiors has moved to Thu 5 Nov because of a supplier delay. Reply if that day doesn't work.
148 characters, 1 part
Phone order confirmed(service)
Thanks {first_name}, your order with Fernside Florists is confirmed for delivery on Sat 7 Nov. Any questions, just reply.
121 characters, 1 part
Set up order updates through the API
- 1
Create a test key
Create a test key in the dashboard. It works before your account is approved and sends nothing.
- 2
Write the texts
Draft one text for each order status and keep each to one part where you can.
- 3
Call the API on each change
Send to the customer's number with client_ref set to the order number and an Idempotency-Key for the status.
- 4
Add a webhook
Subscribe to message.delivered, message.failed and message.received, and check the signature on every request.
- 5
Switch to a live key
Once your account is approved and has credit, swap the test key for a live one.
Questions people ask
Can CaptiFi Connect send updates from my online shop automatically?
Yes, if your shop or order system calls the CaptiFi Connect API when an order changes. There are no ready-made shop or courier integrations, so a developer adds the calls.
Should updates come from my shop name or a number?
A sender name is easy to recognise but can't take replies. A UK mobile number can, and the replies come into your inbox, so use a number for any update the customer might want to answer.
How do I know if an update arrived?
Each text has a status timeline in your message history, and the message.delivered and message.failed webhooks tell your system as soon as the network reports back.
Do I need consent to send order updates?
Not marketing consent, as long as the text is only about the order. Add a promotion and the whole text becomes marketing under PECR.
What does an update cost?
One credit per SMS part to a UK mobile. Texts refused before sending, such as to an opted-out or overseas number, cost nothing. Packs start at £25 for 500 credits (5p a text) and fall to 3.5p on the biggest pack, plus VAT; the pricing page has the table.
Send your first text this week
Set up your account and contacts now; we check every new account before it can send.