In this guide
Restate the material detailsUse a two-account scenarioSeparate verification from approvalPreserve the final agreed scopeReport the actual outcomeA message saying “yes” can be clear in a short exchange and ambiguous in a busy thread. If the conversation has mentioned two accounts, several terms or a device change, the approval should point to the specific action. A clear scope protects the customer’s intention and helps the team avoid applying the wrong request.
This is an original workflow example, not a statement of Dream’s legal authorisation or verification policy.
Restate the material details
Before an action, identify the intended existing account through the appropriate private order reference, the selected term or operation and the quoted amount where relevant. State whether the request is a renewal, new identity or another permitted change. Do not treat a general support question as approval to purchase or alter an account.
Use a two-account scenario
Imagine a customer asks about the living-room account and a retired test entry in the same conversation. An agent sends a quote, then receives “go ahead.” The team should make the target clear before acting. A local label alone may not be enough because names can be duplicated or changed. The original order relationship supplies the durable context.
Separate verification from approval
Verifying that a person may request an account change is different from confirming which change they want. Both can matter. A receipt may help identify a purchase without authorising every possible action. An approval may describe the action without satisfying the provider’s ownership process. Use the actual process for each instead of substituting one for the other.
Preserve the final agreed scope
Keep the relevant confirmation near the order record and connect it to the action reference. If material details change, obtain a clear updated instruction rather than relying on an earlier broad approval. OWASP’s transaction guidance emphasises acknowledging significant transaction details; the practical communication lesson is to make the target and amount visible when they matter.
Report the actual outcome
After the responsible party confirms the result, state what was applied and which account it concerns. If the result differs from the intended scope, keep the discrepancy open and ask for clarification. Do not silently rewrite the request to match the outcome. A clear approval trail supports a focused correction conversation without inventing a refund, reversal or completion guarantee.
If the customer answers a different question from the one asked, clarify the mismatch before applying the action. For example, agreement that a player name is correct is not the same as accepting a service quote. Keep the final instruction next to the relevant scope so a later agent does not have to infer approval from several unrelated short replies.
Questions about this guide
Does every support answer need a purchase approval?
No. Answering a question or reviewing reversible local context is different from performing a paid or account-changing action. Match the confirmation to the actual action and the responsible provider’s process. Avoid adding unnecessary approval steps to ordinary explanations.