KENYA · GUIDE 0537 · EDITION 4.2
Lead enquiry tracking setup in Kenya: Operations and Quality Checks
Deliver the agreed result consistently
Set up enquiry tracking around the team's actual handover process, agreeing enquiry sources, responsible staff, status meanings, follow-up dates, and the minimum customer information worth retaining.
The operating sequence for this offer is:
- Define the enquiry stages, minimum necessary fields and follow-up authority, then approve access and retention rules before using real customer information.
- Configure and test status changes, duplicate handling and reminders using fictional enquiries, then train authorized staff on the agreed process.
- Reconcile pilot records with the owner, document unresolved cases and hand over a repeatable review and correction routine.
Put acceptance into the job record
Enquiries can be traced without collecting unnecessary personal details.
Give staff fictional enquiries covering duplicates, missed calls, and a lost sale, then confirm they can assign ownership and find the next action without extra explanations.
Inspect at the point where a correction is still possible, then again at handover. Record rejected or incomplete output separately from accepted output. A completed task is not automatically an accepted task, and an invoice does not establish that the customer received the right result.
Measure real capacity
Time preparation, the main operation, transport, cleaning, approvals and correction as applicable. The slowest stage determines how much you can promise. Where two orders need the same person, space or equipment at the same time, resolve the conflict before confirming both deadlines. An additional enquiry should not erase a commitment already made.
| Operating checkpoint | Evidence for this business |
|---|---|
| Before starting | Set up enquiry tracking around the team's actual handover process, agreeing enquiry sources, responsible staff, status meanings, follow-up dates, and the minimum customer information worth retaining. |
| During delivery | Configure and test status changes, duplicate handling and reminders using fictional enquiries, then train authorized staff on the agreed process. |
| At acceptance | Give staff fictional enquiries covering duplicates, missed calls, and a lost sale, then confirm they can assign ownership and find the next action without extra explanations. |
| At the pilot review | Keep test cases, duplicate decisions, user misunderstandings, overdue follow-ups, access checks, staff adoption observations, and changes made to make the next customer action clearer during onboarding. |
Keep a correction and escalation rule
When inputs, access, specifications or customer instructions change, pause the affected work and confirm the effect on time and cost. Do not quietly lower the acceptance standard to avoid a delayed delivery. Keep rework caused by your error distinct from a customer-requested change of scope and agree the remedy clearly.
A tracker becomes an unused spreadsheet when nobody owns follow-up or staff interpret the same status differently, making apparent enquiry totals unreliable for business decisions later.
Retain the minimum records needed to investigate a complaint without disclosing unrelated personal information. Use measured delivery and actual acceptance as the basis for expanding capacity, rather than the maximum theoretical output of a tool or production line.
Operating control points for this exact offer
| Sequence | Work method | Release checkpoint |
|---|---|---|
| 1 | Agree unique IDs and whether repeat messages refer to one request or a new job. | Twenty messages are not assumed to be twenty prospective buyers. |
| 2 | Use received date, source, request summary, assigned staff, status, next action and due date. | Each status has a definition; 'won' requires a client-defined confirmed sale event. |
| 3 | Keep the supplied export unchanged, normalise dates in a working copy and preserve original reference links. | Reconcile twenty source enquiries against imported unique IDs and list excluded duplicates. |
| 4 | Add validated status choices and a filter for open actions due before the review date. | Closed rows are excluded from overdue work; blank dates are flagged as missing rather than treated as zero. |
| 5 | Have staff add an enquiry, assign it, change status and close it with a reason. | A second authorised user can follow the next action without private notes or verbal explanation. |
Do not substitute a tick for an observation: record the count, measurement, approved sample or evidence reference used at each checkpoint. Mark unresolved work as held and identify who can approve the recheck.
Diagnose a failure before repeating it
| Observed symptom to investigate | Check the cause | Proposed response |
|---|---|---|
| Same buyer counted several times | Compare original message references and request identity. | Link follow-ups to the existing enquiry while retaining evidence. |
| Overdue view shows completed jobs | Check status filter and date types. | Correct the filter and test one open, one closed and one undated row. |
| Staff leave next action blank | Inspect whether status implies a clear task. | Add a visible missing-action flag and revise the handover rule. |
These are diagnostic prompts, not proof of the cause in a real incident. Separate suspect output, record any correction and repeat the relevant acceptance check. Link rejected units, rework time, replacement materials, customer credits and collection delays to the actual job result.