Separate Waiting on the Customer From Waiting on Your Team
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
Hypothetical example: A customer has not replied, but your colleague has not supplied the revised quote either. Calling that conversation “waiting on customer” hides work your team can still do. Leaving it simply “open” hides the same problem in a larger pile.
Separate unresolved conversations by the next action needed to move them forward: owner action needed, waiting on an internal contributor, or waiting on the customer. Require evidence for each waiting label, retain a named conversation owner, and use a temporary unclassified state when the evidence is missing.
The distinction is not who sent the last message. It is whether useful progress depends on the customer, the owner, or another person inside the business. All scenarios, names, and pilot numbers below are fictional and hypothetical. They illustrate a recommended operating practice, not Alactic customer results or software capabilities.
Define states around the blocker, not the latest message
A useful state answers one question: Who must do something next before this conversation can materially advance? It does not describe the sales stage, the customer's mood, or the age of the conversation.
- Owner action needed: the owner can take the next useful action with available information. This includes answering, checking a record, clarifying a request, or securing an internal handoff.
- Waiting on internal contributor: another person must provide a defined input, decision, or completed action. A named contributor has explicitly accepted responsibility for that work.
- Waiting on customer: a specific customer input is necessary, the customer has clearly been asked for it, and no outstanding internal action can materially advance the request without it.
- Needs classification: the blocker or next responsible person cannot yet be established.
The last state is an exception, not a parking space. Assign someone to investigate it. Uncertainty should remain visible rather than being disguised as customer inactivity.
Avoid creating a state for every department. Finance and operations dependencies can share the internal-wait state, with the contributor named separately. This keeps the vocabulary small without losing accountability.
Require evidence before applying a waiting label
A state is a claim about why work cannot advance. Its supporting note should let another teammate check that claim without reconstructing the entire thread.
Use these fields for each unresolved conversation:
- Conversation owner: who coordinates the unresolved request.
- Missing input or action: exactly what is needed, rather than “update” or “response.”
- Blocking party: customer, owner, or named internal contributor.
- Evidence: the request, explicit acceptance of responsibility, or record supporting the classification.
- Next responsible person: who must make the next move.
- Exit condition: the observable event that requires reassessment.
For a customer wait, sending a message is insufficient. The message must identify something the customer needs to supply. A general offer to help does not establish a necessary dependency.
For an internal wait, sending a request is also insufficient. A named contributor must accept responsibility for the defined work. A receipt acknowledgement establishes only that the request was seen, not that someone has taken ownership of it.
Until acceptance is established, the conversation remains owner action needed. That may make the owner-action queue look larger, but it exposes incomplete handoffs instead of treating them as assigned work.
Use this filled state-definition worksheet
This reusable artifact combines state definitions with filled hypothetical records. Copy the field structure into a shared document or conversation note, then replace the example details with evidence from the actual conversation.
Owner action needed: the answer is available
- Conversation: A customer asks whether a revised quote includes installation. The approved quote explicitly includes it.
- Owner and blocking party: Maya.
- Missing action: Answer the installation question.
- Evidence: The unanswered question and the installation line in the approved quote.
- Next responsible person: Maya checks the quote and answers.
- Exit condition: After answering, assess whether the request is complete or a specific dependency remains. Sending an answer does not automatically create a customer wait.
Waiting on internal contributor: a decision is outstanding
- Conversation: A customer requests an unusual delivery arrangement. Maya sends the exact requirements to Ravi in operations. Ravi explicitly accepts responsibility for providing the feasibility decision and any constraints; he has not yet supplied that decision.
- Owner: Maya.
- Blocking party: Ravi.
- Missing input: A feasibility decision and any constraints.
- Evidence: The defined internal request and Ravi's explicit acceptance of responsibility for the decision, not merely acknowledgement of receipt.
- Next responsible person: Ravi provides the decision.
- Exit condition: A usable decision moves the conversation to owner action needed so Maya can respond. Acceptance of the assignment establishes the internal wait; it does not complete the assignment.
Waiting on customer: a necessary choice is missing
- Conversation: Two suitable configurations have been explained. The customer must choose one before the final quote can be prepared.
- Owner: Lena.
- Blocking party: The customer.
- Missing input: Selection of a configuration.
- Evidence: Lena's message explaining both options and asking which to use; no selection appears in the record.
- Next responsible person: The customer chooses; Lena retains conversation ownership.
- Exit condition: A usable selection creates owner work. A request for clarification also creates owner work because Lena must explain something before the customer can choose.
Owner action needed: a handoff is incomplete
- Conversation: A customer reports a billing mismatch. Lena asks a team discussion group for help, but nobody accepts responsibility.
- Owner and blocking party: Lena.
- Missing action: Secure an accepted handoff for checking the disputed item.
- Evidence: The general request and absence of an accepted assignment.
- Next responsible person: Lena identifies an appropriate contributor and makes a specific request.
- Exit condition: A named contributor explicitly accepts responsibility for the defined work.
Waiting on internal contributor: two inputs are missing
- Conversation: A customer has not supplied a preferred installation date. Operations must also correct the proposed scope before a date can be confirmed.
- Owner: Maya.
- Blocking party: Ravi, who explicitly accepted responsibility for correcting the scope.
- Missing inputs: Corrected scope from Ravi and preferred date from the customer.
- Evidence: The accepted correction request and the explicit customer request for a date.
- Next responsible person: Ravi for the actionable internal work; retain the customer dependency in the note.
- Exit condition: When corrected scope arrives, Maya checks whether she must explain a change or whether the customer's date choice is now the only blocker.
Needs classification: the blocker is unknown
- Conversation: An inherited thread ends with an internal note saying it is pending, without identifying what or with whom.
- Owner: Lena.
- Blocking party: Unknown.
- Missing action: Establish the outstanding request and its dependency.
- Evidence: An ambiguous note with no supporting handoff or clear customer request.
- Next responsible person: Lena inspects the history and consults the previous owner where possible.
- Exit condition: Lena can name the missing action, responsible person, and supporting evidence.
Handle simultaneous dependencies without hiding internal work
A conversation can genuinely wait on multiple parties. Keep one primary state and list secondary dependencies in the note. Use this decision order:
- If the owner can take a useful action now, use owner action needed.
- If an internal contributor has accepted work that can progress now, use waiting on internal contributor.
- Use waiting on customer only when necessary customer input prevents further useful internal progress.
In the installation example, the missing date does not prevent Ravi from correcting the scope. The primary state therefore remains internal wait. When the scope arrives, Maya reassesses rather than automatically switching to customer wait: the correction may require her to explain a change first.
This rule is deliberately conservative about customer waits. Its trade-off is that the primary state does not express every dependency. Preserve secondary blockers in the record instead of allowing them to disappear.
Keep conversation ownership separate from the next action
Ravi owes an operational decision, but Maya still owns the customer conversation. Changing the waiting state should not erase that ownership.
Define the contributor's assignment narrowly enough to verify: provide a feasibility decision, correct the scope, or identify a disputed billing item. Asking someone to resolve the entire customer issue can leave responsibility ambiguous.
The owner checks whether the returned input is usable. A progress update does not complete a decision request. A complete decision returns the next action to the owner. If the contributor declines or can no longer take the work, the owner must secure a replacement handoff rather than leaving that person recorded as the blocker.
These are recommended operating rules, not claims about Alactic controls. Use available fields, labels, or notes, and check your workspace and current plan before depending on a particular capability. Manual classification can support the same method.
Repair misleading states by checking their evidence
Common shortcuts make the queue less trustworthy:
- Using the last sender: an outgoing message might be a complete answer, an acknowledgement, or a precise request. Its direction alone establishes nothing.
- Treating any customer reply as completion: a polite acknowledgement may not contain the missing choice. Compare it with the exit condition.
- Treating internal acceptance as completion: agreeing to provide a decision establishes responsibility, not the decision itself.
- Keeping a stale state: a new customer question can create owner work; an incomplete internal answer can leave the internal wait unresolved.
- Closing work to tidy the queue: closure does not remove an unresolved dependency.
Correct the state and its supporting note together. Briefly explain what evidence changed or what earlier assumption was unsupported. Do not invent a historical request or handoff to justify the old classification.
Test whether the queue now shows who can act
For a hypothetical pilot, inspect 20 unresolved conversations and complete the worksheet fields. Record the state counts, then check three observable measures:
- Evidence completeness: records naming the missing action, next responsible person, and exit condition.
- Unsupported customer waits: records lacking a clear customer request or still containing actionable internal work.
- Unaccepted handoffs: supposed internal waits without explicit acceptance by a named contributor.
Have another teammate independently classify a subset using the same evidence. Discuss disagreements about who can act next, rather than choosing the label that makes the queue look tidiest.
The immediate outcome to look for is a defensible allocation of unresolved work, not a promised reduction in resolution time. Start with conversations labelled waiting on customer: identify the exact requested input and check whether useful internal action remains. Where the evidence fails, correct the state and name who must act next.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications