Connect Slack

A card arrives when something is finished and worth acting on, not while a customer is still typing. Four things post by default:

• New submission — a customer reached the end of a flow: a booking, a lead, an order.
• Booking cancelled by customer and Booking rescheduled by customer — they changed their own appointment from the chat.
• Booking request expired — a request waited past your approval window and lapsed.

Status changed is there too, switched off to begin with. Turn it on and the channel also hears when you or a customer move a submission — including Accept and Decline. It is off by default because working through the inbox can move one submission three times in a minute, and a channel that posts all three is a channel people mute.

• A heading naming what happened and which bot it came from, so a channel carrying two bots still reads cleanly.
• Every answer, one per line, in the order the customer met the questions, with your own question text as the label. A service is named rather than given as an id, and a time is a wall clock on your business's zone.
• The booking, when there is one: the service, the time, and the staff member or resource it is with.
• The customer: their name, username or phone number as far as the flow captured them, and the channel they came from.
• An Open in Meerlume button straight to that conversation in your inbox, where you can reply, take over, or approve.

The card is not editable in this version. If you need a different shape — only the phone number, say, or a line for your own system — send a webhook instead and post to Slack from your side.

Each connection covers exactly one channel, because that is how Slack's incoming webhooks work: the channel is fixed when you install, and a card cannot be redirected afterwards. Press Add another channel to connect a second, a third, as many as your team needs. Channels do not count against the webhook endpoints your plan includes.

• Point each channel at particular bots. Open a channel, press Edit, and turn off All bots to choose. A salon bot can post to #bookings while a quote bot posts to #leads.
• Pick the events per channel. The same Edit dialog ticks what that channel hears, so one can take everything and another only new submissions.
• Label a channel if the name alone is not obvious. The label shows in the list and on the channel's own page.

• Every card is logged. Open a channel to see what was posted, what Slack answered, and the exact card body. While the connection is live, a failed card can be resent from there.
• A card Slack could not take is retried with growing gaps for about two days. Slack also limits how fast one channel can be posted to; when it asks us to wait, we wait.
• If the app is removed in Slack, or the channel is deleted, Slack refuses permanently. Meerlume switches that connection off the moment it hears so and tells you through the bell and your notification channels. Reconnect the channel to resume — a switched-off connection of this kind cannot simply be turned back on, because the old hook is dead for good, and the cards queued while it was dying cannot be resent.
• To stop posting yourself, use the switch on the channel. Remove deletes the connection and its log. Either way the Meerlume app stays in your workspace until you remove it in Slack.

Nothing. The app asks Slack for one permission — posting to the channel you chose — and holds no access to your messages, files, channel list or people. It cannot read replies to its own cards, which is also why acting on a booking happens in Meerlume rather than from a button in Slack.

What does leave Meerlume is the content of the card: your customer's answers, their name and contact details, and their booking, posted into a workspace you control. Treat a channel of cards the way you would treat the inbox itself, and keep it to the people who need it.

Slack is included on Growth and Pro, and connecting another channel never uses up one of the webhook endpoints your plan includes. Cards keep posting if you go over your monthly conversation cap; only adding, enabling and testing channels waits until the cap lifts. If you move to a plan without it, your channels are kept and posting pauses, then resumes on its own when you upgrade again.