Customer experience foundations and role boundaries

Review questions

Customer experience foundations and role boundaries

Begin by choosing the level of the problem: one fast interaction can coexist with an unfinished case or a journey that makes the customer repeat a story. Separate customer report, system evidence and hypothesis. An executable service promise names channel, request type, timer trigger, promised result and update owner; acknowledgement is not resolution. When cases arrive together, compare the effect of delay and urgency using evidence. Route possible privacy or safety harm promptly to its specialist path. Record why priority was chosen and when the next update is due; priority can change with facts.

Review questions

Test your understanding with these questions. Marking and saved results are available with a free account.

  1. Question 1A customer says support replied quickly but made them explain the issue three times. What does this account establish?
  2. Question 2A complete request arrives Friday at 16:00. Business hours end at 17:00 and resume Monday at 09:00. When is a four-business-hour review update due, assuming no holiday?
  3. Question 3An entry code fails for an event starting in 30 minutes; an older receipt can be downloaded. Why triage the code first?