Who is waiting
Maya Okafor, support lead at Acme Ltd, asked who had messaged on WhatsApp this morning. Memtro listed recent conversations with the last message's direction, channel and time, so she could see which ones were waiting on a reply.
Who messaged us on WhatsApp today, and on which channels?
Sinch shows your messaging traffic across SMS, RCS, WhatsApp, Viber, Messenger and other channels. You see the project's apps and channels, message history by contact, conversation, channel, direction and time, recent conversations, and contacts looked up by external id or phone number. When asked and granted, Memtro can send a text message, create, merge or delete contacts, stop or delete conversations and delete messages. Sinch can tell Memtro when a contact sends a message, a delivery receipt arrives or a contact opts out, and a job can start on it. Message text and phone numbers are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Sinch tool, reads what it needs, and answers with the source cited.
These tools change something in Sinch. 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, choose the kinds you want, and Memtro registers its address with Sinch for you. Each event can start a job, with the event as its input. Sinch signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Sinch 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.
Who messaged us on WhatsApp today?
Which conversations had a message in the last hour?
How many messages did we send by SMS this week?
Which channels does our support app have configured?
Send an SMS to +447700900123 saying the engineer is on the way.
Maya Okafor, support lead at Acme Ltd, asked who had messaged on WhatsApp this morning. Memtro listed recent conversations with the last message's direction, channel and time, so she could see which ones were waiting on a reply.
At Northwind, a job starts when Sinch reports a contact opted out. Memtro looks up the contact and its conversations, then tells Dan Fletcher, the CRM owner, which external id to stop messaging.
The teams that lean on Sinch most, a question each of them asks, and what they connect beside it.
A record in Sinch 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 dashboard.sinch.com, copy the project's UUID from Conversation API, then Apps, and create an access key for the project under Settings, then Access keys.
In Memtro, open Connections → Sinch and enter the Region (us, eu or br), the Project ID, the Access key ID and the Access key secret, which is shown once.
App ID is optional and names the app messages are sent from. An administrator grants the actions by name, such as Send message, to the teams that may use them.
Ask who messaged you on WhatsApp today. Events are turned on from the connection's Events tab.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Sinch tools are the same everywhere.
Only when you ask, and only what it has been granted: send a text message to a contact or phone number (spends Sinch credit); create a contact; merge two contacts (the source contact is removed); delete a contact; stop an active conversation; delete a conversation and its messages; delete a message. 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.
Region, Project ID, Access key ID and Access key secret. In dashboard.sinch.com, copy the project's UUID from Conversation API, then Apps, and create an access key for the project under Settings, then Access keys.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Sinch for you. 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