Communication
Slack gets the things that need a person.
Notifications are easy to send and easy to start ignoring. Siteleon posts to Slack only when someone should act: a new enquiry for a service you asked to be told about, a contact form that has stopped delivering, an advertising cost per customer that has jumped. Your team can claim an enquiry or pass it on from the message itself. Anything that changes the website opens in Siteleon, with the preview in front of you.
What connects
You authorise your Slack workspace, choose which channels receive which kinds of message, and Siteleon posts there. It reads nothing in Slack except the responses to its own messages.
What data moves, and which way
- Sent: a new-enquiry message carrying the service asked about, the location, the page that produced it and where the visitor came from.
- Sent: alerts that need a decision — a broken form, unusual bot traffic, a business fact that changed and affects published pages.
- Received: your channel and member list, so you can route each kind of message to the right place.
- Received: the action taken on a message — claimed, assigned, snoozed or dismissed — written back to the enquiry or the insight.
What Siteleon can do with it
- Give each service line its own channel: maintenance contracts in one, emergency call-outs in another that the duty engineer actually watches.
- Claim an enquiry from the message so two people do not ring the same hotel back within the hour.
- Get one weekly summary in plain language — what came in, what became a customer, what changed — instead of a daily trickle.
- Be told when the contact form stops delivering, which is the failure most businesses otherwise discover a fortnight late.
Things you could ask for once it is on
- “Post emergency call-out enquiries from Alicante to the duty channel and everything else to sales.”
- “Stop sending individual visitor alerts — send one summary on Monday morning instead.”
- “Tell me in Slack if any form stops receiving submissions for more than two hours.”
Setting it up
Four steps, in this order.
- 01Open Integrations, choose Slack and authorise the workspace — a Slack administrator may need to approve the app first.
- 02Pick a default channel, then add channels for specific services, locations or alert types.
- 03Choose which events deserve a message and which belong in the weekly summary instead.
- 04Invite Siteleon into each private channel you chose, then run a test enquiry to confirm delivery and the claim button.
Permissions
Siteleon asks to post messages to the channels you choose, read the list of channels and members so you can route to them, and receive the button presses on its own messages. It never asks to read your conversation history, never enters a channel it has not been invited to, never reads direct messages, and never posts as one of your people.
Where it stops
Slack is where you are told and where you triage. It is not where the site changes. You can claim, assign, snooze and open — you cannot publish a page, change a business fact or approve a recommendation from a message, because those need a preview and a record of who approved them. Siteleon reads nothing beyond its own messages, so a decision taken in a thread is not on the customer record until somebody puts it there.
Communication
Others in this group.
Your business online. Built to adapt.
Start with the site you already have, or create something new. Siteleon helps you build it, understand it and keep improving it as the business changes.
No technical setup · Keep your existing site if you want to · [email protected]