Most advice on AI for customer support assumes the customer is one person with one question. In a shared Slack channel the customer is a company: a champion, a finance approver, a procurement contact, sometimes a reseller, all reading the same thread. A wrong answer does not stay with the person who asked. Everyone who can see the channel reads it, and it can come back to you at renewal. The rules below assume that.
One wrong answer reaches the whole buying committee
Slack’s developer guide says all workspaces involved in a connected channel can read and send messages. So a line the AI posts about a credit or a price is visible to every person on the customer side who is in that channel, including people who never asked the question.
Worked example: an account has six people in its channel. The AI tells the champion that the contract includes a service credit that the order form does not contain. The champion forwards it to procurement, who checks it against the signed order form. Now you have a commercial dispute that started with a reply written in two minutes.
The working rule: treat every AI reply in a shared channel as a published statement from your company to the whole customer side, not a private answer to one person. If a draft contains a gated class (listed below), hold it for review, whatever the number of customer members in the channel. A wrong figure still lands in the contract record, and the one person in the channel can forward it. A single-person channel is a defensible place for a fast reply without a check only for statements outside the gated classes. Price, credit, SLA and other gated statements still go to an approver.
Answers must match this account’s contract
Two customers on the same plan can have different terms: a negotiated per-seat price, an SLA addendum, a renewal date that does not match the standard. A general help center cannot know this, so the AI should not answer from it when a contract question comes in.
Put the contract facts on the account record, not in the article library:
- Plan, seat count, per-seat price and any discount, with the date each was set.
- SLA tier and response targets, with the ID of the signed document.
- Renewal date and notice period.
- The version of the order form or addendum that holds each of these.
The AI may cite only those fields and those documents. If a field is blank for an account, its default is to say it doesn’t know and hand off. It should never fall back to the list price or the standard SLA.
Exact wording for a blank field: “I can’t confirm that from your account terms here. I’ve sent it to [name], who will reply in this thread by [time].”
Account-level permissions
There are three boundaries, and the first one fails most often.
- Retrieval is scoped by the channel’s account link, not the message text. If a customer asks “what did the other team ask last quarter?”, the answer must contain nothing from another account. Set the account filter in code from the channel-to-account mapping. Never let the model pick the account from the prompt.
- The AI reads only threads in channels linked to that account. Internal notes and other accounts’ threads are excluded at retrieval, not by an instruction in the prompt. An instruction can be talked around; a missing document cannot.
- Every outbound post checks the account. The send path compares the target channel’s account ID with the account that supplied the source material. A mismatch blocks the send and writes a log entry.
The Slack side of the same boundary is set in the invitation settings:
| Setting | Recommended default | Why |
|---|---|---|
| “Permission only to post” | Most customer members | Customers can post, react, add files and use workflows, but cannot add people or add apps or workflows |
| “Permission to post, invite, and more” | A named sponsor only | Also lets them add people from organizations already in the channel, and add apps and workflows |
| External people in #general or #all-company | Never | Slack does not allow adding external people to these channels |
Slack’s developer guide also says messages from incoming webhooks are visible to all members of a shared channel. An internal alert bot that posts “renewal risk: high” into a customer’s channel is a leak. The rule is that internal bots post only to internal channels, and no webhook reaches a shared channel without review.
Bot users are accessible to all users on the workspace where the app is installed, so keep the app that answers customers separate from any app that reads internal CRM data.
There is one audit gap. As of 2026-11-11, Slack’s developer guide says the conversations.list method does not include connected_team_ids, so you cannot ask Slack which channels are shared with a given organization through that method. Keep your own map of channel ID to account ID, and reconcile it against your list of shared channels on a schedule you can name, such as every Monday.
The review gate for pricing and SLA answers
Classify each draft before it posts. These classes always get a gate:
- Any price, discount, credit, refund or payment term.
- Any response, resolution or uptime commitment.
- Any statement about term, renewal, cancellation or data handling.
- Any “we will” or “you are entitled to” about something the account record does not hold.
The rule: if a draft contains a gated class, it goes to a named approver and does not post. If it contains no gated class and every cited field exists in the account record, it posts.
Worked example: a customer asks, “Can you confirm our renewal price holds at the current rate?” The draft says “Yes, your renewal stays at the current per-seat price.” That is a price and a renewal statement, so it is held. The approver opens the order form, finds that the held price covers one renewal term only, and edits the reply to say so, citing the document version. The customer gets an acknowledgement while they wait: “I’m checking your renewal terms against the order form and will confirm here by [time]. [Name] is reviewing this with me.”
Log five things for every gated reply: the draft text, the field and document version it cited, who approved it, when, and when it posted. Without the citation, a later dispute is a memory contest.
Failure mode: drafts that avoid the keywords. A draft that says “should be fine at the current rate” carries the same commitment. Classify on meaning, and gate any sentence that refers to a number held on the account record.
Slack’s own assistant is not a substitute for this. Slack’s pricing page says the Business+ plan limits Slackbot to “15 messages per user each week”, and that Enterprise+ Slackbot is unlimited for the whole team, as of 2026-11-11. The same page says Slackbot access is changing (“Soon, Slack users across every plan will be able to try Slackbot”), so treat the cap as a current limit, not a fixed one, and check it before you plan a drafting workflow around it.
What to measure
- Gated share per week. The share of replies that hit the gate.
- Change rate. The share of gated drafts the approver edits. If it is above one in five for two weeks running, the AI is reading the wrong field, so fix retrieval before you widen the gate. If it is near zero, check whether approvers are rubber-stamping.
- Gate delay in business hours. Measure it separately from first response time. The gate adds delay, and the customer should see it as a deliberate pause, not silence.
- Errors per account. Count customer-visible errors by account, not by message, because one account with five wrong answers is a different problem from five accounts with one each.
Report AI first responses and human first responses separately, as described in the Slack Connect first response time guide.
Where a product fits
Weft is a support inbox for Slack Connect and email. As of 2026-11-11, it turns each customer message in a shared channel into a thread in one queue, posts replies under the replying person’s own name, and links each customer to an account. Its AI drafting agent is planned, not available, so the account rules and gate above are worth designing now, whichever tool you pick. Its pricing page lists Starter at $39 and Growth at $89 per seat per month in USD list prices before tax, billed annually, with a 14-day Growth trial that needs no card to start.