One enquiry. Seven hidden jobs.

Look beyond the first reply

An enquiry arrives: someone is interested in a property, a vehicle or a service. A quick response can be useful, but it does not tell you whether the request reaches the right person with enough context to act. A conversational interface can look successful while the operational work behind it remains unfinished.

The seven jobs below are an illustrative way to map a common enquiry flow, not a universal sequence or a performance claim. Your business may combine them, split them or require additional controls. The exercise is to make the work after the message visible.

1–2. Capture the enquiry and understand the request

First, preserve the request in the agreed system with its source and time. Check whether it belongs to an existing contact. Avoid creating a second record merely because the same person used another channel. When identity is uncertain, flag that uncertainty rather than merging records confidently.

Second, determine what the person is asking for. A question about availability differs from a complaint or a request to change an appointment. The right next step depends on the intent. Let the customer clarify an ambiguous request instead of forcing it into the nearest category.

3–4. Check the facts and qualify the next step

Before drafting an answer, identify the source that should be trusted for availability, specifications or service terms. Record when that source was checked. An attractive response based on stale information creates work for the person who later has to correct it.

Qualification should collect the minimum context needed to help. In an example property enquiry, that might be area, budget range and preferred timing. Do not turn every conversation into a long form or request sensitive information without a clear need. The process owner should define what is necessary and what belongs in a later conversation.

5–6. Coordinate the handover and update the record

Coordination is a separate job from conversation. The right colleague needs the request, the relevant facts and a clear next action. A proposed meeting needs availability and a timezone. A non-standard question may require review before anyone commits to an answer.

After the handover, the system should record what actually happened. A suggested appointment is different from a confirmed appointment. A draft message is different from a sent one. Choose status labels that preserve those differences, so the pipeline does not look healthier than the underlying work.

7. Follow through, with an owner

The final job is to make sure the next action has an owner. If a customer asks for a later reply, record it. If an employee needs to review an exception, route it. If an appointment changes, make sure the receiving team can see the change. Any customer communication should follow the permissions and current channel rules agreed for the implementation.

Measure the whole path. Useful measures can include incomplete records, time waiting for an owner, corrections and completed handovers. Treat those as proposed operating measures, not promises of a particular conversion improvement. The right measure depends on the job you want the workflow to finish.

Use the Workflow Mapping Kit to follow one real, anonymized enquiry through these stages. If you cannot identify the owner or trusted source at a step, that is a useful finding. Resolve it before asking an agent to operate the process at scale.