11 integrations

Reply on iMessage knowing what was said everywhere else

Connect Aircall, Dialpad, Gong, Gmail or Salesloft so an agent replying on iMessage knows what was already said on the phone and by email — and your reps can ask what happened without digging.

No code · Works on your own number · Live in minutes

A customer who called yesterday and texts today should not have to start over. Connecting your call and email systems gives the agent the history — the call that happened, the thread, what was promised — so its reply picks up where the last conversation ended.

This is what separates a two-way texting tool from an agent. The tool moves messages. The agent knows the account had a call on Tuesday, that a follow-up was promised, and answers accordingly.

Your team gets the same benefit in reverse: a rep can ask what was discussed with an account and when, and get it summarised from the recording and the mailbox instead of scrolling for it.

🤖 Account Agent · iMessage
what did we promise brightside on the call?
•••
On Tuesday’s call you agreed to send revised pricing by Friday and to look at their SSO question. Neither has gone out yet.
ugh. anything by email since?
One — their ops lead chased the pricing yesterday afternoon. Want me to draft a reply?
↳ Gong transcript + Gmail thread, same account

Who this is for

Teams running calls and texts side by side

Stop customers repeating themselves because the last conversation happened on a different channel.

Reps who need the backstory fast

Ask what was discussed with an account and when, summarised from the call recording and the mailbox.

Support and success teams

One thread per person, with everything that happened elsewhere already in context.

Two ways to connect Communications

Connected for the bot

Your account, every conversation

Connect the company phone and email systems and the agent has shared history for every conversation on the number.

Enabled for customers

Their account, their data

Each rep connects their own line and mailbox, so the agent works from that rep’s history with the customer rather than a generic company view.

What people use this for

The same agent, asked different things by different people on the team.

Rep

Pick up where the call left off

Someone who spoke to your team yesterday texts today, and the agent already knows what was discussed.

Rep

Ask what was promised

Get commitments from a call summarised back, instead of listening to a recording to find them.

Customer

Stop repeating yourself

History from email and calls is in context, so the agent never asks something already answered elsewhere.

Manager

Catch up on an account fast

Ask what has happened with a customer this month and get it across calls, email and texts at once.

Support

Avoid the cold handoff

When a person takes over, the whole cross-channel history is already there rather than being re-gathered.

Ops

Keep one thread per person

Calls, email and texts sit against the same customer instead of in three disconnected tools.

11 Communications integrations

Communications integration FAQs

Is this a replacement for our phone system?

No. It connects to the phone system you already have so an agent texting on iMessage has that context. Calls keep happening where they happen now.

Which systems can I connect?

Aircall, Dialpad, Gong, Nooks, Salesloft and Gmail.

How is this different from an SMS platform?

An SMS platform moves messages. Here an AI agent reads the connected systems and answers on its own, in the blue bubble, with the history behind it.

Can each rep keep their own history separate?

Yes. With each rep connecting their own line and mailbox, the agent works from their relationship with the customer rather than a shared company view.

Other categories

Put it on a number your customers already text

Pick a model, write a prompt, connect the tools it needs, and go live in the blue bubble — no code required.