Spaces

Confirmation messages for demos, upgrades and requests at your software company

These confirmation messages let a software company confirm a booked demo, a plan change, a support ticket or an access request in a clear, friendly way. Fill in the details and copy.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

A user who asks for a demo, a plan change or a data export wants to know one thing: did it go through. A clear confirmation lowers anxiety and cuts the 'just checking' follow-ups that fill an inbox. It also makes your company feel organised.

Fill in the date for the demo and the name of your team contact. Each message below confirms a different kind of request. Always say exactly what was done and what the user should expect next, in the same words they used.

Demo booked

You are booked in for a demo of [business] on [demo time]. [contact name] will run it, and you will get a calendar invite shortly. Reply here if you would like to bring a colleague or change the time.

Plan change done

Your plan change is done. The new features are already on your workspace, and your next invoice will show the update. If anything looks off, tell me and [contact name] will check it today.

Support request received

I have your request and logged it with our team. [contact name] is looking into it, and you will hear from us in this chat as soon as there is news. Nothing more is needed from you.

Data export started

Your export from [business] is on its way. For large workspaces it can take a while, and you will get a link when it is ready. If it has not arrived by tomorrow, write back and [contact name] will help.

Confirm like you mean it

A good confirmation repeats the key detail, such as the date or the plan name, so the user can spot a mistake at once. It also names a person, which tells them someone is responsible.

Do not confirm things that have not happened. If a plan change needs a person to approve it, say 'I have passed your request to our team' rather than 'it is done'. Overclaiming creates more messages than it saves.

  • Repeat the date, plan or item in the message.
  • Name the person who will follow up.
  • Say what the user should do if something looks wrong.

FAQ

Should confirmations be sent by a person or an agent?

Either works for a simple confirmation, like a demo booking. Anything involving money, such as a plan change with a charge, should be checked by a person before it is confirmed.

Can we send confirmation messages to people who have not asked for anything?

No. Confirmations are replies to something a user did. Write only to people who started a conversation or are expecting to hear from you about a request they made.

How soon after a request should we confirm?

As soon as possible, ideally within minutes. A quick confirmation tells the user they were heard, even if the full answer takes longer.

More free tools for software companies

Read the guide: Answer your users' messages with an AI agent.