A customer may use a website form, telephone, email, messenger or a recommendation. The customer sees one company, but internally those conversations are often spread across personal phones, chats, inboxes and spreadsheets. Some never enter a system, some receive a late response, and the owner sees only completed sales.
A common enquiry system is not a contact archive. Its purpose is to ensure every relevant enquiry has an owner, a meaningful first response and a recorded next action.
Define what counts as an enquiry
Not every message is a sales opportunity. Define minimum criteria: there is a contact or reply channel, the subject of interest is understood and a real product or service need exists.
| Event | Classification | Action |
|---|---|---|
| Customer asks about price or availability | New enquiry | Create a record, owner and response deadline |
| Message about an active order | Continuation of an existing deal | Add it to history without duplicating the customer |
| Spam or a supplier offer | Non-sales contact | Close with a separate reason |
| Existing customer's support question | Service request | Route to the service process and retain the customer link |
Without one rule, one adviser creates a deal for every message while another records only confirmed orders. Reports cannot be compared.
Create one intake without forcing customers into one channel
Customers should not be required to use one website form. Instead, every channel should create a record in a shared queue, or staff should be able to do so in seconds during a call.
- the website passes the contact, source, page and message;
- email creates a new enquiry or attaches to an existing one;
- a messenger sends a new conversation into the queue;
- a telephone call creates a card manually or through integration;
- an offline enquiry records “shop”, “event” or “referral” as its source.
Minimum fields for a new enquiry
| Field | Purpose | Rule |
|---|---|---|
| Date and exact time | Measure response speed | Created automatically |
| Channel and source | Assess marketing and traffic quality | Channel is not confused with campaign |
| Contact | Reply and identify possible duplicates | Telephone or email is normalised |
| Subject of interest | Route to the right adviser | Short factual summary |
| Owner | Personal accountability | Assigned immediately by a rule |
| First-response deadline | Prevent silent loss | Depends on channel and working hours |
| Next action | Continue after initial contact | Has a date, type and performer |
Do not overload the initial record with information the adviser cannot yet know. Add details during qualification.
Separate three time measures
- Time to acceptance — from creation until assignment or acceptance by an adviser.
- Time to meaningful first response — until a reply genuinely moves the enquiry forward, not an automatic acknowledgement.
- Time to next step — until the agreed call, quotation, invoice or other action.
An automatic “we received your message” is useful to the customer but must not be reported as sales work.
Assign an accountable owner
Distribution must be predictable: product group, region, language, customer type, current workload or round-robin queue. Include employee absence and a maximum acceptance time.
If an adviser does not accept the enquiry, the system should remind, reassign or escalate it. A notification with no follow-up action does not solve the problem.
Prevent duplicate deals
The same customer may submit a form, then call and use chat. Three separate deals create internal conflict and distort conversion. Check a normalised telephone number, email, active deals and recent enquiries.
A match is not always a duplicate because the customer may have a new independent need. Suggest a relationship rather than merging records blindly.
Example control queue
| State | Control | Manager action |
|---|---|---|
| New without owner | No more than five working minutes | Check the distribution rule |
| Accepted without first response | Channel-specific deadline | Investigate the delay |
| Contact made, no next action | Immediately after conversation | Return for planning |
| Next action overdue | Separate overdue queue | Recover contact or close with a reason |
| Closed without reason | Completion blocked | Record a verifiable reason |
Measures for the owner
- relevant enquiries by channel;
- share without an owner;
- median first-response time;
- share of overdue next actions;
- conversion from enquiry to qualified opportunity;
- duplicates and repeat contacts;
- reasons for closing without a sale.
An average can hide a small number of very long delays, so also use the median and the share outside the service target.
Common mistakes
- Keeping enquiries in personal chats. The company loses the history when access changes.
- Creating a record only after a sale. Lost demand cannot be measured.
- Counting an auto-reply as an adviser response. The customer receives no solution.
- Leaving no next action. A card exists but the sale has stopped.
- Using one target for every channel. Chat and email expectations differ.
- Closing with “did not buy”. The business learns nothing actionable.
Enquiry control in Business Reactor
Business Reactor Core connects the customer, source, owner, status, next action and order in one environment. This removes the gap between recording an enquiry and ensuring it actually progresses.
Once intake is controlled, define sales stages. A stage must represent an achieved result and determine the next work, not store an adviser's subjective comment.
Conclusion
Bring every channel into one controlled queue, define a relevant enquiry, assign an owner immediately and never leave a record without a next action. Measure meaningful response time and overdue work, not just the number of cards.
The next step is a pipeline whose stages reflect real progress with the customer. Business Reactor Core.
