Two people from the same customer account ask for opposite changes: one wants a mailbox removed, while another says to keep it. Acting quickly may seem helpful, but an irreversible change can create a bigger problem than a short delay. Pause the change, keep the discussion neutral, and use the account’s established procedures to identify who is authorized to decide. Then ask the contacts to provide one consistent instruction through an appropriate channel. This process creates a clear next step without treating confidence, job title, or the latest message as proof of authority.
The useful bits
- Pause irreversible work while the conflict is unresolved, and say what is on hold.
- Check authorization against established account records and procedures—not assumptions.
- Ask the contacts to confirm one specific instruction and verify it before proceeding.
Stop the action before it crosses the point of no return
As soon as you see contradictory instructions, pause any action that could delete, overwrite, transfer, or otherwise be difficult to reverse. If the change is scheduled or already in progress, stop or hold it where your process allows. Do not try to resolve the disagreement by carrying out part of each request.
Make the pause visible to the people involved. State what action is on hold and that you need to resolve the conflicting instructions before proceeding. Be precise about status: if you have only paused the work, do not imply that anything has been changed or restored. If a step has already happened, describe that accurately and escalate according to the account’s established process.
“We’ve received different instructions about [specific change]. I’ve paused [specific action] and have not proceeded with [irreversible step]. I’ll confirm the authorized instruction before continuing.”
Use the account’s existing authorization process
Check the records and procedures already established for that account. Depending on your service arrangement, these might identify an authorized contact, an approval workflow, or a required confirmation channel. Use the applicable process rather than deciding based on who wrote most recently, who sounds most certain, or who appears more senior.
If the records do not make the decision-maker clear, ask the appropriate account owner or internal escalation contact how to verify authority. Avoid asking either disputing contact to declare themselves the decision-maker. If you need to contact someone through a known channel, use contact information already held in the account’s approved records rather than details supplied only in an unexpected conflicting message.
Keep the request narrowly defined
Describe the exact decision that needs resolution, in plain language. Include the relevant account or item, the requested change, and the important consequence—such as removal or loss of access—without adding assumptions about why either person asked for it.
Separate the decision from related questions. If one contact also requests a different change, do not treat agreement on the first issue as approval for the second. A clear, limited question makes it easier for both contacts and the authorized decision-maker to confirm the same thing.
Ask for one consistent instruction
Once you know the correct approval route, ask the contacts to reconcile their requests and provide one instruction through that route. Depending on the established procedure, this could mean a response from the authorized contact or an approval recorded in the required system. A copied email may help keep people informed, but it does not replace a required approval method.
Make the confirmation specific enough to act on: what should change, which account or item it applies to, and whether the requested action is to proceed or not proceed. If the contacts continue to disagree, keep the action paused and refer the issue to the designated account owner or escalation contact. Do not choose between them yourself.
“Please confirm one instruction for [account/item]: should we [proposed change] or leave it unchanged? Please have [authorized contact or approval route, as established for this account] confirm the decision, including any relevant scope or timing.”
Check the instruction before resuming
Before acting, compare the confirmed instruction with the original request and the account procedure. Confirm that it comes through the required channel, is from the authorized decision-maker, and addresses the same item and scope. If anything is missing or inconsistent, ask a focused follow-up question rather than filling in the gaps.
Afterward, communicate what you did and what remains unchanged. Record the conflicting requests, the pause, how authority was checked, the final instruction, and the action taken in the appropriate account record or work system. Keep the record factual and limited to what is needed for continuity.
A quick checkpoint for the handoff
Before releasing the pause, run through this short checklist. It helps prevent an unclear reply from becoming an unintended authorization.
- Is the disputed action still paused, with its status described accurately?
- Did I use the account’s established method to identify who can approve it?
- Does the confirmed instruction specify the exact change and affected item?
- Does the instruction match the required channel and approval process?
- Have I recorded the decision and told the relevant contacts what happens next?
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction