Were this week's Textmagic texts delivered, and which chats are still unread?
Textmagic connects Memtro to your business SMS account. It reads message activity, sent and received, with delivery status and times, and your two-way chats with unread counts and assignees. It finds contacts by name, phone or email, and lists contact lists, scheduled sends, templates and email senders. When asked and granted, it can send or schedule an SMS, send an email campaign, manage contacts, lists and templates, unsubscribe a number, cancel a scheduled send, and close or reopen a chat. It never returns message text, phone numbers or contact names, only ids, statuses and times.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Textmagic tool, reads what it needs, and answers with the source cited.
These tools change something in Textmagic. 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.
Once Textmagic 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.
Textmagic + MemtroWhich outbound messages failed to deliver this week?
Which chats have unread messages, and who are they assigned to?
What is scheduled to send next?
How many members does the Spring offers list have?
Create a template called Delivery reminder.
Sarah Chen, marketing manager at Northwind, asked whether Tuesday's SMS session reached everyone. Memtro read the outbound messages for that session and grouped them by delivery status. It listed the failed ones by contact id so she could check those contacts in Textmagic.
Dan Fletcher, operations lead at Acme Ltd, asked Memtro to text the Site visits list that Friday's visits move to 10am. With sending granted to his team, Memtro sent the SMS to every member of the list, charged to the account balance. The send then showed in Textmagic's message activity with its delivery status.
The teams that lean on Textmagic most, a question each of them asks, and what they connect beside it.
A record in Textmagic 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.
AgentMail
Fireflies.ai
SendGrid
Avoma
Missive
tl;dv
Grain
Fathom Video
ClickSend
OneSignal
Bird
MeetGeek
Sinch
Telnyx
SMTP2GO
MailerSend
InfobipIn Textmagic, open API settings and choose Add new API key. Name it Memtro, generate it and copy the key. Keys made for the old v1 API do not work.
In Memtro, open Connections → Textmagic and paste your Username and the API key. Your username is shown next to your keys in Textmagic.
The key has the whole account's access and can send charged messages, so an administrator grants the send actions by name only to the teams that should use them.
Ask which outbound messages failed to deliver this week.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Textmagic tools are the same everywhere.
Only when you ask, and only what it has been granted: send or schedule an SMS to numbers, contacts or lists (charged per message); send an email campaign to contacts, lists or addresses (charged); create a contact; edit a contact; delete a contact; add a note to a contact; create a contact list; add contacts to a list; remove contacts from a list; create a message template; edit a message template; unsubscribe a phone number (permanent); cancel a scheduled message; close or reopen a chat. 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.
Username and API key. In Textmagic, open API settings and choose Add new API key. Name it Memtro, generate it and copy the key. Keys made for the old v1 API do not work.
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
