Most owners looking at Slack notifications AI receptionist setups want one thing: to hear about new work in a channel the team already watches. Klugon's Slack connection does one job: it sends Slack notifications when the AI receptionist captures a lead, books an appointment or flags a conversation for a person. Each message carries the details a colleague needs to act, plus a link back to the right page in your Klugon dashboard.
This page covers what is posted and when, how to connect it with a Slack incoming webhook, which plan you need, and the things it does not do. The last part matters as much as the rest, because a notification you assume exists but never arrives is worse than none at all.
What the Slack connection does
Klugon is an AI receptionist for small businesses. It answers your website chat, WhatsApp, Instagram, Messenger and, on the voice plans, your phone line. While it talks to customers it can save leads, book appointments into your calendar and flag conversations that need a human. The Slack connection turns three of those moments into channel messages.
It is a one-way, outbound connection. Klugon posts into Slack; it never reads your Slack messages, never replies from Slack and does not create channels or users. It uses a Slack incoming webhook, which is a private URL that lets an outside service post to one channel. There is no Slack app to install from a marketplace and no sign-in with Slack.
The three events that reach Slack
Klugon sends a Slack message for these events and no others:
- New lead. When the assistant saves someone's contact details, or when you add a lead by hand in the dashboard.
- New booking. When the assistant books an appointment, or when you create a booking yourself in the dashboard.
- Handover request. When the assistant decides a chat or message conversation needs a person and flags it for your team.
A new conversation starting does not post to Slack. Neither do cancellations, reschedules, edits to an existing booking, status changes on a lead or new messages in an ongoing conversation. If you need any of those, check the dashboard; Slack will stay quiet.
What each Slack message contains
Every message is short and plain, written to be read on a phone. The fields that appear depend on what the assistant collected, so an empty field is simply left out.
New lead messages
A lead message starts with "New lead:" followed by the person's name. Underneath it lists, where known:
- Phone
- Interested in (what they asked about)
- Source (the channel or "manual" for leads you typed in)
- Notes
It ends with an "Open in Klugon" link that goes to your Leads page.
New booking messages
A booking message starts with "New booking:" and the service name. It then shows:
- Customer
- When, written as the date and time with the duration in minutes
- Staff, if a team member was assigned
- Email and phone, if the customer gave them
- Notes
The link at the bottom opens your Bookings page.
Handover messages
A handover message reads "A customer wants to talk to a person". It shows the channel the conversation happened on (website chat, WhatsApp and so on) and the reason the assistant gave, if any. The link opens your Conversations page so someone can read the thread and reply.
A sample of what the channel looks like
The following is a made-up example for a fictional salon called Willow Lane Hair, shown as plain text rather than a screenshot.
In Slack these appear as separate messages from your webhook app, one per event, in the order they happen.
Slack notifications AI receptionist setup, step by step
To set it up, you need permission to create an app in your Slack workspace, or someone who has it, and access to the Integrations page in Klugon.
Step 1: create a Slack app with an incoming webhook
Slack's own guide to sending messages using incoming webhooks is the reference here. In short:
- Go to api.slack.com/apps and choose Create New App, then From scratch. Give it a name your team will recognise, such as "Klugon alerts", and pick your workspace.
- In the app's settings, open Incoming Webhooks and switch the feature on.
- Click Add New Webhook to Workspace, choose the channel you want messages in, and authorise.
- Copy the webhook URL Slack shows you. It starts with https://hooks.slack.com/services/.
If you pick a private channel, you need to be a member of it. Some workspaces require an admin to approve new apps, in which case Slack will ask for approval before the webhook works. Slack also offers a short overview of incoming webhooks for Slack for workspace admins.
Step 2: paste the URL into Klugon
In the Klugon dashboard, open Integrations and find the Slack card. Paste the URL into the Incoming webhook URL field. There is also a Channel name field; this is only a label for your own reference. The webhook decides where messages go, so typing a different channel name here does not move them.
Click Connect. Klugon checks that the URL looks like a real Slack webhook (it must be a hooks.slack.com address, or hooks.slack-gov.com for Slack's government cloud) and then posts a short "Klugon is connected" message to the channel. If you see it, you are done.
After saving, the URL is masked in the dashboard. Treat it like a password: anyone who has it can post into that channel.
Step 3: send a test whenever you like
Once connected, the Slack card shows a Send test button. It posts a test message to the same channel so you can confirm the webhook still works after someone renames or archives a channel, or after an admin changes app permissions.
If something is wrong, Klugon shows a plain message rather than a code. For example, it will tell you if the webhook has been removed, if the channel was archived, or if Slack rejected the request. In those cases the fix is almost always to create a fresh webhook in Slack and paste the new URL in.
Changing or removing the connection
To send messages to a different channel, create a new webhook for that channel in your Slack app and replace the URL on the Slack card. Klugon posts the "connected" message again when the URL changes. To stop notifications, click Disconnect on the card. You can also remove the webhook from the Slack side, which stops it working immediately.
Which plan includes Slack
Slack sits with the team and CRM connections on the Business and Scale tiers of the AI voice agent and the AI social agent. That means:
- AI voice agent Business or Scale: included.
- AI social agent Business or Scale: included.
- AI chatbot on its own, at any tier: not included.
- Starter tiers: not included.
The free trial counts, so you can connect Slack during your seven days on a qualifying plan. If your plan doesn't include it, the Slack card shows a lock with a link to the plan you would need. Current prices are on the pricing page.
How teams use the channel day to day
The Slack connection is deliberately simple, and that shapes how it fits into a working day.
One channel, everyone sees the same thing
A webhook posts to exactly one channel, and Klugon holds one Slack webhook per business. Leads, bookings and handovers all go to the same place. Many small teams find this is the right shape: a single "front desk" channel that the owner and one or two staff keep an eye on.
If you would rather split them, for example bookings to a "diary" channel and leads to a "sales" channel, Slack alone can't do it from one webhook. You can route events to different places through Zapier, which receives the same three events and lets you filter on the event type.
Use Slack's own alert settings
Slack decides how loud each message is. You can set the channel to notify you on every new message, or mute it and check it a few times a day. Slack explains the options in its help article on how to configure your Slack notifications. Klugon doesn't tag individual people, so if you want a specific person alerted, set that channel to notify them for all new messages.
Reacting to handovers
When the assistant flags a conversation, it does not stop talking to the customer; it marks the conversation as escalated so your team can find it. The Slack message is the nudge. Someone opens the link, reads what was said and replies from the Conversations page. Our article on handing calls and chats to staff goes through how to set this up so customers aren't left waiting.
What Slack notifications look like on each channel
The same three events come from every channel Klugon answers, with a few differences worth knowing.
Website chat, WhatsApp, Instagram and Messenger
On text channels all three events can fire. The assistant saves leads when someone shares contact details, books when the booking tools are on and a slot is free, and flags a handover when a customer asks for a person or the question is beyond what it knows. You can read more about the website side on the AI chatbot for websites page and about messaging apps on the WhatsApp AI chatbot page.
Phone calls
On the voice plans, the AI phone receptionist can save leads and make bookings during a call, and both of those post to Slack in the same way. Klugon can't transfer a live call to a person. When a caller asks for someone, the assistant takes their details and a message instead, so on the phone that request usually arrives in Slack as a new lead with a note, not as a handover message.
Things you add yourself
Leads you type into the Leads page and bookings you create in the Bookings page post to Slack too. That is handy if the channel is where your team keeps track of the day, but it can surprise people who expect only the assistant's work there. The lead source shows "manual" for leads you added.
Reliability and timing
Klugon sends each Slack message as soon as the lead, booking or handover is saved, separately from the conversation itself. The customer's chat or call is never held up waiting for Slack.
There are honest limits to this. If Slack is down, the webhook has been deleted, or the request takes longer than a few seconds, that message is dropped. Klugon does not retry it later and does not show a failed-delivery warning in the dashboard. The lead, booking or conversation itself is still saved in Klugon, so nothing is lost; you just won't get the ping. Treat Slack as an alert, and treat the Leads, Bookings and Conversations pages as the record.
A simple habit covers this: check the dashboard at the start and end of each day, and use the Send test button if the channel has gone unusually quiet.
What the Slack connection doesn't do
To keep expectations straight, these are things Klugon's Slack connection does not do today:
- No two-way chat. You can't reply to a customer from Slack, and replies in the Slack thread go nowhere. Reply from the Klugon dashboard.
- No mentions or direct messages. Messages go to one channel. Klugon doesn't tag people or send DMs.
- No conversation start alerts. A new chat or call beginning isn't posted, only the three events above.
- No updates after the fact. Cancellations, reschedules, lead status changes and booking edits aren't posted.
- No summaries or transcripts. The message holds the key fields, not the whole conversation.
- No email, SMS or push alerts from Klugon. Slack and Zapier are the two ways Klugon tells you about new activity outside the dashboard.
- No live call transfer. On the phone, a request for a person becomes a message for your team, not a transferred call.
- No retries. A message that fails to send is not resent.
If any of those is a deal-breaker, Zapier receives the same events and can pass them to email, SMS tools or other apps, with the same caveat that it only knows about the three events Klugon sends.
How Slack fits with Klugon's other connections
Slack is for telling people. The other team tools are for storing things:
- Notion adds a row to a database for each new lead.
- Mailchimp adds leads who agreed to marketing emails to an audience.
- Zapier passes leads, bookings and handover requests to thousands of other apps.
You can run Slack alongside any of them. A common pairing is Slack for the alert and Notion or a CRM for the list. All of these are listed on the integrations page.
Frequently asked questions
Do I need a paid Slack plan?
No paid Slack plan is required by Klugon. You need a workspace where you are allowed to create an app and add an incoming webhook. Some workspaces restrict app creation to admins, so ask yours if the option is greyed out.
Can I send leads and bookings to different channels?
Not with Slack alone. One webhook posts to one channel, and Klugon stores one Slack webhook per business. To split events across channels, connect Zapier, filter on the event field and post to whichever channel each event belongs in.
Will Klugon post every chat message to Slack?
No. Only new leads, new bookings and handover requests are posted. Ordinary messages, conversation starts and transcripts stay in the Klugon dashboard.
Can my team reply to customers from Slack?
No. The connection only posts into Slack. Use the "Open in Klugon" link in each message to go to the conversation and reply from there.
Why didn't a notification arrive?
The most common causes are a deleted webhook, an archived channel or an app removed by a workspace admin. Press Send test on the Slack card to check; Klugon will tell you if Slack rejects it. Klugon doesn't retry failed messages, so check the Leads and Bookings pages for anything you might have missed.
Does it work on the AI chatbot plan?
Not on its own. Slack is included with the Business and Scale tiers of the AI voice agent and the AI social agent, including during the free trial. The AI chatbot product alone doesn't include it at any tier.
Do phone calls post to Slack?
Leads and bookings taken on a call post in the same way as on chat. Klugon can't transfer live calls, so a caller who asks for a person is usually saved as a lead with a note, and that is what you will see in Slack.
Is the webhook URL safe to share?
No. Anyone with the URL can post into your channel. Klugon masks it after you save it. If it leaks, delete the webhook in your Slack app and create a new one.
Slack notifications are a small piece of Klugon, but they are often what makes the AI receptionist feel like part of the team: the work lands where people already are. Start a trial on a voice or social Business plan from the pricing page, connect the webhook, and send yourself a test before the first real customer arrives.