Giving every enquiry one owner
An illustrative account of enquiries from calls, whatsapp and email go onto one register with a name against each.
This story shows a practical response to enquiries from calls, whatsapp and email go onto one register with a name against each.
Before
In this industrial valves business with about 40 people, the issue is enquiries from calls, whatsapp and email go onto one register with a name against each. The trouble appears first at the hand-off, before the monthly report can reveal it. The routine depends on the sales coordinator knowing which call, slip or instruction matters. Records exist in missed call list, sales mailbox and WhatsApp enquiries, but another person cannot reliably reconstruct the decision. This is the problem behind giving every enquiry one owner.
A request arrives and somebody responds to the loudest part first. The original source is left in a folder or WhatsApp chat. Later, when the sales manager needs to review it, people reconstruct what happened from memory. The missing piece is often customer name, drawing or item, quantity, requested date and next contact. By the time it is found, another person has already acted on an assumption.
The cost is visible as interrupted work, repeated checking or a promise that needs correcting. No saving or improvement figure is claimed here. The point is to change one repeatable action so that the next case can be handled without a chain of calls.
Why it was like that
The previous method relies on informal permission and experience. Staff may understand the right thing to do, but not where to record it or who can approve an exception. Adding a shared spreadsheet without clarifying authority would leave the same bottleneck in place.
In this example, the control that is missing is no enquiry is marked complete until the next action and its owner are written down. An urgent request can legitimately break the normal rule. The exception still needs a named decision-maker, a reason and a source reference. Otherwise the exception becomes the usual way of working.
The change
The replacement is a one-page enquiry register. Give every new enquiry an ID and named sales owner. This is the required check before an instruction moves to the next person. Set next action at capture. Finally, review unowned lines daily. Each line retains the evidence needed if the decision is challenged later.
Copyable rule for this team
Example register rows, for illustration only:
| Reference | Source | Required action | Owner | Status |
|---|---|---|---|---|
| S049-01 | enquiry register | Give every new enquiry an ID and named sales owner | owner | Open |
| S049-02 | enquiry number and the source message | set next action at capture | sales manager | Check |
The owner can set a sample limit, but it should be based on actual financial exposure, not copied from another firm. A rule that touches statutory dues, credit, worker pay or electrical safety also needs a qualified reviewer.
After
In the revised composite routine, the first person records the incoming request once. Another team member can see its source, status and next action without recontacting everybody. The sales manager sees only the cases needing judgement. Routine cases move under written delegated authority.
For the specific case in this article, the first visible change is give every new enquiry an id and named sales owner. The next person can then set next action at capture. At the end, review unowned lines daily. That sequence matters because each part leaves a record that the next role can verify.
A weekly check samples a few entries rather than trusting the tick column. The manager looks for cases marked closed without supporting evidence, repeat exceptions and requests that still depend on the owner. Those are reasons to revise the rule.
What to watch out for
- Staff may start filling the register after the event. Check the time and reference against the source.
- The authorised manager may approve an exception by phone and forget to record it. Ask for the decision to be added to the same entry.
- The team may treat every request as urgent. Compare actual deadlines and commercial or safety effects before changing priority.
Separate a new enquiry from a confirmed order. An unanswered question about the specification must remain visible.
Copy it
Use the table above as a starting point. Replace the example entries with two current cases. Mark unclear evidence as Open, then name the next person to check it. Keep the source record, owner, next review date and reason for any override. An example exposure of ₹18,500 or 8 units is illustrative only; set limits from your own business records.
Start with Enquiry register. If you need the full sequence, use Daily enquiry review. Measure open exceptions and missed commitments for four reviews before deciding whether the change holds.
Read next
- Enquiries not followed up
- Daily enquiry review
- Enquiry register
