A lot of the businesses that ask us about Intercom aren't looking to replace it. They've already got a support team running there, a Messenger widget customers know, and workflows built around it. What they're missing is the phone — Intercom is built for chat and email, and it doesn't pick up a call. That's usually the actual reason AIVA and Intercom end up connected, not any dissatisfaction with Intercom itself.
What "side by side" means in practice
AIVA's Intercom integration isn't about taking over your chat widget. It's about covering voice and SMS — the channels Intercom doesn't — while staying connected to the same customer record and the same team. A customer might message on Intercom, then call the same business an hour later; with the integration connected, that call isn't a stranger showing up. AIVA can see the same conversation history and pick up where the chat left off, instead of asking the customer to explain themselves from scratch. It works in the other direction too — if your team resolves something in Intercom and the customer calls back later with a related question, AIVA can see that history, so the call doesn't start with the customer explaining a decision your team already made.
Handoff, without the repeat-yourself problem
When a conversation needs your team — a request for a human, a query outside what AIVA handles, a genuinely difficult call — AIVA hands off directly into Intercom with the full conversation attached. Your support team sees it exactly where they already look for everything else: same inbox, same customer timeline, same assignment rules. There's no separate dashboard for AIVA conversations that someone has to remember to check.
A handoff that dumps a customer into a new tool with no history is barely better than no handoff at all — they still have to repeat themselves, just to a different party. A handoff into the same Intercom conversation, with history intact, is the difference between "let me get someone" and someone actually being able to help immediately.
What actually syncs between the two
It helps to be precise about the boundary, since "AIVA and Intercom share a customer record" could mean a lot of things. What AIVA reads is conversation history — enough to recognise that a caller has an existing thread and to see what was already discussed, so it isn't starting cold. What AIVA writes is new activity: a handed-off conversation lands in Intercom as a new conversation in your inbox, tagged and attached to the right customer, with the full transcript of what AIVA covered before handing off.
What doesn't happen is any rewriting of your existing setup. AIVA doesn't edit conversations your team already had, doesn't touch your macros or saved replies, and doesn't change your assignment rules — it hands a new conversation into the queue those rules already govern, the same as if a customer had messaged in directly. Your Intercom instance ends the day with more conversations in it, not a different Intercom than the one your team configured.
This happens at the moment of handoff, not on a delay — by the time your team gets a notification, the conversation is already sitting in the inbox with everything AIVA knew attached, ready to pick up rather than something that shows up ten minutes later. That immediacy is deliberate: a handoff that arrives minutes after AIVA told the customer "let me get someone" undercuts the very thing that made the handoff feel smooth in the first place.
What Intercom keeps doing, what AIVA adds
The division of labour stays simple: Intercom keeps running your chat and email exactly as it already does, with the team, macros, and reporting your business has built up around it. AIVA sits alongside it as the voice and SMS layer, using the same customer record so neither side is guessing about what the other already knows. Nothing about your Intercom setup needs to change to add this — no new inbox rules to learn, no macros to rebuild.
A conversation that crosses channels
A customer messages Intercom on a Tuesday asking about a policy exception, and your team resolves it after a short back-and-forth. On Thursday, that same customer calls to ask a related follow-up question. Without the integration, AIVA would be starting cold, and the customer would have to explain the exception again before getting anywhere. With it connected, AIVA can see that the exception was already granted and can pick the conversation up from there — either answering directly if it's a simple follow-up, or handing off to your team with both conversations already attached if it's not.
When a customer uses both channels almost at once
Occasionally a customer doesn't wait for one channel to finish before trying another — they message Intercom, don't get an immediate reply, and call AIVA a few minutes later about the same thing, or the reverse. Worth knowing how that plays out. Because AIVA checks conversation history before responding, a call that comes in while an Intercom thread is still open isn't treated as unrelated — AIVA can see that the same customer already has something in flight and factor that in, rather than answering as if it's hearing about the issue for the first time.
Where this actually needs a decision on your end is ownership: if a live agent is already typing a reply on the Intercom side when AIVA picks up a call about the same issue, should AIVA keep handling it, or recognise the open thread and hand off immediately rather than potentially giving the customer two different answers from two different places? Most teams set this so an actively-worked Intercom conversation takes priority — AIVA acknowledges the call, confirms your team is already on it, and either answers a narrower question directly or hands off cleanly rather than duplicating an agent's in-progress work.
This is a genuinely rare pattern — most customers wait for a reply before trying a second channel — but it's the kind of edge case worth deciding on deliberately rather than discovering the first time it happens with a real customer watching two different answers arrive in two different places.
Who this fits
This tends to make the most sense for businesses with real investment in Intercom already — a trained support team, canned responses and macros built up, reporting built around it — who just want the channels Intercom can't cover on its own. AIVA becomes the voice and SMS layer in front of the same team, not a second support system running in parallel.
Considerations before you connect
Worth deciding before going live: how AIVA should identify a returning customer across channels — usually phone number or email, whichever your Intercom setup already uses to match people — so history actually links up rather than creating parallel, unconnected records. It's also worth agreeing on assignment rules for handoffs: whether AIVA-originated conversations should go to a general queue or to specific team members, and whether that should differ from how Intercom conversations are normally assigned.
Setting it up
Connect your Intercom workspace, decide how AIVA should identify returning customers across channels, and set which conversation types should hand off directly to your team versus stay with AIVA. Most teams have this running within a setup session, alongside whatever inbox rules are already in place.
If your support team already lives in Intercom and your phone doesn't, see this next to similar options — Zendesk, Freshdesk — plus Slack if your team also wants alerts outside the inbox, in AIVA's other integrations. Read more on how handoffs work, check pricing, or start free and connect Intercom yourself.