Spaces

The first-reply checklist for software and IT client messages

This checklist shows what the first reply to a new message should contain when the sender is a client with a broken system or a prospect with a project in mind. It is made for software, web and IT support firms.

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

Before you start

Clients of a software or IT firm write for two very different reasons. One has a site that is down and customers who cannot pay. The other wants to know whether you build booking systems and roughly what that costs. Both judge you on the first reply, and the first reply has to tell them apart.

Read each point and tick the ones your team, or your AI agent, already does. Every gap is a place where an engineer later has to ask the same question again. Pin the list near the support desk, or go through it at your next stand-up with the person who watches the inbox.

Tick each one as you go. 0 of 10 done.

[ ] Say who you are and which client or project the message is about.
[ ] Tell urgent reports apart from ordinary questions in the first line.
[ ] For a fault, ask for the page or screen, the time it began and the exact error text.
[ ] Ask for a screenshot or a short screen recording.
[ ] Ask how many people are affected and whether work has stopped.
[ ] Confirm receipt and say when they will hear next.
[ ] For a new project enquiry, ask what the system must do and who will use it.
[ ] Ask roughly when they need it and whether a budget range exists.
[ ] Remind them never to send passwords in the chat.
[ ] Finish with one clear next step.

What a strong first reply sounds like

Picture a client writing that the order export is empty. A good reply from {business} might read: Thanks, I have logged this as a ticket. Which export, and about what time did you last see data? A screenshot would help too. An engineer will look within the hour.

That reply names the action, asks for two facts and promises a time. It does not diagnose the cause, and it does not apologise for three lines. The engineer picks up a ticket that already has the facts they need.

Mistakes that slow down support

These show up again and again in client chats at software firms.

  • Replying with a link to the whole help centre instead of an answer.
  • Asking for a login so you can have a look yourself.
  • Guessing a cause before an engineer has seen the logs.
  • Leaving a prospect waiting a day while you decide who owns the lead.

FAQ

How fast should we answer a first message from a client?

Acknowledge urgent faults within minutes, even if the fix takes hours. For ordinary questions and new project enquiries, a considered reply within a working hour or two is a good aim.

Can our agent tell an outage from an ordinary question?

Yes, if you give it clear severity rules, such as payments failing or a whole site down. Anything it is unsure about should be treated as urgent and passed to a person.

What if the client never sends the details we asked for?

Send one gentle follow-up in the same chat. They wrote to you, so a reminder is fine, but if the fault is serious, an engineer should pick up the phone instead.

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.