Journal · 17 June 2026
When the confirmation sends people elsewhere
We keep a folder of thank-you screens that do extra work. One clinic’s capture app finished with a button labelled “Join our community,” which opened a Facebook page last updated during a previous Merdeka promotion. Visitors who tapped it never came back to wait for the SMS. The nurse who called them was not told that the Facebook page was part of the path.
Another, for a weekend insurance roadshow at a mall in Ampang, sent a second form for “preferences.” The second form asked for income range. People who had just given a phone number in a noisy atrium declined, and the first form marked them as complete anyway. The callback list looked healthy. The second form’s incomplete pile sat in a vendor report nobody in the booth could open on a phone.
Confirmation copy should do one job: tell the visitor what happens next and who will do it. If you want a Facebook follow, put it on a poster behind the desk, not on the only screen that appears after submit. If you need a second form, say so before the first submit, and let the visitor refuse without polluting the callback list.
When we map a path, we treat every button on the thank-you screen as a fork. We follow each fork once. If a fork leads to a page with no owner, we write “unowned” on the map in the same ink as the stalls. Managers sometimes ask us to soften that word. We do not. An unowned page is how a name leaves the building without anyone at reception noticing.
Before you add another link to a confirmation, read it aloud to the person who phones. If they cannot say what they should do when a visitor taps it, remove the link. The capture app can survive being quieter.