01 / Define the boundary
Choose one inquiry workflow.
Start with one kind of incoming customer inquiry that staff can follow from arrival to a reviewed next step. Make the scope narrow enough to observe, and write down what should remain outside it.
- Which incoming messages are in scope: product questions, service requests, billing questions, complaints, or another defined group?
- Where do inquiries arrive today, and what marks the start and finish of the triage task?
- Who owns the queue, who can answer each topic, and who handles urgent or sensitive cases?
- Which inquiries must stay on the current human-led path while the team assesses a possible workflow?
The first deliverable is a shared description of the current process. It is not a commitment to automate, change customer treatment, or connect a particular tool.
02 / Observe the current process
Map intake, context, and ownership.
Follow an inquiry from its current entry point through review, handoff, and response. Preserve the source message and show who is accountable for each next step.
- Original message
- Keep the customer’s wording and attachments available to the reviewer; a summary or label is not a replacement for the source.
- Available context
- Record only the relevant customer, order, service, or prior-contact details the team is authorized to use.
- Owner and status
- Show who is responsible for the next step and whether the inquiry is new, awaiting information, under review, routed, or answered.
- Channel and timing
- Keep the received date and channel visible so staff can apply the organization’s existing response and escalation practices.
A process map is a way to make the work visible. It does not show that a particular model, vendor, mailbox, CRM, or helpdesk connection is available or suitable.
03 / Agree on useful labels
Define topics and an exception path.
Keep the topic list small enough for staff to apply consistently. The examples below are a starting point to adapt, not a standard every organization must use.
- Product or service question
- A question about what is offered, how it works, or what is included.
- Price or billing
- A question about a quote, invoice, charge, payment, or pricing detail.
- Order or scheduling
- A request about an existing order, appointment, delivery, or timing.
- Problem or complaint
- A report that something did not work as expected or needs attention.
- Account or access
- A request involving sign-in, account details, or access to a service.
- Other or unclear
- A message that does not fit the agreed topics or needs a person to interpret it.
Include “other or unclear” and a human handoff. Do not force an uncertain inquiry into a neat category just to complete a queue.
04 / Surface gaps without filling them in
Flag missing information for a person to assess.
Agree on what information staff need to understand or route the selected inquiry type. Possible assistance can point out an absent field, apparent conflict, or unclear request and show why it raised a question. It should not invent the missing answer.
- A detail needed to understand the request is absent
- Flag what is missing and point to the message context that led to the flag. Do not infer the customer’s answer.
- Two details appear inconsistent
- Describe the inconsistency plainly and leave resolution to staff, who can ask a clarifying question if needed.
- The inquiry may need urgent or specialist attention
- Route the item for prompt human assessment under the organization’s existing process; a label is not a risk decision.
Staff decide whether a follow-up is appropriate, what to ask, and whether the matter needs a different route under existing practice.
05 / Keep wording reviewable
Prepare a draft, not an automatic reply.
A possible draft can help staff start a response, but it must remain an unsent proposal. Give the reviewer the inquiry and any approved source material used to prepare it.
- Use only facts the reviewer can find in the inquiry or in current, approved organization material.
- Keep uncertain details visible and leave placeholders or questions where facts have not been confirmed.
- Use the organization’s normal tone, but do not invent policies, availability, prices, eligibility, or commitments.
- Treat refunds, exceptions, complaints, sensitive subjects, and promises about timing or outcomes as staff decisions.
- Keep the draft separate from the sent reply and preserve the source and any staff edits according to existing practice.
No classification or response is verified merely because it sounds plausible. Staff must check it against the original inquiry and current, authorized guidance before taking action or sending anything to a customer.
06 / Keep people accountable
Make staff review a real workflow step.
Name the reviewer and give them the time, context, and authority to change or reject the proposed classification, information flag, and response draft.
- Read the original inquiry and relevant source context before accepting or changing the proposed topic.
- Confirm that each missing-information flag is relevant, and decide whether clarification is actually needed.
- Check every sentence in the draft for accuracy, tone, policy fit, privacy, and unsupported promises.
- Edit or discard the draft freely; send a response only through the organization’s normal, authorized process.
- Route urgent, sensitive, ambiguous, or high-consequence matters to the responsible person.
- Record corrections and pause the assisted step if the source is unavailable or the output cannot be reviewed in time.
If staff cannot inspect the source, correct the result, or pause the assisted step, review is not meaningful. Keep the organization’s established human-led route available.
07 / Learn from observation
Evaluate a small, bounded test.
If the organization chooses to explore assistance, agree on a limited sample and a review period first. Keep the usual process available and compare observations rather than assuming the change will improve service.
- Did inquiries land in a useful topic, or did staff frequently change the suggested label?
- Were missing details flagged when needed, and how often were flags irrelevant?
- Could a reviewer verify each response draft against the source and approved material?
- What needed editing or removal, and how much review effort did that add?
- Were urgent, sensitive, or out-of-scope messages routed through the existing process?
- Did the trial raise data-handling concerns or change the customer or staff experience?
Results from a limited test may not carry over to another topic, channel, or team. A reasonable next step may be to revise the labels, stop, or examine a different slice.
08 / Keep the scope honest
Limits and practical checklist.
This guide describes a possible workflow, not a guaranteed result or a claim that a third-party service is available, approved, or connected. Suitability depends on the organization’s process, data, tools, and review capacity.
Before you begin
- Choose one inquiry type, channel, owner, and bounded review period.
- Map the current intake, topic labels, missing-detail checks, handoffs, and source records.
- Agree on a small topic set, an “other or unclear” path, and explicit exceptions.
- Limit assistance to proposed labels, missing-information flags, and response drafts for staff review.
- Use only tools and data handling approved by the organization; do not assume an email, CRM, helpdesk, or other integration is connected.
- Require staff to verify classifications and drafts before routing, acting on, or sending a response.
- Compare corrections, missed or irrelevant flags, review effort, and observed concerns before deciding what to do next.
To discuss an inquiry workflow with Clearpath, you can share the context through an inquiry. You can also browse the other workflow guides.