Send website chat enquiries to Slack
When a visitor leaves their details with your AI chat agent, Slack sends you a direct message with their name, email and what they asked. Reply while the visitor is still on your mind.
Sending enquiries to your tools is part of the Starter, Business and Scale plans. On Free, enquiries wait in Hazelchat. See pricing.
SlackFictional sample
New website enquiry from Alex Example (alex@example.com)
Message: Could you fit a team of 12 on Friday evening?
Last question: Do you take group bookings? (answered)
Website: https://your-business.example
Open in Hazelchat: https://app.hazelchat.co/#contacts/…
What arrives in Slack
Zapier’s public template “Send Slack direct messages for new Hazelchat enquiries” starts from Hazelchat’s New Enquiry trigger. This is what it puts in Slack:
| In Slack | From the template |
|---|---|
| Recipient | You pick yourself or a colleague after connecting Slack. |
| Message Text | The five lines above: name and email, message, last question with its status, website, and the link to the enquiry. |
| Send as a bot | Yes, with Zapier’s default bot name. |
| Auto-Expand Links | No, so links a visitor typed are not unfurled. |
| Link Usernames and Channel Names | No. |
Conversation transcripts and your agent’s answers never leave Hazelchat. The link opens the enquiry and its conversation there.
Set it up in four steps
-
In Hazelchat
Switch visitor details on
In Hazelchat Settings, switch visitor details on and leave capture running, so visitors can leave an enquiry.
-
In Hazelchat
Create an API key
Create an API key in the Settings card for Zapier and copy it. It is shown once.
-
In Zapier
Open the template
Open the template in Zapier, connect Hazelchat with that key, then connect Slack and choose who receives the message.
-
On your site
Test, then turn it on
Leave a made-up enquiry in your chat, check what arrives, then turn the Zap on. Hazelchat marks each enquiry it sends.
Good to know
Why a direct message
A direct message cannot notify a whole channel, even if a visitor types
<!channel>or@channelinto their message. That is why there is no template for channel posts.One message per enquiry
Each saved enquiry sends one message. Answers your agent gave and the rest of the conversation stay in Hazelchat; the link opens them.
Every field the trigger sends
You can map any of these in the Zap, as well as or instead of the template’s choice.
| Field | What it holds |
|---|---|
id | The enquiry’s id in Hazelchat |
created_at | When the enquiry was saved, as an ISO time in UTC |
name | The name the visitor typed |
email | The email address the visitor typed |
message | The visitor’s note, which may run over several lines |
website | The website the chat ran on: yours, not the visitor’s |
last_question | The visitor’s last question before they left their details |
answered | answered or unanswered: whether your agent answered that question, never the answer itself |
enquiry_url | A link to the enquiry in Hazelchat |
utm_source, utm_medium, utm_campaign, utm_content, ad_click_network, referrer_host, chat_started_on and chat_opened_via | Where the visitor came from and where the chat started, each only when the visitor’s browser reported it |
There is no phone, company or consent field. Name, email, message and last question are what the visitor typed: treat them as untrusted text, and escape them before using them in HTML or email templates.
Other ways to send enquiries
Prefer n8n? Start a workflow with the Hazelchat Trigger and add n8n’s own Slack node after it. Hazelchat publishes no ready-made n8n workflow for this; the n8n guide covers the trigger.
The same trigger has public templates for HubSpot, Trello, Microsoft Teams and Google Sheets. The Zapier guide covers the trigger for unanswered questions, the enquiry search and the draft-answer action.
Your data controls still apply
Enquiries go to Zapier (US) and on to Slack. Pausing capture, turning visitor details off or leaving the paid plans cancels pending deliveries. Revoke the key to stop them.
Deleting an enquiry in Hazelchat cannot remove the copy already in Slack. Delete it there separately.
Every new enquiry, in Slack.
Build your AI chat agent first, from your own pages. Send enquiries on once it answers well. See all integrations.