One Message Can Heal
Create Your Sorry Card

Apology guides

Login Issue Apology Message

Account-access problems need a clear support path without requesting passwords, one-time codes or sensitive account details in a normal message.

2 min readGuidance & examples

Before you write

Identify the affected sign-in step and give the established status or support route. Never ask for a password or one-time login code.

Check the reference, names and status before sending. If a date or time matters, use the actual date and time zone. Keep proposed arrangements distinct from confirmed ones.

Examples to personalise

These are original writing examples, not statements about your situation. Replace bracketed details, adjust the wording and remove any claim you cannot verify.

Personalise a draft

Choose an example, fill in the relevant details and edit the result in your own voice. The helper uses the selected example; it does not invent facts or send the message.

Check before sharing

  • Use an official domain or support channel.
  • Check the issue before suggesting repeated resets.
  • Avoid collecting credentials in ordinary messages.

Do not include a fabricated reset link or tell someone to share a one-time code.

Questions about this message

Should users share their password with support?

No. A support apology should not request passwords or one-time codes. Direct users to the service's approved recovery process.

Make it personal

Start with the words. Then choose how you want to share them.

  • A truthful detail
  • A natural tone
  • A considerate next step

Review available card options in the creator and check the final wording before sharing.

Make your message personal.

Use the ideas here as a starting point. Bring your own words and details to the creator when you are ready to make your sorry card or message.

Create your sorry card