The 20–50 truck reality
This is the band where inconsistency starts costing money. Two dispatchers quote the same lane differently. A customs packet waits in whoever's-inbox-it-landed-in. New hires take months to absorb lane knowledge the desk already paid for.
Drafts grounded in the workspace's shared lane history give every dispatcher the same starting point — the junior's draft cites the same routes the senior would have checked.
What matters at this size
- Team access with real scoping: assignment-based visibility, capability-gated agent chat, and per-user language settings.
- Document throughput: packets assemble, extract, screen, and file continuously instead of queueing on one person.
- Telegram approvals keep managers unblocked when they are away from the desk.
- Run history and stats show quoting performance per period, so managing by evidence replaces managing by anecdote.
Scaling without re-platforming
Multiple inboxes can feed the same workspace, and each inbox's runs stay attributable. Fleet tracking, deal watching, and document intake all attach to the same workspace spine, so adding a capability is a toggle rather than a new vendor.
Frequently asked questions
Can different team members work in different languages?
Yes. Dashboard language and the agent's internal analysis language are per-user settings; client replies always follow the client's detected language.
How do we keep a junior from sending a bad AI draft?
The draft gate means every send is a deliberate act, and run history records what was sent versus drafted. Managers review edits and pricing stats over time.