Can a Chatbot Send New Leads or Complaints to Slack?
Yes, and this is one of the more useful automations to set up early, but be precise about the mechanism. AeroChat’s own documented notification channels are desktop alerts, email, and sound, not a built-in Slack app. To get leads or complaints into Slack, you connect AeroChat’s webhooks (Growth plan and above) to Slack, either through Zapier or directly using a Slack Incoming Webhook, and route the two differently since they need different urgency.
Leads and complaints are not the same alert
Treating every notification the same way is the most common mistake here. A new lead is good news that can wait for a normal check-in. A complaint, especially a tagged or escalated one, often needs eyes on it within minutes. Route them to separate channels, such as #new-leads and #customer-complaints, rather than one shared feed where an urgent complaint scrolls past between routine lead notifications.
Two ways to connect AeroChat to Slack
| Method | How it works | Best for |
|---|---|---|
| Slack Incoming Webhook | AeroChat’s webhook posts directly to a URL Slack generates for one specific channel. No middle tool needed. | A single, simple channel destination with minimal setup |
| Zapier (Webhooks by Zapier to Slack) | AeroChat’s webhook goes to Zapier first, which can format the message, route by tag or content, and post to different channels conditionally | Routing leads and complaints differently, or formatting the alert beyond a raw data dump |
The direct Slack webhook is simpler if you only need one destination. Zapier earns its place the moment you want conditional routing, sending complaints to one channel and leads to another based on how the conversation was tagged.
Setting up the Zapier route: leads vs. complaints
- Create two Zaps, both starting with “Webhooks by Zapier” as the trigger.
- In AeroChat, add the first Zap’s webhook URL as the destination for your lead-capture event, and the second Zap’s URL for your complaint/escalation-tag event.
- Send a test event for each so Zapier captures the actual data structure being sent.
- Add a “Slack: Send Channel Message” action to each Zap, pointing the lead Zap at
#new-leadsand the complaint Zap at#customer-complaints. - Format the message using the mapped fields (customer name, summary, and a link back to the conversation if AeroChat’s webhook includes one) so the alert is useful without anyone needing to click through immediately.
- Turn both Zaps on and confirm with a genuine test of each.
What a good Slack alert actually includes
A raw data dump is technically correct and practically useless. A well-formatted message includes what happened in one line (new lead or complaint tagged), who it’s from, a short summary of the conversation, and which channel it came in on, whether that’s web chat, WhatsApp, or Instagram. If the webhook payload includes a link back to the conversation in AeroChat, include it. That link is usually what turns a Slack notification into someone actually acting on it rather than just seeing it.
This complements, not replaces, human handover
A Slack alert is a notification, not a live conversation transfer. AeroChat’s human handover is still what moves the actual conversation to a person for a live reply. The Slack alert is how your team finds out it’s happened, or that a specific tagged conversation needs attention, especially if their attention genuinely lives in Slack rather than an inbox. For the broader pattern of getting the right conversation to the right person, not just a Slack ping, see can a chatbot send customer details to my sales team and, specifically for prioritising high-value customers, can a chatbot notify my team when an important customer needs help.
A concrete example message
Rather than a raw field dump, a well-built complaint alert in #customer-complaints might read: “New complaint tagged. Sarah M., order #4821, damaged item on arrival. Channel: WhatsApp. [View conversation]”. That’s four pieces of information and one link, readable in two seconds, and it’s exactly what the “Slack: Send Channel Message” step’s field mapping in Zapier is for: pulling the specific values out of AeroChat’s webhook data and arranging them into a message a person can act on immediately, rather than a wall of raw JSON.
Avoiding alert fatigue
A channel that pings constantly gets muted, and a muted channel defeats the entire point of building this. Scope each Zap to a genuinely meaningful event, such as a captured lead or a tagged complaint, rather than every message in every conversation, and resist the temptation to add more trigger conditions “just in case.” If a channel is consistently noisy, that’s a signal to narrow the trigger, not to ask the team to try harder to keep up with it.
Frequently asked questions
Do I need Zapier to connect AeroChat to Slack?
Not necessarily. A Slack Incoming Webhook lets AeroChat post directly to one channel without Zapier in between. Zapier becomes worthwhile once you want conditional routing between leads and complaints, or message formatting beyond what a raw webhook post gives you.
Can I route based on conversation tags rather than just event type?
Yes, if the tag is included in AeroChat’s webhook payload. Use a Zapier filter or path step to send tagged conversations to different Slack channels based on that field, rather than building a separate Zap for every possible tag.
What’s the difference between this and AeroChat’s smart notifications?
Smart notifications are AeroChat’s own built-in alerts, delivered via desktop, email, or sound to your agents directly. Slack routing is something you build on top using webhooks, useful specifically when your team’s actual attention lives in Slack rather than those built-in channels.
