Post website chat enquiries to Microsoft Teams
Each enquiry from your AI chat agent is posted to a Teams channel, so the right colleague can pick it up instead of it waiting in one person’s inbox.
Sending enquiries to your tools is part of the Starter, Business and Scale plans. On Free, enquiries wait in Hazelchat. See pricing.
Microsoft TeamsFictional 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 Microsoft Teams
Zapier’s public template “Send Microsoft Teams channel messages for new Hazelchat enquiries” starts from Hazelchat’s New Enquiry trigger. This is what it puts in Microsoft Teams:
| In Microsoft Teams | From the template |
|---|---|
| Team, channel and importance | You choose them after connecting Microsoft Teams; the template names none. |
| Message Text | The same five lines as the Slack template: name and email, message, last question with its status, website, and the link to the enquiry. |
| Message Text Format | Plain Text, so a visitor’s words cannot add mentions or markup. |
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 Microsoft Teams and choose the team and channel.
-
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
A channel, on purpose
Teams messages from this template go to a channel your team shares. Plain text keeps a visitor from mentioning the whole channel.
Who sees it
Everyone in the channel sees the visitor’s name, email and message. Pick a channel for the people who follow up on enquiries.
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 Microsoft Teams 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 Slack, HubSpot, Trello 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 Microsoft Teams. 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 Microsoft Teams. Delete it there separately.
Every new enquiry, in Microsoft Teams.
Build your AI chat agent first, from your own pages. Send enquiries on once it answers well. See all integrations.