Back to the Salik case studyRAKBANK · Salik AutoPay
CUSTOMER JOURNEY MAP

Keep the toll account funded.
Stay in control of the money.

Driver using Salik
Goal: reliable recharge with an understandable payment rule.

Scroll horizontally to follow all six stages.

Journey stage01Find02Understand03Configure04Confirm05Manage06Recover
TouchpointPayee list + action menuAutoPay stateRecharge settingsReview + confirmationSaved instructionPayment status + support
Customer actionIdentify the right Salik payee and locate AutoPay.Determine whether automatic recharge is already active.Choose the trigger, amount and funding account.Check the selected instruction before committing.Change, stop or re-enable AutoPay.Understand an unsuccessful or unconfirmed recharge.
Customer concern“Where do I change this?”“Is it actually on?”“When will money move?”“Have I chosen correctly?”“Can I stay in control?”“Was I charged?”
Pain pointEdit Beneficiary and Manage AutoPay compete with the customer’s mental model.Red in both switch states creates a misleading affordance.Missing balance context increases the effort of evaluating the rule.Customers want a short journey and enough detail to verify their choices.Losing previous settings would create avoidable re-entry and uncertainty.An active instruction does not explain a failed or unconfirmed payment.
ConfidenceQualitative interpretationUncertaintyDoubtCautionReassuranceControlAnxiety
Design opportunityPair nicknames with vehicle plates; distinguish one-off recharge from the recurring instruction.Recognition + information scentPair distinct visual states with explicit enabled / disabled labels.Visibility of system statusExpose balance context, common presets and the complete instruction.Recognition over recallKeep selected settings visible in a concise confirmation.Error preventionRetain readable settings and distinguish the toggle’s enabled and disabled states.User control and freedomDistinguish confirmed failure from unknown status; explain the next action.Recoverability

Concerns summarise research themes rather than direct quotations. The confidence curve is a qualitative design interpretation; recovery highlights a service opportunity raised during testing.