Texts that land in your systems, or get a good answer.
Each mobile number sends its texts to one place: your own endpoint, or a text agent that works from the same knowledge as your voice agents. Either way, a person can step in whenever it matters.
Signed webhooks, delivered until they land.
Every inbound text is posted to your https endpoint as JSON, signed with HMAC-SHA256 so you can prove it came from Myrmur, and carrying a delivery key so you can ignore a repeat.
- Retries that give up gracefully
- If your endpoint is down, Myrmur tries again after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours, then holds the message for you to retry from the portal.
- Opt-outs in the payload
- When someone texts STOP or START, the event says so, and Myrmur keeps the opt-out on record.
- A secret you control
- The signing secret is shown once and can be rotated whenever you like.
- Health at a glance
- The portal shows how many were delivered, how many are on the way and how many are still failing, with a Retry failed button.
POST https://api.example.com/sms
{
"type": "sms.received",
"number": "+61491570110",
"from": "+61412345678",
"text": "Can I move my install to Thursday?",
"received_at": "2026-09-30T04:12:09Z"
}A text agent that knows when to stop talking.
Give it a persona and instructions, attach your knowledge libraries, and it replies from the next text. It uses the same product-aware knowledge as voice agents, and remembers which product the customer chose for the next half hour of the conversation.
- Approved answers, word for word
- Up to 50 fixed replies. When a question matches one exactly, that reply is sent as written.
- Short by design
- You set the longest reply it may send, up to 480 characters.
- A handoff line
- When it can't help, it says so in your words and flags the conversation for a person.
- Try it first
- A test box in the editor lets you text it before customers do.
- Is the mobile plan or the NBN one cheaper to add a line to?
- Happy to check. Which one do you have now, NBN or a mobile plan?
- Mobile
- Adding a line to a mobile plan is done in the app under Plan, then Add a service. Want the link?
Rules run before the model sees a word.
Some messages should never reach an AI. Myrmur handles them first, the same way every time.
- STOP, START and HELP
- Never answered by the AI. STOP records an opt-out that holds until the person texts START.
- No talking to machines
- Senders that aren't phone numbers are refused, and a loop guard stops agents replying to each other.
- Duplicates dropped
- The same message delivered twice, or sent twice in a few minutes, gets one reply.
- Limits per person
- A daily cap on replies to any one sender, and an hourly cap per conversation.
- Quiet conversations close
- After three days without a message, a conversation closes and the next text starts fresh.
- Honest status
- "Sent" means the carrier accepted it. A reply is only marked delivered when the carrier confirms it.
A person is always one tap away.
Anyone with access to Messages can take a conversation over. The agent goes quiet the moment they do, and they can hand it back or mark it handled when they're done.
- Needs a person
- Conversations the agent hands off get their own filter and badge, and an email to the owner and everyone with access to Messages. Each person can opt out of the emails.
- Or tell your own systems
- Switch on the needs-a-person event and your webhook gets the message and a link straight to the conversation.
- Afternoon works, but the driveway's gated. Someone needs the code.
- I'll get someone from the team to sort that out for you.
- Sam took over. The agent is paused.
- Thanks, I've added the gate code note for Thursday afternoon. See you then.
Bring the platform you run. We'll bring the calls.
Myrmur is opening now, by invitation. Tell us what you run and where your calls need to land, and we'll set up your first numbers and route them with you.