In this guide
- Train the decision, not a slogan
- Use three contrasting scenarios
- Include a refusal to collect secrets
- Include a scenario where two desks have work
- A hypothetical training correction
- Assess what the trainee refuses to infer
- Assess the handoff sentence
- Keep the exercise current
- Reusable work card
- Sources and scope
- Continue with a different task
Use contrasting purchase scenarios to distinguish merchant, processor and cardholder questions.
Train the decision, not a slogan
“Ask the issuer” is sometimes right and sometimes an unhelpful shortcut. Staff need to recognize when the business can answer from its own order or payment record, when it needs processor support and when the customer has an account-specific question. Teach those distinctions using fictional examples.
Use three contrasting scenarios
One scenario concerns a missing item, another an uncertain merchant payment status and another a customer’s account access. Ask the trainee to identify the record they can check and the role with authority over the unresolved question. Do not ask them to diagnose an account from the brand name.
Include a refusal to collect secrets
Every scenario should reinforce that staff do not need a PIN, password or one-time code to provide ordinary merchant service. The correct next step can include a private official channel, but the trainee should not create a credential collection process or browse an employee or customer account.
Include a scenario where two desks have work
A useful training exercise should not imply every enquiry has one simple owner. Give staff a fictional case in which the merchant must investigate a cancelled order while the customer also asks about account access. The trainee should keep the merchant investigation open and identify the verified cardholder route for the separate access question. This tests whether the staff member can divide responsibility without abandoning the customer or overstepping into account administration. Use the business’s real approved procedures to evaluate the answer. General role definitions are context, not a complete operating manual for the merchant.
A hypothetical training correction
A trainee routes every refund question directly to the issuer. Ask what the merchant can first establish: whether a return was approved and whether a refund action exists. The issuer may need that merchant evidence. Conversely, a trainee who promises to fix the account needs a clearer explanation of the merchant’s limit.
Assess what the trainee refuses to infer
A strong trainee can state what the evidence does not establish. Two payment references do not necessarily mean two completed charges; a return approval does not prove account credit; a familiar card name does not explain a decline. Ask the trainee which additional merchant evidence or authorized owner would resolve the uncertainty. This approach rewards disciplined service rather than confident speculation. It also gives trainers a concrete way to identify a knowledge gap: the missing skill may be interpreting a system label, finding a receipt or explaining a handoff, rather than memorizing more product terminology.
Assess the handoff sentence
Have the trainee say one concise sentence explaining what they checked and what happens next. Listen for unsupported timing guarantees and vague pronouns. A good sentence identifies the responsible party without making the customer feel abandoned.
Keep the exercise current
Use the merchant’s actual policies and processor guidance to review the examples. Update them when systems change. The public sources establish general roles; they do not certify staff competence or define the business’s live payment workflow. This publication’s route tool is a rehearsal aid, not a support-ticket system.
Reusable work card
Use these prompts in your organization’s approved process. They request no private account information and do not authorize a payment or account change.
- Use contrasting scenarios for fulfilment, uncertain merchant payment status and private account access.
- Ask which merchant record can be checked and which role can answer the remaining question.
- Include a clear boundary against collecting credentials or browsing customers’ account history.
- Practice a handoff sentence that explains the finding and next responsible party without abandoning the customer.
- Listen for unsupported timing guarantees and vague language that hides ownership.
- Update examples against actual merchant policies and processor guidance when systems or procedures change.