Can a Chatbot Send Customer Details to My Sales Team?

Yes, but “send customer details to my sales team” usually means one of two different things, and mixing them up is the most common mistake stores make when setting this up. It can mean alerting a live rep right now, so they can jump into the conversation with context, or it can mean writing a permanent record into your CRM for later follow-up. These are different jobs with different tools, and a chatbot that does one well does not automatically do the other.

This article covers the first job: real-time handoff to a person. If you specifically want the CRM-record side — deduplication, field mapping, consent, routing rules — see how a chatbot adds new leads to your CRM.

Handoff vs. CRM sync: not the same job

Intercom’s own documentation for its sales-handoff feature draws this line explicitly. A handoff “shares full conversation history and AI-generated summaries so sales can pick up with complete context” — a one-way, real-time conversational transfer. A CRM sync, separately, is what “automatically creates or updates leads” as a data record. One gets a person into the conversation immediately; the other makes sure the conversation is findable later. Most stores need both, built as two separate pieces of logic rather than one feature doing double duty.

The practical test: if a lead is worth a person’s immediate attention, handoff is the job. If it’s worth following up on but doesn’t need someone right now, CRM sync is the job. Some conversations genuinely need both — a rep gets alerted immediately, and the CRM record exists in case that rep is unavailable and someone else has to pick it up later.

How AeroChat handles real-time handoff

AeroChat’s human handover triggers on two conditions: the customer explicitly asks for a person, or the AI isn’t confident it can answer correctly. When either fires, the full conversation history carries over automatically, so the rep who picks it up sees exactly what the customer has already said — nobody asks the customer to repeat themselves. AeroChat auto-assigns the chat to an available agent, and any agent can also manually pass a live conversation to a specific teammate who’s online, which matters when a particular rep owns a particular account or region.

On the notification side, AeroChat’s smart notifications alert agents via desktop browser notification, email, or sound — configurable independently per event and per agent. It’s worth being precise here rather than assuming: as documented, this is desktop/email/sound, not a native Slack integration. If your sales team lives in Slack, the practical move is routing AeroChat’s email alerts (or a webhook, on the Growth plan and above) into a Slack channel yourselves, rather than assuming a direct connection exists out of the box.

What should trigger a real-time alert?

AeroChat’s two built-in triggers — explicit request and low AI confidence — cover most of the baseline case. Beyond those, a sales team typically wants its own trigger conditions layered on top: a pricing question from a qualified account, a request for a demo, a keyword suggesting urgency. Whatever the rule, define it as a specific, testable condition rather than “whenever it seems important,” which no automation can act on consistently. A trigger you can’t describe precisely in one sentence is a trigger you can’t debug when it fires too often or not enough.

What information should the alert contain?

Send both a summary and the full conversation, not one or the other. Intercom’s own Fin for Sales feature sends “full conversation history and AI-generated summaries” together — the summary lets a rep decide whether to act in the next few seconds, and the full history is there the moment they need more than the summary gives them. A rep who has to click through several screens to reconstruct what happened will often just miss the moment entirely.

A useful alert includes, at minimum:

• a one- or two-line summary of what the customer wants;
• the full conversation, or a direct link to it (AeroChat preserves this automatically on handover);
• which channel it happened on — web chat, WhatsApp, Instagram, and so on;
• why the alert fired — explicit request, low confidence, or a specific business rule you’ve added.

How real-time notification works across platforms

The exact mechanism varies by vendor, and it’s worth knowing the range before assuming your platform works a particular way just because a competitor’s does.

Business hours change the right behaviour

Gorgias’s business-hours-aware handoff is a useful model regardless of which platform you use: during staffed hours, get a person into the live conversation immediately; outside staffed hours, don’t leave the customer waiting on a chat window nobody is watching — convert the request into a ticket or an email the team will see when they’re back, and tell the customer that plainly rather than letting the chat go silent.

If you’re building this on AeroChat, the practical version is: use human handover during your team’s active hours, and lean on a scheduled or after-hours message plus a queued smart notification when nobody’s online to take the handoff live. The customer should always get an honest answer about when to expect a person, never a chat window that quietly stops responding.

Testing the handoff, not just the chat

Before relying on this in production, walk through a handful of specific cases: a customer explicitly asking for a person, a question the AI genuinely can’t answer confidently, a handoff request that arrives outside business hours, and two handoff requests arriving at the same time to see how routing behaves under load. Confirm that the full conversation history actually shows up on the rep’s side in every case — a handoff that drops context defeats the point of automating it in the first place.

Frequently asked questions

Does “sending details to sales” mean the same as adding a CRM lead?

No. Sending details to sales, in the sense covered here, means alerting a live person during or immediately after a conversation. Adding a CRM lead means writing a permanent record for later. A conversation can trigger both, but they run as separate steps — see the CRM lead-capture guide for the record-keeping side.

What happens if no one is available to take the handoff?

Define this before it happens, not after. A common pattern: if no rep responds within a set window, fall back to a queued notification (email or ticket) and tell the customer honestly that a person will follow up, rather than leaving them staring at “connecting you to an agent” indefinitely.

Should the alert include the full transcript or just a summary?

Both. A summary lets a rep act in seconds; the full transcript is there the moment a summary isn’t enough. Sending only one or the other tends to slow reps down in the exact moment speed matters most.

Which channels does handoff work on?

On AeroChat, human handover is available across web chat, WhatsApp, Instagram, Messenger, Telegram and email, with the same full conversation history preserved regardless of which channel the conversation started on.