Skip to main content
Velor

Channel · SMS

The same agent, grounded and compliant — in the text thread.

Your Velor agent works the same way over SMS as it does on chat and voice — same knowledge base, same custom actions, same guardrails. One update applies everywhere. On SMS a customer who asks for a person is handed to your team's inbox; the agent also hands off when it judges it cannot resolve something or the customer is clearly frustrated, as it does on chat and voice. Who is notified depends on who you set to receive escalations.

What it does.

One agent, every channel

The SMS deployment uses the same agent configuration as your chat and voice channels. Knowledge base, action schema, and guardrails are shared — one update applies everywhere.

Grounded replies via text

Every SMS reply is grounded in your current knowledge base. The agent retrieves on every turn, so customers get accurate answers even when your docs change.

Action execution over SMS

Order status, subscription changes, appointment confirmations — the same custom actions available on chat and voice work over SMS. Destructive actions are held for a teammate to approve.

Straight answers about reaching a person

When a customer asks for a person, the conversation is escalated into your team's inbox and the customer is told a teammate has it, but only if the handoff actually went through. If it could not be raised, the customer is told that plainly and nobody is promised. The agent also hands off on its own judgment when it cannot resolve something or the customer is clearly frustrated, under the same rule: nobody is promised unless the handoff went through.

How the SMS channel works.

  1. 01

    Customer texts in

    Inbound SMS to your Twilio number routes to the Velor agent. No app required — standard text message from any device.

  2. 02

    Agent retrieves and responds

    Same retrieval pipeline as chat. The agent pulls the relevant KB passages and, where your action schema allows, calls your APIs — all within the SMS thread.

  3. 03

    Destructive actions wait for a human on your team

    A write action that needs confirmation never fires from the text thread. It is held, queued for a teammate to approve or decline in the dashboard, and the customer is told someone will review it and follow up — the same gate as every other channel, resolved by your team rather than by the customer.

  4. 04

    When the customer asks for a person

    An explicit request for a person raises an escalation in your inbox, ahead of any AI answer. Whether a teammate is paged depends on who is set up to receive escalations in your workspace. If the assistant itself fails to produce an answer, the customer is asked to try again shortly, your team gets a dashboard notification, and the thread stays with the assistant.

What teams ask about SMS.

Can I use my existing phone number?

Yes — SMS routes through your Twilio number or a new one you provision. The number is yours; Velor handles the agent routing behind it.

What do I have to set up first?

A Twilio number in your own Twilio account, with its messaging webhook pointed at Velor. For US numbers, carriers filter texts from unregistered numbers, so you also register for A2P 10DLC with Twilio; that registration is yours to complete and Velor does not do it for you. Until you do both, the Channels page in your dashboard shows SMS as needing setup, and it shows Live only after a real text has reached Velor.

How does threading work for multi-turn conversations?

Conversations are thread-tracked by phone number. The agent maintains context across the same SMS thread, so follow-up messages continue in the same conversation — not a fresh session.

What about MMS and images?

Images and files a customer sends by MMS are received and stored with the conversation. The agent replies in plain text and cannot send files back over SMS — attachments on an agent reply go out by email only.

How does this affect my existing chat configuration?

Nothing changes — SMS is an additional channel, not a replacement. Your chat widget, voice configuration, and action schemas remain exactly as configured. You extend to SMS without migrating anything.

One agent, every channel

Configure once. Deploy everywhere.

SMS runs on the same brain as the rest of Velor — one knowledge base, one set of guardrails, one scoped action schema, one audit trail. Tune a behavior once and every channel respects it. No per-channel re-training, no drift between how the agent answers on the phone versus in chat.

Run it on your own tickets.

Every workspace starts with a 14-day free trial. No credit card. If you want a guided walkthrough against your data, we're happy to run one with you.