Confirmation messages for licences, upgrades and trials
These confirmation messages tell a software customer exactly what was set up, such as a trial, a licence move or an upgrade, and what they should do next. They are for publishers replying to requests customers made.
Runs in your browser. Nothing you enter is sent anywhere or saved.
Before you start
A customer who asks to move a licence, extend a trial or add a seat wants proof that the request landed. A clear confirmation prevents the follow-up message asking whether it worked. It also gives you a record of exactly what you agreed.
Fill in the two boxes and choose the confirmation that matches the request. State what changed, when it takes effect and what the customer should do. Only send a confirmation for something that has really been done, never for something still waiting.
Licence moved
Hi, this is [business]. I have set up [item]. To finish, please [next step]. If anything looks wrong, reply here and a member of the team will check straight away.
Trial started
Thanks for choosing to try us at [business]. Your trial of [item] is ready. Please [next step]. Reply to this chat if you hit any problems along the way.
Seat added or changed
Hello from [business]. The change to [item] is done. Please [next step] so every person on your team sees it. Tell me if the seat count does not look right.
Upgrade or edition change
Hi, [business] here. Your move to [item] has gone through. Please [next step]. Your earlier files and settings should carry over, and I am here if they do not.
Request received, still being checked
Thanks for your request to [business]. I have passed [item] to a colleague to check. Once it is done we will tell you here, and you will then be able to [next step].
What a good confirmation holds
Three things: what was done, when it applies and what the customer does next. If a change takes a few minutes to appear, say so, or customers will message again after thirty seconds.
Add a line about what to do if it does not work. A customer who knows where to turn feels more confident and is less likely to open a second chat.
Avoiding confirmations that cause trouble
A wrong confirmation is worse than a late one.
- Do not confirm a licence move until your system shows it.
- Do not quote a price in a confirmation unless a person has checked it.
- Do not include the full key, only the last characters.
- Do not promise a feature date or a refund inside a confirmation.
FAQ
Can the agent make the change itself?
Only if you give it a tool that does so safely. Many publishers let the agent look up an account but keep changes with a person, and confirm only after the person has acted.
Should confirmations include a licence key?
Best not. Say that the key was sent to the account email, or show only the last few characters. The full key in chat can be copied by anyone who sees it.
How soon after the request should I confirm?
As soon as the change is real. A short, honest confirmation within minutes stops the customer wondering, and it saves your team from answering a second message about the same thing.
More free tools for software publishers and app makers
- First-reply checklist for software publishers and app makers
- Hand-over rules checklist for software publishers and app makers
- First-week checklist for software publishers and app makers
- Weekly chat review checklist for software publishers and app makers
- Busy-season checklist for software publishers and app makers
- Customer privacy checklist for software publishers and app makers
- Do and don't guide for your agent: software publishers and app makers
- Greeting messages for software publishers and app makers
- After-hours replies for software publishers and app makers
- Reminder messages for software publishers and app makers
- Apology and complaint replies for software publishers and app makers
- "Let me check" replies for software publishers and app makers
- Follow-up messages for software publishers and app makers
- Review request messages for software publishers and app makers
- Price and quote replies for software publishers and app makers
- Delay and stock notices for software publishers and app makers
- Thank-you messages for software publishers and app makers
- Hand-over notes for software publishers and app makers
- Ready answers for software publishers and app makers
- Holiday and closure notices for software publishers and app makers
- Missed enquiries calculator for software publishers and app makers
- AI agent instructions builder for software publishers and app makers
- Auto-reply message writer for software publishers and app makers
- FAQ answer sheet for software publishers and app makers
- Reply speed scorecard for software publishers and app makers
- Is your business ready for an AI agent? Quiz for software publishers and app makers
- Message workload planner for software publishers and app makers
- Hours saved calculator for software publishers and app makers
- Enquiry-to-customer value estimator for software publishers and app makers
Read the guide: Answer software customer messages before they become tickets.