An undelivered code
Sarah Chen, support manager at Acme Ltd, asked why a customer never got their login code by SMS. Memtro found the message in the SMS log and showed it as undeliverable, with the error Infobip gave.
Was the SMS to this customer delivered, and if not, what went wrong?
Infobip connects Memtro to your messaging. It reads the delivery logs of SMS and email sent in the last 48 hours, with sender, recipient, status and error. It also reads your email sending domains with their DNS checks and the status of a scheduled bulk. When asked, and once an administrator has granted the action by name, it can send an SMS or an email, which reaches real people and is billed, pause, resume or cancel a scheduled bulk, and create or update a person in People. Logs older than 48 hours do not exist.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Infobip tool, reads what it needs, and answers with the source cited.
These tools change something in Infobip. 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 Infobip 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.
Which SMS failed to deliver today?
Was the email to dan@bigco.example delivered?
Is the DNS for our sending domain verified?
What is the status of tomorrow's scheduled bulk?
Pause the scheduled bulk for the spring promotion
Sarah Chen, support manager at Acme Ltd, asked why a customer never got their login code by SMS. Memtro found the message in the SMS log and showed it as undeliverable, with the error Infobip gave.
Priya Sharma, marketing lead at Northwind, spotted a wrong date in a scheduled SMS bulk. She asked Memtro to pause it. Memtro paused the bulk in Infobip, so nothing was sent, and the bulk can be resumed once the text is fixed.
The teams that lean on Infobip most, a question each of them asks, and what they connect beside it.
A record in Infobip 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 Infobip portal, open Developer Tools → API Keys → Create API key, name it Memtro and leave the allowed IP addresses empty.
Choose the scopes: sms:logs:read and email:logs:read to read logs, email:manage and sms:manage for domains and bulks, and the send or people:manage scopes only if Memtro may send or manage people. Copy the key.
In Memtro, open Connections → Infobip and enter the API host shown on the portal's home page and the API key.
Ask your first question: which SMS failed to deliver today?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Infobip tools are the same everywhere.
Only when you ask, and only what it has been granted: send an SMS (billed per message part, reaches real people); send an email (billed, reaches real people); pause, resume or cancel a scheduled SMS or email bulk; create a person in People; update a person in People (names replaced, tags and contacts added). 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 host and API key. In the Infobip portal, open Developer Tools → API Keys → Create API key, name it Memtro and leave the allowed IP addresses empty.
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