Delivery failures last week
Sarah Chen, customer operations lead at Acme Ltd, asked how many texts failed to deliver last week. Memtro read the message detail records for the week and counted them by status, with each failure's profile and cost.
How many texts failed to deliver last week, and what did messaging cost?
Telnyx shows your numbers, messages and calls. You see phone numbers with routing and tags, messaging profiles, message detail records with direction, status, parts and cost, one message's delivery status, call recordings' metadata, voice connections, number orders and webhook deliveries. When asked and granted, Memtro can send or schedule an SMS or MMS, cancel a scheduled message, retag or reroute a number, manage messaging profiles and release a number. Telnyx can tell Memtro when a message arrives, is delivered or fails, or a call ends, and a job can start on it. Message text and recordings are never read.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Telnyx tool, reads what it needs, and answers with the source cited.
These tools change something in Telnyx. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Telnyx, choosing the same kinds; the tab shows Telnyx's own steps. Each event can start a job, with the event as its input. Telnyx signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Telnyx is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
How many texts failed to deliver last week?
What did messaging cost us this month?
Which of our numbers route to the Support connection?
Are our Telnyx webhooks failing?
Schedule a text to +447700900123 for 9am tomorrow reminding them of the appointment.
Sarah Chen, customer operations lead at Acme Ltd, asked how many texts failed to deliver last week. Memtro read the message detail records for the week and counted them by status, with each failure's profile and cost.
At Northwind, a job starts when Telnyx reports an SMS arrived at the support number. Memtro looks up the number's routing and recent message records, then tells Tom Reilly, the support lead, which profile received it.
The teams that lean on Telnyx most, a question each of them asks, and what they connect beside it.
A record in Telnyx is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In the Telnyx Mission Control Portal, go to API Keys and create a key. It carries the whole account, with no scopes, and is shown once.
In Memtro, open Connections → Telnyx and paste it into API key. Set API region only to use a host outside North America.
An administrator grants the actions by name, such as Send message or Release phone number, to the teams that may use them.
Ask how many texts failed to deliver last week. Events are turned on from the connection's Events tab, and the address is then added as each messaging profile's Webhook URL in Telnyx.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Telnyx tools are the same everywhere.
Only when you ask, and only what it has been granted: send an SMS or MMS from one of your numbers (charged per message); schedule an SMS or MMS for later (charged when sent); cancel a scheduled message; change a phone number's tags, reference or the connection its calls route to; create a messaging profile; change a messaging profile's name, enabled state, allowed countries or daily spend limit; delete a messaging profile (permanent); release a phone number from the account (permanent). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key. In the Telnyx Mission Control Portal, go to API Keys and create a key. It carries the whole account, with no scopes, and is shown once.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Telnyx, choosing the same kinds; the tab shows Telnyx's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time