Skip to content
Shared inbox

One shared inbox for website conversations

Website chat lands in one inbox your team can read together, with unread state, attachments, and tickets. Unlimited teammates on the published plans.

tkit.ai social card for live chat, an AI teammate, and a shared inbox
Conversations and tickets in the same workspace inbox
Unlimited teammates on Starter, Growth, and Scale
Separate workspaces for products, brands, or clients

A place the whole team can see

Details about A place the whole team can see

The inbox is the dashboard view of website chat. A visitor message arrives in real time, marked unread, with the conversation attached. Anyone you invite can open it. The published Starter, Growth, and Scale plans list unlimited teammates and do not add a per-seat price. Those prices are indicative, and there is no online checkout.

A shared Slack channel can hold the same words, and it also holds launch notes, deploys, and jokes. The inbox is only the customer thread. That separation is the reason to use it. The essay on a shared inbox instead of a shared channel goes further into the habit, including what still belongs in chat.

Conversations and tickets

Details about Conversations and tickets

You can keep reading a conversation or raise it as a support ticket. Tickets have statuses the team can move, including open, resolved, and closed. The monthly ticket numbers on each plan are indicative limits, not something you buy from a checkout on this site. If you are unsure about volume, write with a rough count of new conversations.

Attachments stay on the thread. Unread state tells you what nobody has opened. None of that replaces a decision about who answers first. First reply time is still a clock you can measure yourself. The calculator on this site uses times you type and does not connect to the inbox.

Workspaces keep products apart

Details about Workspaces keep products apart

A workspace is a boundary for a product, a brand, or a client. Each workspace has its own members, widgets, and inbox. A company with two products should not train one widget on both and hope the greeting makes sense. The workspaces guide describes how to split them without losing the thread.

Inside a workspace you can run more than one widget. That is useful when the marketing site and the logged-in app should look different, or when a wildcard domain and a docs host need separate greetings. Allowed domains still decide where each snippet loads.

What the inbox does not try to be

Details about What the inbox does not try to be

It is not a shared email client, a social inbox, or a phone system. Messages start from the website widget. If your team also answers email, that mail stays in whatever tool you already use. The support templates are drafts you copy into email or chat. They are not sent from this inbox.

Tee can reply before a person does, using the notes on that widget. The inbox is still where a teammate continues the thread, pauses Tee for one conversation, or turns Tee off. Read AI website chat for that switch, and the live chat widget page for the snippet that feeds this inbox.

Bring support closer to your product

Install the widget, invite your team, and review every reply before it reaches a customer.

Get started