Spaces

Confirmation messages for software and IT firms

These confirmation messages let a software or IT firm confirm a logged ticket, a booked call, a maintenance window or a change request. Fill in the details and copy the message that fits.

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

Before you start

In a software firm, a confirmation is a small act of trust. A client who hears that their ticket exists, with a number, stops worrying that the message vanished. A prospect who gets a call confirmed with a time and a name turns up prepared. Without that, both are left wondering.

Fill in the two boxes below, and every message updates to match. Use them for tickets, calls, planned maintenance and change requests. Keep the confirmation short and specific, and include exactly what was agreed. Anything not agreed should be left out.

Ticket logged

Thanks, this is logged at [business] as [reference]. An engineer has the details you sent. We will update you in this chat, and you can quote that number if you write about it again.

Discovery call booked

Your call with [business] is booked for [when]. We will talk through what you want to build, who will use it and how soon. Please send any documents or examples you have before then.

Maintenance window confirmed

Confirmed. The planned work at [business] is set for [when]. Some features may be unavailable for a short time. We will write here when it is finished. The reference is [reference].

Change request received

We have received your change request, reference [reference]. A person at [business] will review it, tell you what it involves and agree timing with you. Nothing will change on your system until then.

New user account request

Thanks for the request, reference [reference]. For safety, someone at [business] will check it with your account owner first. Once confirmed, the new user will be set up by [when].

What a good confirmation always includes

A confirmation should answer three questions: what happened, what comes next, and when. If a client can read yours and know all three, they will not need to write again.

Always include the reference number. It saves minutes on every later message, and it makes a client feel that your systems are in order.

Mistakes to avoid

A confirmation can create problems of its own.

  • Confirming a change that nobody has reviewed.
  • Giving a time you cannot be sure of, such as a fix date.
  • Leaving out the next step, so the client has to ask.
  • Sending a confirmation for access changes before the account owner has verified them.

FAQ

Can the agent confirm a call by itself?

Yes, if it can see your calendar through its own tools. Otherwise it should collect the preferred time and say a person will confirm, so no one is double booked.

Should a change request be confirmed as done?

Confirm that it was received. Only say it is done after an engineer has finished and checked it, because a wrong "done" is worse than a slower, truthful update.

How soon after a request should we confirm it?

As soon as it is logged, ideally within a few minutes. The confirmation is a receipt, and receipts matter most when the client is already a little anxious.

More free tools for software and tech support firms

Read the guide: Answer client messages at your software and IT firm, from outages to scoping.