Sends WhatsApp text, media, and interactive messages, places and ends voice calls, and checks whether an SMS was delivered.
6actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro checks whether an SMS reached a customer or bounced, giving agents instant visibility into notification delivery. Agents stop guessing whether a message went through and act on real data.
Ayro sends WhatsApp messages to customers directly from a support conversation, keeping communication in one channel. Customers get faster replies without the overhead of switching tools.
Ayro initiates an outbound call to a customer via Mocean, bringing urgent issues into real-time conversation. Complex problems resolve faster on voice than through text back-and-forth.
Each card is one request a support team gets, and the Mocean actions Ayro runs to close it.
Ayro answers on WhatsApp with the message type the reply actually needs - plain text, a media file, an approved template, or an interactive prompt - rather than forcing every response into one format.
For a request that needs a voice touch, Ayro dials out with a defined command flow, ends the call by its UUID when the flow completes, and retrieves the recording once it is done.
The incoming webhook hands Ayro the raw event payload with its message ID and event type, so a customer message is parsed and answered on the same channel it came in on.
Ayro checks an SMS delivery status by message ID and pulls the audio for a completed call, so a follow-up starts from what really reached the customer instead of what was sent.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Mocean actions it has and picks the ones a request needs.
Authorize the Mocean account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Mocean actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeMocean · Ayro
What can you do in Mocean without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Mocean.
Not with this toolkit. The only SMS action is Query SMS Message Status V2, which checks delivery of a message by msgid after it was sent elsewhere, and there is no verification or OTP action at all. Outbound messaging here runs over WhatsApp Send Message V2 or a voice dial.
All 6 actions your agent can call on Mocean, straight from the live MCP connection.
Query delivery status of an SMS message.
Initiate an outbound voice call via Mocean API.
Download a call recording.
Hang up an active voice call.
Receive and return the full incoming WhatsApp webhook payload.
Send a WhatsApp message via Mocean API.
Same connection, same setup. Pick the next one your team already uses.
Builds contact groups, checks caller IDs, recordings and credits, and reports on past voice and text broadcasts in DialMyCalls.
Creates meeting spaces with set access rules, reports who joined and for how long, pulls transcripts, and finds past conference records.
Sends priority alerts to people or delivery groups, tracks emergency acknowledgements, cancels retries once someone responds, and keeps rotas current.
Checks the credit balance, sends bulk batches with per-recipient content, generates one-time passwords, and pulls delivery reports back by batch ID.
Posts to the right board as an event happens, as auto-formatted text or an exact 6x22 grid of character codes.
Reads threaded topics, sends and schedules messages, manages channel subscriptions, and watches the event queue so new Zulip activity triggers the next step.

Authorize the account and your agent has all 6 actions from the first conversation.
