A shared inbox instead of Slack

A shared Slack channel works until the customer thread and the team thread are the same scroll. Deploys, jokes, and a billing question from the website sit in one history. Someone reacts with a check mark. A week later nobody can say whether the customer got an answer.

A shared inbox is a narrower tool. On tkit.ai it is the place website chat goes: unread conversations, attachments, and tickets. Slack can stay the place the team talks to itself. This note is about that split, not about replacing chat.

What gets lost in the channel

The failure mode is not “Slack is bad.” It is that a channel has no single unread state for a customer. Three people can see a message, each assuming another person has it. The message is then both seen and unanswered.

Search makes this worse. The words you need are next to an incident thread from the same afternoon. You can find them, and you can also miss them. A new teammate reading the channel for context reads everything else too.

If the volume is a few messages a week and the same person always answers, a channel is honest. Write that person's name in the topic and keep going. Move the work when a second person starts answering, or when a message can sit for a day without anyone being sure.

What the inbox is for

The shared inbox receives the widget conversation. It shows what is unread. A teammate replies there, and the visitor sees that reply in the widget. You can raise the conversation as a ticket and set a status such as open, resolved, or closed.

That is enough structure for a small team. It is not a status meeting. The useful habit is: if a customer is waiting, the thread is in the inbox, and one person is on it. Internal debate about the answer can still happen in Slack. Paste the conclusion back into the inbox so the customer is not waiting on a channel they cannot see.

The published plans list unlimited teammates on Starter, Growth, and Scale, so inviting the second person is not a new per-seat line. Those prices are indicative, and pricing is not a checkout.

What should stay in Slack

Incident coordination, release notes, hiring, and “is this a bug or a misunderstanding?” belong in the team channel. So does a draft you are not ready to send. The inbox is a bad place to think out loud, because the reply box is aimed at the visitor.

Also keep email in your mail client. The inbox does not collect the company Gmail. If a customer writes both places, answer both, and do not expect one tool to merge them. The support templates are drafts you can paste into either.

A simple handoff

1. The widget message arrives unread.
2. The person on coverage opens it and either replies or says in Slack, “I have the billing thread, need a yes on the refund.”
3. The decision comes back in Slack. The customer-facing sentence is typed in the inbox.
4. If the work will outlast the shift, raise a ticket and leave the status honest.

Coverage is a schedule, not a feature flag. If nobody is on the inbox after 18:00, the greeting should say so. A fast channel during the day and a silent widget at night is how first reply time gets a long tail. You can add the timestamps you already have to the first reply time calculator. It will not read Slack or the inbox for you.

Workspaces, not one more channel

If two products share a Slack workspace, they often share a support channel too. The messages are distinguishable only by the customer saying the product name. A tkit.ai workspace is a separate inbox, widget, and member list for a product, brand, or client. The workspaces guide is the longer version. Use it before you add #support-2.

When not to bother

Do not add an inbox because a blog post said channels decay. If one founder answers from a personal DM and the volume is tiny, another login is friction. Revisit when you cannot tell, from the channel alone, which customer is still waiting.

The widget side of this is the live chat widget. Install steps are in the install guide. Until that script is on an allowed domain, the inbox has nothing to show.