Apology Message Generator

Research on apology effectiveness converges on the same components. A message containing all four repairs trust. One missing any of them reads as a formality.

The action. Name the specific thing with a time attached. I missed your call on Thursday and did not ring back until Sunday, rather than I am sorry for everything.

The impact. Say what it cost them, in their terms. You were left wondering whether something was wrong.

Ownership. Own it with no reason following. Every explanation attached reads as a defence, however true.

The repair. One concrete change described as already happening, not promised for later.

Three short sentences covers all four. The generator is constrained to that shape, which is why the output stays usable rather than drifting into a paragraph of feeling.

The generator has no facts about your life. Everything in the output comes from your description.

Name the action. Not I was rude, but I interrupted her twice in front of her parents.

Attach a time if you have one. Tuesday, last week, and for the past month all give the message something concrete to anchor to.

Say what changed for them if you know it. She stopped bringing things up with me. He rearranged his whole day.

Leave your feelings out of the description. The message should be about their experience, and describing your guilt pushes the output in the wrong direction.

Two sentences of description usually produce a better result than one word or a paragraph.

Six constructions are blocked at generation, and knowing why helps when you edit.

Sorry if you were upset. The word if disputes whether the harm happened, so the reader hears you questioning their reaction.

Sorry, but I had a long day. Everything before but is cancelled by what follows. The reader hears the second half.

Mistakes were made. Passive voice with no subject means nobody is apologizing.

Sorry you feel that way. This apologizes for their emotional response instead of your action, and reads as condescension.

Please forgive me. This hands them a task. An apology gives something rather than asking for something back.

I feel terrible about this. True or not, it describes your suffering and quietly asks them to manage it.

The four parts stay constant. The register changes, and picking the right relationship changes what the generator returns.

For a partner, the output stays direct and avoids declarations. After a while together, sweeping statements about how much someone means read as filler, and the specific thing is what is missing.

For a friend, the wording loosens. Formality to someone close reads as distance, which is usually the thing being repaired.

For family, the repair section carries more weight. They have heard the acknowledgment before, so what they read for is whether anything changes.

For work, the message goes plain and professional. Name the error, state the fix, give a date. A work apology is judged on containment rather than on how sorry you sound.

Under 180 characters, which is the cap on the card and on the generator output.

That limit is a filter rather than a restriction. Long apologies almost always contain a defence, because room invites explanation.

The four parts compress cleanly. I cancelled twice in three weeks without explaining. You started planning around me not showing up. I said no to Friday and I am there at seven. That is all four, inside the cap.

If your situation will not fit, you are usually apologizing for several things at once. Pick the one that matters most. Stacked apologies dilute each other and the reader loses track of what you are taking responsibility for.

Anything longer belongs in a conversation. The message exists to make that conversation possible.

Read the draft before anything else. This is the step people skip and the one that decides whether the message works.

Fix anything untrue. The generator fills gaps with plausible detail, and plausible is not the same as accurate.

Fix anything outside your normal voice. The person reading it knows how you talk, and text pitched wrong is the signal they catch first.

Cut anything that reads as defence, even if the generator produced it. The constraints catch the common failures, and judgement catches the rest.

Generate again if the draft misses. Repeated runs produce genuinely different wording rather than the same sentence reworded.

Four situations where a generated message is the wrong tool.

Serious harm. The effort of finding your own words is part of what a serious apology proves, and outsourcing it removes the proof.

A repeat apology. Naming a pattern honestly is not something to delegate. I have said this before and then done it again has to come from you.

A relationship with its own language. Long friendships and marriages carry a register generated text misses.

When you already know the sentence. If it is in your head, type it. The generator exists for the blank box.

Both give you a starting point, and they start from different places.

A template contains someone else's facts in the right structure. You swap your situation in, which works when the example is close to yours.

A generated message contains your facts in the right structure, because you supplied them. That works when your situation is specific and no template fits.

The message library on this site holds twelve written examples covering partners, friends, family, and work. For common everyday apologies, adapting one is often faster than describing the situation.

Neither works unedited. A template sent as written reads worse than a plain text, because the structure implies thought the words do not carry.

Length and sincerity move in opposite directions on an apology, which surprises people.

A long message gives you room to explain, and explanation reads as excuse regardless of intent. The reader is scanning for whether you understand what you did, and every extra sentence about context delays that answer.

A short message forces a choice about what matters. Naming one specific thing communicates more than describing five in general terms.

There is a practical reason too. A card holds a few lines legibly. Anything longer either shrinks below readable size or gets cut.

If the situation genuinely needs more room, the message should ask for a conversation rather than trying to be one.

The same words work in both places, and the delivery changes how they land.

A text arrives immediately and reads as low effort. That suits small things and undercuts anything serious.

A card carries visible effort. Designing something and putting both names on it proves time in a way a text cannot.

The generator produces card-length output for that reason. If you want to send it as a text instead, copy the message and send it plainly.

For anything that genuinely hurt someone, the card wins. Effort is read as sincerity, and the effort has to be visible.

The description you type is the only thing that leaves your device.

Names, the finished message, colours, and the exported file are all handled in your browser. No account exists, so there is nothing to attach anything to.

The description goes to NVIDIA, which runs the model that writes the draft. Nothing is stored on our side.

If that does not suit the situation, the message library gives you twelve human-written examples with no network request at all.

Sending it is the start. The change named in it is what decides whether anything repairs.

Do not follow up asking whether they read it. That converts a gift into a request for a reply.

If they accept it, stop apologizing. Continuing past acceptance asks them to keep reassuring you.

If they respond with more detail about what hurt, listen without defending. People who have written you off do not explain.

Then do the thing you named. An apology repeated without a change becomes a record of unreliability.