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.
Create a free account to mark your answers and save your progress.