SellBot now has real team queues and inbox metrics
The storefront assistant should not be the end of the product. Once AI has done its part, the hard conversations need to land with the right people, in the right queue, with clear ownership. That is what the new team features are for.
Queues
Team routes
Each team can work from its own queue instead of sharing one mixed inbox.
Assignment
Auto assign
Least-loaded eligible operator wins when the team allows automatic assignment.
Views
Route state
Saved views now carry real search, sort, and filter state into the URL.
Metrics
Reply pace
Team-level unresolved load and average first reply time are visible in the panel.
Dedicated team queues
Each team now has its own queue route, so support, sales, or operations can work from a clean slice instead of fighting one global inbox.
Team-aware auto assignment
When auto-assign is enabled, new team work can land with the least-loaded eligible operator instead of sitting unowned.
Saved views with real route state
Search, sort, and filter presets now behave like real navigable queue views instead of hidden server-side filters.
Operational metrics
Unresolved load, unassigned work, pending volume, resolved volume, and average first reply time are visible at the team level.
Why this matters
AI handoff is only good if the next owner is obvious
Most AI chat products stop at the answer. The harder problem starts after that: who owns the conversation when the shopper asks for an exception, wants a quote, needs post-purchase help, or simply needs a human to close the last 10 percent?
Team queues fix that by moving SellBot from a storefront feature into an actual operating surface. The assistant gets the shopper moving. The team layer makes sure the expensive conversations do not fall into a shared bucket that nobody owns.
AI gets the shopper moving
SellBot answers the first layer of questions, recommends products, and keeps the path to purchase fast while intent is high.
Humans take over when the conversation turns expensive
When the shopper needs a judgment call, an exception, or real account help, the conversation can be handled in inbox instead of disappearing into email.
Teams keep ownership clean
Sales can own pre-purchase deal flow, support can own post-purchase issues, and operations can own the edge cases that usually create internal confusion.
What shipped
The team layer is not just labels
We did not stop at a cosmetic team tag. The inbox now has first-class team records, team members, team assignment on conversations, dedicated routes for team queues, and metrics that let operators see where response pressure is building.
That means teams can own their work in a way that looks much closer to a real support or revenue workflow instead of a flat list of mixed conversations.
Practical outcomes
- Less queue drift because ownership is explicit.
- Faster first responses because unresolved and pending load are visible by team.
- Cleaner escalation because the AI layer and operator layer now connect inside one product.
- Better reuse because notes, macros, labels, and saved views sit next to team routing instead of outside it.
Next step
If your AI assistant is going to escalate, the inbox has to be part of the product
That is the direction SellBot is moving in now: storefront answers, live configuration, approved policy sync, and a real team-operated inbox behind the scenes.