Every channel, orchestrated.

Jungledrum carries your customer conversations across SMS, short codes, voice and chat, and hands them to your AI as a single thread. Your agent picks the channel. We own the reach.

Join the waitlist See how it works

Search conversations

Priya Shah10:06RCSMoved to Thursday, 2pm.
Tom Becker09:58SMSThanks, that's sorted.
Order 482109:41VoiceCall completed, 1m 42s
Ana Lima09:20ChatIs the size 9 back in?
Kofi MensahMonEmailInvoice attached.

PSPriya Shah+44 7700 900123 · one thread, two channelsAgent handling

Hi Priya, your cleaning is booked for Tuesday at 10am.RCS · 10:02

Can I move it to Thursday?SMS · 10:05

Moved to Thursday, 2pm. I've sent the new confirmation.RCS · 10:06

Perfect, thanks!SMS · 10:07

Reminder call booked for Thursday at 1pm.Voice · 10:07

Reply arrived on SMS, kept on this thread

booking-assistant is watching this threadTake over

Receipts

RCS delivered10:02
RCS read10:03
Reply on SMS10:05
RCS delivered10:06
Reply on SMS10:07
Voice call queued10:07

Route

1. RCS
2. SMS
3. Voice

Channels

SMSFull carrier reach
Short codesSix-digit, dedicated
RCSVerified, branded
VoiceCalls that follow up
EmailIn, out and escalated
ChatSame send path

Built for agents

Your AI sends the message itself.

Connect an agent and messaging becomes something it can simply do. Send, receive, confirm delivery — no integration project sitting between the decision and the message.

Most messaging platforms that advertise an MCP server give your agent a way to read their documentation. Ours gives it a way to send the message. Everything it needs is already there: the numbers, the channels, the receipts, the reply.

Your booking agenton Jungledrum

YOUR AGENT

Your booking is confirmed for Tuesday at 10am.

CUSTOMER · SMS

Can I move it to Thursday?

YOUR AGENT

Moved to Thursday, 2pm. I’ve sent the new confirmation.

Delivered on RCS · reply arrived on SMS · one thread

Reach

Short codes, not just a chat window.

Smart inboxes stop where the app store stops. We provision newly released six-digit short codes and connect direct to the carriers, so a conversation reaches a phone that has never installed anything.

Dedicated six-digit short codes, provisioned end to end
Direct carrier connections, never a grey route
Two-way traffic and delivery receipts as standard
Voice on the same number, in progress with the carriers

Short code60123Direct to carrier

ND60123Text message · Today 10:02

Northside Dental: your cleaning is booked for Tue 10:00. Reply C to confirm or R to rebook.RNo problem. Thursday 2pm or Friday 9am?ThursdayDone. See you Thursday at 2pm.Delivered

Business messaging was built before any of this. We started from a clean sheet, on a new stack, with AI in the middle of it rather than bolted to the side.

One platform

Every channel, running live.

Routing, fallback, receipts and provisioning all happen on one platform, while your agent gets on with the conversation.

Routing, live

The platform walks your priority order until one channel delivers.

99.95%

Platform availability target

Redundant carrier paths, so a single route going down is not your outage.

300TPS

Throughput, country-wide

100 TPS per carrier, up to 300 TPS nationally. Your agents’ messages go out as they are sent, instead of waiting behind someone else’s campaign.

Number reserved
Carrier registration filed
Sender approved, live

Short codes, provisioned

We run the registration in the background while you build against a test number.

Agent is drafting a reply…

Delivered, receipt written back

Receipts your agent can read

Every send returns state the model can act on, not a log line for a human to find later.

5ways to connect

MCP, CLI, editor, REST, SMPP

AI-native or traditional. Bind straight to SMPP if that is what your platform speaks. Same platform underneath.

Features

Everything an agent needs, ready on day one.

Here is what the first afternoon looks like.

13:02
Connected the MCP server to your agent. The CLI and editor plugin went in alongside it.
13:06
Your agent sent a test text to your own handset. It read the receipt: delivered, direct route, one segment.
13:15
Short code registration filed. It clears in days, so you carry on building on a test number.
13:31
Set the route order to RCS, then SMS, then voice. The next receipt says which one carried it.
13:48
Pointed the monitoring tool's alert email at Jungledrum. The next alert rings the on-call phone instead.
14:05
Asked support a question. The AI agent answered it, then handed the follow-up to an engineer with the thread attached.
14:10
Done for the day.

Join the waitlist →

Use cases

Where agents are already doing the messaging.

Each one is the same send path with a different agent behind it. Scroll sideways.

Harbour HardwareText message · Today 11:24
Where's my order 4821?
It left the depot at 9:40 and arrives before 5 today. Want a text when it's 10 minutes away?
Yes please
Resolved by the agent
Support
Tier-one resolution over text
60123Text message · Today 10:02
Northside Dental: cleaning booked Tue 10:00. Reply C to confirm or R to rebook.
R
Thursday 2pm or Friday 9am?
Fri
Calendar updated
Appointments
Reminders that accept a reply
Kauri FitoutsText message · Yesterday 16:48
Do you do commercial fit-outs?
We do. Roughly how big is the space, and when do you want to start?
About 400m², in March
Good fit. Does Thursday 11am suit for a call?
Sales call booked
Sales
Qualifying inbound leads
60457Text message · Today 08:15
Waitematā Plumbing: payment for invoice 2291 failed. Reply 1 to retry now or 2 for a call back.
2
Callback queued
Operations
Alerts that get acted on
60890Text message · Today 14:02
Kōwhai Bank: your sign-in code is 482 913. It expires in 5 minutes.
Delivered in 0.9s
Verification
One-time codes that arrive
Something we haven't listed
Tell us what your agent needs to send, and we'll tell you which channels it should go out on.
Your use case

FAQs

Frequently asked questions.

Still curious? any hour. It escalates to an engineer when it needs to.

How is this different from a smart inbox?

An inbox gives your team one view of messages that have already arrived. Jungledrum is the layer underneath. We carry the message out over SMS, a short code, RCS or voice, and bring the reply back on the same thread.

What does AI native actually mean here?

That an agent can send, receive and confirm messages without anyone writing glue code first. Worth checking when you compare us: several platforms advertise an MCP server that can only search their documentation, so your agent still has to call a REST API to send anything. Ours executes.

Do I have to choose a channel up front?

No. Send the message once with the order of channels you’d prefer. We adapt it per channel and fall back automatically, then tell you which one carried it.

How does email fit in?

Both ways. We send email as a channel like any other, and we take email in as an escalation path: plenty of monitoring tools, legacy platforms and vendors can only email you. Send it to us instead, and we turn it into a callback, a text or a phone call with retries until someone acknowledges it.

Can you get me a dedicated short code?

Yes. New Zealand recently opened six-digit short codes, and we run the whole process for you: carrier registration, sender approval and testing. It takes days rather than minutes, so we start it the moment you sign up. Voice on the same number is in progress with the carriers.

Who answers when I need help?

An AI agent picks up first, by voice or chat, at any hour. It knows the platform and resolves most questions on the spot. Anything it can’t, it hands to one of our engineers with the conversation attached, so you don’t start again.

How long until my first message?

An afternoon for a working send path on a test number. Short code registration runs in parallel, so the build is finished and tested before the paperwork clears.