Your inbound desk, from first message to closed deal
Inquiry catches what customers send you, works out what it is worth, puts it in front of the right person, and keeps score while you work. Email arrives straight into it. WhatsApp, SMS and web-form conversations sit alongside — and you answer all of them from the same place.
Invite-only — your owner sends the invitation.
Five steps, and you only do one of them
Everything except writing the reply happens without anyone asking.
Arrives
A customer writes in. The message is stored exactly as it came before anything reads it, and a duplicate is recognised rather than filed twice.
Understood
It is scored on the way in: how urgent, how qualified, what it is about, and how likely it is to convert.
Routed
It joins the right team's queue. An agent takes the next one — and two people pulling at the same moment never land on the same inquiry.
Answered
The reply is saved the moment it is written, then sent by email, WhatsApp or SMS, threaded back into the customer's own conversation.
Measured
Volume, response time, conversion and risk move behind it. Nobody maintains a spreadsheet.
Six places to work, not six tools to buy
Each one is a tab away from the others, over the same history.
Inquiries
Every message, narrowed by channel, status, agent, missed SLA or attachment. Open one and you get the whole thread, who touched it, and what they did to it.
Teams & queues
Group work by channel and topic — the WhatsApp complaints desk, the sales queue. Members pull the next item, and the top bar tells them how much is waiting.
Leads
Everyone who writes in becomes a lead, matched across email and phone so the same person is one record, moving through new, contacted, qualified, won and lost.
Agents & roles
Invite colleagues, grant and revoke roles, and see load per person: assigned, open, resolved, missed SLAs and a fortnight of trend.
Dashboard
A daily snapshot and nine tabs — including an assist queue that floats the twenty inquiries most worth your attention to the top.
Pipeline
The machinery in the open: what ran, how long it took, and what failed in the last twenty-four hours.
Built so the bad day is survivable
Most of what follows only matters when something goes wrong — which is exactly when a desk earns its keep.
Saved before it is understood
The original message is written down first and interpreted second. If anything trips while reading it, the message is still sitting there.
A reply outlives the mail server
What an agent types is kept the instant they send it, and delivered as a separate step. An outage at the provider delays the answer. It never eats it.
Two agents, one queue, no double work
Taking the next inquiry locks it to whoever reached it first. Everybody else gets the next one down — not an error, and not the same customer answered twice.
Every change has a name on it
Claims, forwards, reassignments and status moves are recorded with the work itself. The history you read is the record, not a reconstruction of it.
A score you can argue with
Scoring is a published, versioned ruleset rather than a black box. The same message scores the same way every time, and a new version writes a new result instead of quietly rewriting last quarter's.
Seven roles that match how desks actually work
Triage, responder, closer, analyst and more. Hold two roles and you see both queues, not the narrower one. Owners can drop into an agent's view and see exactly what that agent sees.
Where it sits
Measured against the three things teams usually reach for instead.
| Capability | Shared inbox | Generic helpdesk | CRM | Inquiry |
|---|---|---|---|---|
| Threaded conversations | Partial | Yes | No | Yes |
| Queues two people can pull from | No | Yes | No | Yes |
| Lead pipeline attached | No | No | Yes | Yes |
| Scored as it arrives | No | No | Partial | Yes |
| Full audit trail | No | Partial | Partial | Yes |
| Self-hosted, your data | No | No | No | Yes |
Seven families of numbers, kept up as the work happens
Nothing is exported and nothing is entered by hand. First response is held to a four-hour target, and anything that slips past it is marked on the inquiry itself — so a missed one is a filter, not an audit.
Give people exactly the desk they need
Roles are granted and revoked by the owner, and the grant is checked on every request — take one away and it stops applying immediately.
| Owner | Runs the platform. Everything, including granting roles. |
|---|---|
| Supervisor | Sees the whole desk and can route work, but cannot change roles. |
| General agent | Handles their own queue end to end: pick up, reply, forward, close. |
| Triage | Works the unassigned pool and routes it to the right agent. |
| Responder | Answers inquiries in their queues, and can hand them on. |
| Closer | Resolves and closes inquiries in their queues. |
| Analyst | Read-only: sees everything and the metrics, changes nothing. |
Sign in to your desk
Inquiry is invite-only. If your team already runs it, your owner has sent you a link — and if you are the owner, the first account is yours.
Sign in