Why it matters
It is the first step for any support team and the one that changes day-to-day work most.
Without it there is no way to know how many questions are outstanding, no way to split the work, and every absence blocks whatever that person had half-finished. Above all, it makes the work visible.
What separates it from an email alias
An alias distributes copies; a shared inbox assigns responsibility.
With an alias, two people answer the same thing or nobody answers anything, and both situations show up in the first week.
The rule that makes it work
Every conversation either has an owner or is unassigned, and no intermediate status means "somebody is probably looking at it".
The moment there is a grey area, that grey area fills up.
How to set one up
It can be running in an afternoon.
- Connect the email addresses and the channels customers already use.
- Create the teams and decide who sees what.
- Agree the rule that every conversation has an owner or is unassigned.
- Write saved replies for the ten most repeated questions.
- Set response targets by priority or by channel.
- Check the unassigned view every day.
When it stops being enough
When most replies need data living in another tool.
At that point the bottleneck stops being organization and becomes the distance between the conversation and the data.
The Intake inbox
It brings website chat, email, WhatsApp and Slack into one list.
The AI sets the topic and picks the team, and each team assigns by hand, in turns or to whoever has the fewest open conversations. Next to every conversation sit the customer’s data and what the AI agent already checked, and the agent resolves first whatever does not need a person.
