B2B customer support is the help a company gives the businesses that buy from it. The unit of work is the account, not the person who wrote in, because an account has several contacts, a contract with response times and often a shared Slack channel. For the Slack side, see the Slack Connect support guide.
How B2B support differs from B2C
- The account is the unit. One engineer’s question belongs to an account that may have six people across support, finance and operations. Show every open thread beside the renewal date.
- The contract sets the clock. First response time runs from the customer’s message to the first reply from someone who can act on it. Time to resolution runs until the problem is fixed. Write both into the service level agreement per priority.
- Shared channels need access rules. Slack’s Help Center says people can only reach channels they were invited to, and admins can restrict who invites external people. On Pro and Business+, Admins and members with permission can enable additional organizations.
Support models and plan check
- Ticket inbox: email or a web form, one owner per thread. The customer has to leave Slack.
- Shared Slack channel: the customer posts where they already work, but nothing shows which message is still unanswered.
- Hybrid: every customer message in a shared channel becomes a tracked thread, and replies return to Slack. Weft works this way, posting replies under the replying person’s own name.
- Plan check: on Free, Slack Connect is “1:1 only”, so a shared customer channel needs Pro or higher. As of 2026, Pro is $7.25 USD per user per month when paying annually.
Clock rules worth copying
- Several contacts, one clock. The clock starts at the first question from any contact, and other contacts’ messages do not restart it. Assign one owner within 15 minutes and say so in the thread.
- Resolved means confirmed. Close it when the customer confirms the fix. If they go quiet, ask “Does this fix it for your whole account, or only one workspace?” and close it after 3 business days of silence. A reply is not a resolution.
- AI replies. Label each agent reply with the agent’s name and time. An auto-reply such as “We got your message” does not stop the clock; a reply that answers or asks a question does. Review 20 random threads a week.
- Breach. With 30 minutes left on a 2-hour promise and no reply, notify the owner. At zero, mark the thread breached, and record the credit or escalation decision with its date.
Worked example: the promise is 2 business hours, Monday to Friday 09:00 to 17:00. A customer posts at 16:30 on Friday. Friday contributes 30 minutes, Monday starts at 09:00, and a reply at 10:00 adds 60 business minutes. That is 90 business minutes, inside 120. A clock started at the reply would show zero. On the wall clock, the same wait is 65.5 hours.
The common mistake
Treating the shared channel as the support system. A bare channel shows neither ownership nor how long anyone waited, so questions get answered twice or never. Escalate an account with three or more open threads and a renewal within 60 days to its owner, and log the call as a dated account note.