Resolve Conflicting Answers Within the Inbox Team
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
One teammate says the customer can change a booking. Another says changes are no longer allowed. A third remembers a manager making an exception last week. Assigning the conversation to one person stops duplicate replies, but it does not establish which answer is supported.
To resolve inconsistent answers from shared inbox staff, separate three questions: what evidence applies to this case, who is authorised to settle any remaining uncertainty, and what can safely be said while that decision is pending. Select evidence by applicability and authority before recency. Keep one person responsible for the customer conversation without treating that person as the authority on every underlying rule.
The worksheet below turns that approach into a practical review. It records competing claims, tests their support and gives the responding teammate a holding-response brief rather than an instruction to sound confident.
1. Define the disputed claim before debating the answer
Start with the smallest statement that the team disagrees about. “What is our booking policy?” is too broad. “Can this customer change the session date after the preparation pack has been sent?” gives reviewers something they can actually test.
Capture the customer’s request, the relevant case facts and any answer already sent. Distinguish verified facts from assumptions. A teammate saying “the pack probably went out yesterday” is not the same as a dispatch record.
Ask each person to state their proposed answer and its supporting source separately. This prevents a persuasive explanation from obscuring a weak basis.
- Claim: What exactly should the customer be told?
- Support: Which instruction, record or decision supports that claim?
- Scope: Does it cover this service, customer type and stage of the process?
- Gap: What would still need to be verified?
Avoid starting with a vote. Several staff members may repeat the same outdated note, so agreement is not independent confirmation. Equally, one dissenting teammate may have the only applicable instruction.
2. Use an evidence hierarchy, not a newest-document rule
A useful hierarchy asks two questions in sequence: is this evidence eligible to govern the case, and, if so, how strongly does it support the proposed answer?
First check applicability, approval and effective status. A recent draft for a different service does not outrank an older approved instruction that still governs this one. Then use the following recommended order:
- An authorised decision for this exact case. It must come from someone permitted to make that decision, and its conditions must be recorded. A one-off exception does not automatically change the general rule.
- A current, approved instruction covering this case. Check its scope, effective date and whether it replaces earlier guidance.
- Verified case records. These establish facts such as whether a preparation pack was sent. They help apply a rule but do not create permission to make an exception.
- Older instructions and internal notes. These may explain past practice, but their current status needs checking.
- Recollections and unsupported assertions. These are leads to investigate, not sufficient grounds for a customer promise.
This is not a point-scoring system. A source with a title and date can still be irrelevant. A colleague’s recollection may lead to a genuine authorised exception, but the recollection alone does not establish its terms.
If two applicable approved instructions conflict and neither clearly supersedes the other, stop treating the task as document selection. The unresolved conflict needs an authorised ruling.
3. Separate conversation ownership from decision authority
The conversation owner is accountable for keeping the customer informed, gathering evidence and ensuring that the eventual answer is sent. The decision authority is the person permitted to interpret the disputed instruction or approve the requested exception. They may be different people.
Find the authority through the existing approval route, the instruction’s named approver or the relevant process owner. Do not assume that the most senior person available can waive every rule. Ask a narrow question: “Are you authorised to decide whether this instruction permits this change, or does it need to go elsewhere?”
There may also be two different decisions. A process owner may confirm what the standard instruction means, while another designated approver handles exceptions. Record which decision you are requesting so that a clarification is not mistaken for permission to depart from the rule.
If authority is unclear, send the issue to the manager responsible for identifying the correct approver. That manager need not invent a substantive answer. Meanwhile, the conversation owner should retain responsibility for the customer update rather than transferring the thread repeatedly.
4. Filled fictional answer-dispute worksheet
Fictional worked example: All names, dates, rules and timings in this worksheet are hypothetical. They illustrate a recommended operating method, not an Alactic product capability or customer result.
Case and disputed answer
- Case: Inbox reference H-214. A customer asks to move a workshop booking after receiving its preparation pack.
- Verified facts: The request arrived on 18 June. The workshop is on 24 June. The booking record shows the preparation pack was sent on 17 June.
- Precise question: Can inbox staff confirm a date change after the pack has been sent, or must they obtain an exception decision?
- Customer communication so far: An acknowledgement has been sent. No change has been promised.
- Conversation owner: Maya, the assigned inbox adviser.
Competing evidence
- Evidence A — old internal note: A team note dated 8 January says advisers may move workshop bookings when the request arrives at least two days before the session. Its current approval status is not recorded. It does not discuss preparation packs. It supports a possible earlier practice, but does not establish the current answer.
- Evidence B — recent approved instruction: An instruction approved by the service operations lead, effective 1 June, covers the same workshop service. It explicitly replaces the January change guidance. It permits routine date changes before preparation-pack dispatch and requires approval from the service operations lead after dispatch. It directly covers the verified case facts.
- Evidence C — colleague’s recollection: Leon remembers a manager allowing a post-dispatch change the previous week. He cannot identify the booking or confirm whether it was an exception. This supports a search for a prior decision, not a promise that the current customer qualifies.
Evidence selection and authority
- Selected governing evidence: Evidence B, because it is approved, effective, applicable to the service and explicitly replaces Evidence A.
- Supporting case evidence: The dispatch record establishes that the request falls into the approval-required branch.
- What can be concluded: Maya cannot confirm the change under the routine instruction. An exception decision is required.
- What cannot be concluded: The customer is not necessarily ineligible for a change. Requiring approval is not the same as refusing the request.
- Authorised decision-maker: Priya, the service operations lead named in the instruction.
- Question sent for decision: “For H-214, do you approve a date change after preparation-pack dispatch? Please record the permitted action and any conditions.”
- Treatment of the recollection: Leon will look for the earlier case if it is readily available, but that search will not delay the escalation. Any previous exception must be checked for scope before reuse.
Holding-response brief
- Purpose: Acknowledge the requested change and explain that approval is being checked.
- Confirmed information: The request has been received; the preparation pack has already been sent; a post-dispatch change requires review.
- Unresolved point: Whether the exception will be approved.
- Do not say: The change is confirmed, the change is impossible, or a previous customer’s exception guarantees the same outcome.
- Next action: Maya sends the approval request to Priya and retains the customer conversation.
- Next customer update: By 3 p.m. on 18 June, a hypothetical checkpoint that Maya has checked she can meet. If the decision is still pending, she will send a status update rather than imply approval.
Thanks for asking to move your workshop booking. Because your preparation pack has already been sent, I need to check approval before confirming a date change. I’ll update you by 3 p.m. today, even if the decision is still pending.
5. Make the interim response useful without overstating certainty
A holding response should tell the customer what is happening, not merely that the team is “looking into it.” Include the confirmed boundary, the action being taken and the next update point. Omit the internal debate unless it is necessary to correct something already communicated.
The worksheet’s selected evidence supports a limited answer: approval is required. It does not support an outcome. That distinction matters because teams often turn uncertainty into an accidental refusal or an accidental promise.
Choose a checkpoint the conversation owner can control. A commitment to provide an update is usually more manageable than a commitment to obtain a decision by a particular time. Do not invent a response deadline for an approver who has not accepted it.
Match the wording to the actual state. Say that a request has been sent for approval only after it has been sent. Do not describe a booking as changed because somebody has agreed to review it. If a customer must act before an external cutoff, state only verified timing and escalate the urgency without promising the outcome.
6. Recover when the evidence or the process fails
The worksheet will not always produce an immediate answer. These failure cases need explicit handling:
- Two current instructions conflict. Record the conflicting passages in your own words, identify their scopes and ask the authorised process owner which applies. Do not choose whichever gives the easier customer response.
- The decisive fact is missing. If dispatch status is unknown, verify it before applying a post-dispatch rule. Keep the question open rather than filling the gap with habit.
- The approver is unavailable. Use an existing delegated route if one exists. Otherwise retain the request, escalate the missing authority and update the customer. Urgency alone does not confer approval powers.
- A teammate already promised the wrong outcome. Preserve the communication history, alert the authorised decision-maker and correct the customer-facing answer promptly once the position is established. Acknowledge the earlier inconsistency without blaming an individual.
- An exception is approved informally. Ask the approver to confirm the case, permitted action and conditions in the shared record. A vague “fine” may leave the team unsure what was authorised.
There is a trade-off between speed and evidence collection. For a straightforward conflict, checking the applicable instruction and one decisive case fact may be enough. For an unclear exception, more investigation is justified. Avoid searching every historical conversation when a current instruction already establishes the next step.
7. Close the dispute without turning an exception into policy
When the decision arrives, record four things together: the answer, its evidence, the decision-maker’s authority and its scope. Then give the conversation owner a clear instruction about what may be communicated and what still requires action.
In the hypothetical worksheet, an approval might permit one date change subject to available space. That would not authorise staff to promise a particular session before checking availability, nor would it erase the approval requirement for later cases.
Deal with the outdated note through the existing document process. Mark it for withdrawal, correction or a clear reference to the replacement instruction. Do not leave two apparently active answers for the next shift to rediscover. Preserve historical material where needed, but distinguish it from current guidance.
If the final answer differs from an earlier customer response, explain the correction directly. The customer needs the reliable position and the next step, not a detailed account of which teammate won the argument.
8. Test the worksheet on the next live disagreement
For the next disputed answer, assign one conversation owner and complete the worksheet before sending a substantive response. Keep the review proportionate: one precise claim, the competing sources, the selected evidence, the remaining uncertainty and the authorised decision route.
For a hypothetical pilot covering the next five disputes, record:
- Whether the governing evidence and its scope were identified.
- Whether the authorised decision-maker was named.
- Whether the promised customer update happened on time.
- Whether an unsupported promise or refusal had to be corrected.
- Whether obsolete guidance remained available as a current answer.
These observations reveal different problems. Repeated missing facts suggest a case-record issue. Repeated uncertainty about approvers suggests an escalation-route issue. Repeated reliance on old notes suggests a guidance-maintenance issue. Use the next review to fix the recurring cause, rather than asking staff to resolve the same disagreement more confidently.
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