SMS Support Agent with Codex
Every inbound text is the same small job repeated: work out what they meant, find the matching line in your playbook, send one message under 300 characters through Twilio. Codex is at its best on well-scoped work of that shape, and a run finishing quickly is worth real money on a channel people read within a minute. The API side, a single send back to the number that texted in, is exactly the layer it is dependable at.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Ana Sofia Guzman+52 55 1234 8890
hola, cn i chnge the delivery to fri? order 88214, nobodys home thurs. thx
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Twilio
One sign-in. The agent acts through your account, scoped to what this template uses.
Business name
The name your customers know you by, written exactly as you would put it in a text message.
Support playbook
Everything the agent is allowed to answer - your hours, delivery and returns terms, the common fixes, and the exact wording for anything sensitive. It only ever answers from this.
Escalation contact
Who takes over when the agent cannot help - the name and number or team, and when they are reachable, written so the agent can say it in one short line.
Runs on Codex
Preselected for this page — connect your Codex account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why Codex for this agent
Short jobs, done quickly
The whole task is a lookup and one send, so runs stay small and the answer arrives while the customer still has their phone in hand.
Steady with the send call
Replying to the right number, once per inbound text, with no stray second message, is mechanical work rather than judgement. That is where this harness rarely slips.
Before you fork
What stops it running up a phone bill?
The instructions cap it at one message per inbound text, under 300 characters, with no signature and no link unless your playbook supplies one, which keeps most replies inside a single billed segment. It also stops after two replies to the same person and hands the thread over. Twilio bills you for those segments directly, so watch a real day before pointing your main number at it.
Run it with a different agent
Put SMS Support Agent to work on Codex
Free to start. Guided setup, a test run against staged conversations, and it's live.