Products
Enquiry Desk
See every enquiry in one list, with an owner
enquiry-desk.txtas is → to be
Today an enquiry passes through an inbox, a forward, a spreadsheet, a call and a chase, and is retyped twice on the way. Afterwards it sits in one list with an owner and a reply.Illustrative hours, not a measurement.
An enquiry arrives by form, by email, by phone — and then it depends on who saw it. Enquiry Desk puts every one of them in a single list, gives it a person, and shows what happened last. Nothing is retyped, and nothing waits unnoticed.
Enquiries stop being retyped and none of them waits in an inbox for somebody to notice it: every one is in a single list, has a person against it, and shows what happened last.
How it runs
- one list holding every enquiry, whatever route it came by
- the enquiry arrives with the details needed to answer it
- an owner and a next step on each one
- the history of what was said, next to the enquiry
- the stages named the way the business names them
- a reminder when nobody has replied
Where it does not fit
- businesses with so few enquiries that a shared inbox genuinely suffices
- sensitive or confidential requests
- incomplete submissions needing a human read
- decisions requiring judgement, not routing
- sales that live inside a customer portal we do not control
Size: a medium piece of work — an estimate from the pattern, not from your business.
What we would want to know before committing
- where enquiries arrive today, all the routes, and how many a month
- what happens after one is submitted today
- who owns an enquiry once it arrives, and who should see which
- the stages an enquiry actually passes through here
- what counts as closed, won and lost
- destination system, if any
- count how many enquiries a month actually arrive
- measure current handling time per enquiry
- agree the stages, and the lead fields that must be captured, before building any of them
- confirm who is allowed to see what
- confirm integration access to the destination system