A customer phones about a repair. Someone else emails for a quotation. A visitor leaves details at reception, then sends the missing model number on WhatsApp. By the afternoon, the team needs to know what each person is waiting for and who will respond.
Start with a routine the team can use in its existing tools. A small shared register may be enough. The useful result is a colleague being able to answer three questions: what does this customer need, who is handling it, and what happens next?
Bring the request together across channels
At the first contact, write a short description in the customer’s terms. “Needs a written quote for a replacement printer before a planning meeting” is more useful than “Printer enquiry”. Capture the contact route they want you to use and the date they need an answer, where they have one.
If the same person later phones or sends another message about that request, update the existing record after checking that it is the same enquiry. A new, unrelated job needs its own record. Do not combine customers just because their names look similar.
| Field | What to record | Why it helps at handover |
|---|---|---|
| Reference and received time | A short unique reference, date and channel | Find the request again and distinguish separate jobs |
| Customer need | The requested result, relevant details and original-message link | Continue with the context already available |
| Contact route | The agreed way to reply and the details needed to do so | Reach the customer through the intended channel |
| Owner and cover | The person responsible, plus a cover arrangement when needed | Know who is taking the next step |
| Next action and due time | A specific task, its owner and an agreed checkpoint | Distinguish an active plan from a vague reminder |
| Status and evidence | Current position, last action and a link or note showing what happened | Review progress and explain a closure |
Use a short summary rather than copying every attachment into another location. Keep customer details in the tools your business has approved for that work, with access for the people who need them. This register is an operational aid; it does not establish your legal retention or privacy requirements.
Give the next action to a person
Agree who owns each request before it leaves the intake stage. That person does not have to perform every task. They are responsible for checking the next step and making the handover clear when someone else needs to act.
Replace “sales to follow up” with “A designated sales colleague will check the required paper size and send the questions to the customer by the agreed checkpoint”. If the person who can approve a quotation is unavailable, record who will cover or when the customer will receive an update. Do not promise a delivery date or service response that has not been confirmed.
For a handover, the receiving colleague should acknowledge that they have taken responsibility. Until that happens, the current owner should keep the request visible. Moving a message to another folder is not, by itself, evidence that someone has picked it up.
Separate “waiting” from “finished”
Choose a few statuses the team understands. For example: new, in progress, waiting for customer, waiting internally and closed. Agree what each means before using it in a report.
A request waiting for a model number still needs an owner and a review date. A quotation sent to the customer may complete one action while leaving the enquiry open for an agreed follow-up. Close a request when the team’s defined endpoint is reached, and note why: answered, order confirmed, customer declined, duplicate linked to the main record, or no further contact after the agreed follow-up process.
Start priorities with the customer’s stated need and the effect of delay. An office unable to print essential documents may need a different route from a future equipment comparison. Route urgent faults, complaints and commitments to the appropriate person; do not make an unapproved quotation or technical decision just to clear the queue.
Use a review that ends with actions
At a time the team can sustain, review new requests, unassigned work, actions due and requests waiting on someone. For each exception, make a decision: complete the action, ask for the missing detail, transfer ownership with acknowledgement, or agree a new checkpoint and explain the change.
Keep the original due time visible when a task moves. Otherwise, repeatedly changing the date can make an overdue request look healthy without helping the customer. Where an expectation changes, tell the customer what is now known and when they will hear from you again.
A worked review across four channels
Illustrative example — fictional requests, roles and times; no customer results or service-time commitments. A small office reviews the following register on Tuesday morning:
| Request | Current position | Decision and next checkpoint |
|---|---|---|
| E-101 · Email quotation request | Sales owner needs the required paper size | Ask the customer for that detail; owner checks for a reply at the agreed afternoon review |
| E-102 · Phone repair enquiry | Reception recorded the fault; no technical owner has accepted it | Reception gets an appropriate colleague to accept the handover and confirms the next contact arrangement |
| E-103 · Walk-in consumables enquiry, later updated on WhatsApp | The model number is now available in the original conversation | Update E-103, link the message and ask the owner to verify the exact item and availability before quoting |
| E-104 · WhatsApp follow-up on a sent quotation | The customer has asked a question about installation | Return to in progress; quotation owner obtains an approved answer and agrees when to reply |
The review produces four explicit next steps. It does not establish four sales, four resolved enquiries or any measured saving. The team still needs to carry out the actions and record what happened.
Keep the existing method when it does the job
If a shared register already gives your small team reliable ownership and follow-up, improve that routine before adding another system. Check that colleagues can find the latest entry and use it when someone is absent.
Consider a more structured inbox or customer-management tool when the current method makes assignments, access, history or reminders difficult to manage. Test a representative enquiry through intake, transfer, absence cover and closure before choosing. Confirm how each channel is handled; a shared email inbox does not automatically capture telephone calls, walk-ins or WhatsApp.
For one email-specific example, Google’s Collaborative Inbox supports taking or assigning conversations and marking them complete, subject to the appropriate permissions. See Google’s assignment and completion guidance. Those features illustrate ownership within that tool; they do not prove that every channel or system is connected.
Measure completed follow-ups before claiming a result
For a defined review period, count the follow-up actions due, those completed by the original due time, those still overdue and those rescheduled. Record who checks the evidence. Track the reason for waiting separately so the team can see whether it needs a customer detail, internal approval or clearer ownership.
For example, if 8 of 10 actions due in the period were completed by their original checkpoint, that is 80% of those actions completed on time. It is not an 80% sales conversion rate. Keep enquiries, actions, quotations and confirmed orders as separate measures. A completed reminder is useful evidence of work done; it is not proof of revenue.
Use the follow-up record with your next request
Download the enquiry and handover record or start with the blank register headings. Agree one owner, one next action and a checkpoint before you expand the process.
If the team can describe where requests stall but needs help fitting the workflow to its systems, contact BusiQuip with one example of the handover you want to improve. Describe the channels you use, who handles the request and where it currently gets stuck. Scope, connections and costs need to be confirmed for your business.
For the WhatsApp intake stage specifically, read our guide to WhatsApp reception and team follow-up.






