Spaces

Your first week with an AI agent at a software or IT firm

This checklist walks a software or IT firm through the first week of an AI agent answering client messages, from writing down support hours to reviewing the first chats. It suits small and mid-sized firms.

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

Before you start

Most software firms already have the knowledge an agent needs. It lives in a wiki nobody updates, in the head of the person who answers support, and in old ticket replies. The first week is about getting that knowledge into a form your agent can use, and watching closely while it learns the rhythm of your clients.

Work through the list in order. Do the early items before you switch anything on, and the later ones as real chats arrive. Keep a person close to the chats for the whole week, because the best corrections come from reading actual conversations while they are fresh.

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

[ ] Write down your support hours and what happens outside them.
[ ] Define your severity levels in plain words, with one example each.
[ ] Name the on-call person and a backup for the week.
[ ] List the services you offer and the projects you do not take.
[ ] Collect the five questions you answer most often, with good replies.
[ ] Decide what ticket details the agent may share, and with whom.
[ ] Run ten pretend messages through the agent before going live.
[ ] Go live with existing clients first, not a public contact route.
[ ] Read every chat on day one and two, then a sample each day.
[ ] Hold a fifteen minute review on day seven and fix what you found.

What to expect in the first few days

Expect the agent to ask clients for details more often than you would. That is usually fine, and it can be tuned. Expect a few answers that are right but too long. Trim the instructions and the next ones are shorter.

Do not expect it to know things you never wrote down. If a client asks about a release date and nobody gave the agent a release calendar, it should say it will check. That is the correct behaviour, and it tells you what to write next.

Common first-week stumbles

Firms like {business} tend to hit the same few problems.

  • Severity levels so vague that every message looks urgent.
  • No backup for the on-call engineer, so a missed call stalls a handover.
  • Sharing too much ticket detail with the wrong contact at a client.
  • Forgetting to tell the team the agent is live, so staff and agent both reply.

FAQ

Do we need to document everything before we start?

No. Start with support hours, severity levels, your services and the five most common questions. Add more each week as real chats show you what the agent was missing.

Who should watch the chats during the first week?

Someone who knows your clients and your systems, such as the support lead or a senior engineer. They can spot a wrong answer immediately and correct the instructions the same day.

Is it safe to start with live clients?

Yes, if the handover rules are clear and a person is on call. Start with known clients who write to you already, and keep sensitive topics with your engineers from day one.

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.