Features
In-call SMS
OnCore texts the caller while they're still on the phone — links, price lists, directions — so they hang up with it in hand.
Your assistant can text the caller mid-call — so the link, address, or price they asked about is on their phone before they hang up.
What it is#
Some things are better in writing than read aloud — a link, a price list, an address. When a caller asks for one, the assistant says a line you choose ("Sure, I'll text that to you right now"), sends the message, and the caller has it on their phone before the call ends — they can even confirm it arrived while still on the line. An SMS reason defines each scenario: the situation that triggers it, what the assistant says, and the exact text that goes out.
What you can do with it#
- Send a booking or payment link — when the caller is ready to act, text them the link to your booking or payment page mid-call instead of hoping they find it later. The body is fixed text you write when creating the reason — every send carries the same message.
- Text prices and menus — a full price list arrives as a message rather than being read out item by item.
- Send directions or an address — the caller leaves the call with it saved on their phone, not scribbled down.
- Answer "can you send me that?" properly — any stock content a caller regularly asks for becomes its own SMS reason with its own wording.
- Text a different number — if the caller wants it sent elsewhere, they can read out another number and the assistant sends it there.
How to set it up#
Everything is configured through OnCore's REST API. You create an SMS reason for each scenario — a name, the trigger ("when the caller asks for pricing"), the line the assistant speaks before sending, and the message body itself — attached to the assistant that should send it. That's the whole setup: texts go out from OnCore's own sending numbers, so you don't need to provision or register anything. The steps are in the SMS Reasons API reference; how in-call texts relate to two-way texting on the SMS channel is covered in SMS & texting.
Limits & FAQ#
- Texts arrive from a OnCore sending number matched to the caller's country, which may differ from the number the caller dialled.
- A number given without a country code is assumed to be in the same country as the assistant's phone number; if a number can't be understood, the assistant politely asks the caller to repeat it.
- Every text is recorded on the call: the end-of-call report carries the ID of the SMS reason that fired, and the call is categorised as an SMS send — so your systems can see exactly what was sent and why.
Do we need our own texting number? No. In-call texts are sent from OnCore's numbers with no setup on your side. That's separate from the two-way SMS channel, where the assistant answers inbound texts on your own number — that one does require a linked number.
What happens if the text can't be sent? The assistant is told the send failed and the conversation carries on — a failed text never drops the call. If the problem is the number itself, the assistant asks the caller to repeat it before trying again.
Can one assistant send different texts for different requests? Yes. Add one SMS reason per scenario — pricing, directions, a booking link — each with its own trigger, spoken line, and message.