On a hotel booking site, why should a payment-failed message drop the playful tone used in the booking-confirmed message?

## Tone follows the reader's state The same product speaks to the same guest in very different moments. After a booking is confirmed, the guest is relieved and wants the essentials: dates, hotel, confirmation number. After a payment fails, they are anxious, possibly embarrassed that a card was declined, and worried the room will be gone. **Tone** - how the product's constant voice is expressed - should follow that shift. The voice does not change; the dials for seriousness, energy and length move. The shift is not a matter of taste. A stressed reader has less attention to spare, so a message that works for a relaxed reader - with a joke to decode or a long apology to get through - costs more when they are anxious. Tone is part of making a message usable, not only pleasant. ## Why humour fails in failures - **It reads as indifference.** A joke next to a problem signals that the product does not take the problem seriously, even if the brand meant to be reassuring. - **It can feel like mockery.** When the failure may be the guest's own card, a playful line can land as laughing at them. - **It delays the fix.** Puns and cute apologies push the useful part - what happened and what to do - further down. - **It wears thin.** A line that amuses once is irritating on the third failed attempt. - **It moves attention to the brand.** A clever line makes the moment about the product's personality rather than the guest's problem. - **It travels badly.** Wordplay rarely survives translation and can confuse readers working in a second language. This is why many content guidelines say plainly: no humour in errors, failures or anything involving the reader's money, data or safety. ## What calm and helpful sounds like | Don't | Do | Why | |---|---|---| | Oops! Our payment gremlins struck again! | Your payment didn't go through. | Plain, serious, no joke | | You entered an invalid card. | The card was declined. Try another card or payment method. | No blame, focus on the next step | | We're so, so sorry!!! Something went terribly wrong. | We couldn't complete your payment. Your room is held while you try again. | Calm, not alarmed; reassures with a fact | | Transaction error 402: request rejected. | We couldn't complete your payment. | Human, not a system log | The 'do' column is still warm - it is written by a person for a person - but it is quiet. ## Success is brief, not a party The confirmation message has more room for warmth, but restraint still helps: - lead with what the guest needs to know - hotel, dates, confirmation number; - keep any light touch to one short line, such as 'You're all set for Lisbon'; - avoid stacking exclamation marks or celebrating routine actions loudly, which makes every success sound the same and devalues the ones that matter; - remember the guest may read it again later to check details, so it should hold up on the second read. ## Where light touches are fine Playfulness is not banned from the product; it is placed. A light tone suits a moment when: 1. the reader is not losing money, time, data or a booking; 2. the joke does not delay or obscure the task; 3. it still works on the tenth reading; 4. it does not rely on wordplay that breaks in translation. Onboarding hints, an inviting search prompt and a first-trip welcome usually pass. Payment failures, sold-out rooms, cancellations and account problems do not. ## A quick check before shipping a message - How is the reader likely feeling at this moment? - What could they lose if this goes wrong? - Would this line still sound right to someone who has just failed three times? - Is the next step visible without reading past a joke? If the honest answers point to stress or loss, the tone should be calm and plain, whatever the brand's usual playfulness. The brand loses nothing by it: guests remember how the product treated them when something went wrong far longer than they remember a clever line.