Spaces

Is your software or IT firm ready for an AI agent? A quick quiz

This quiz asks eight yes or no questions about whether a software or IT firm has what an AI agent needs to answer client messages well, such as written procedures, severity levels and an on-call person.

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

Before you start

An agent is only as good as what you give it to work from. A software firm often has the knowledge, but scattered across a wiki, a ticket tool and the memory of the person who has been there longest. Before an agent starts answering clients, it helps to know which pieces you already have and which you still need.

Answer each question for how things are today. A no is not a failure, only a task. Your result shows how ready you are, and the text under each band suggests what to prepare before switching an agent on for your clients.

Do you have written support hours that clients can see?
Do you have written severity levels, with an example of each?
Is there a named person who can take an urgent handover at any time you offer support?
Do you have a written list of the services you provide and the projects you do not take?
Do you have a secure way for clients to share credentials, other than chat?
Do you keep notes of common client questions and the answers you give?
Can you say who may see ticket details and who may not?
Is someone able to read the agent's chats every week and correct them?

Answer all 8 to see your result. 0 so far.

Why written material matters so much

An agent cannot read a senior engineer's mind. It can only use what you have written. A paragraph describing what counts as an urgent fault is worth more than any clever setting, because it is the line between a calm reply and a missed outage.

The good news is that most of this material already exists in some form at {business}. You are collecting and tidying it, not inventing it from scratch.

If you answered no to the person question

A hand-over route is the most important thing on the list.

  • Name one person for each support hour you offer, plus a backup.
  • Agree how they will be alerted, and how fast they should reply.
  • Test it once with a pretend urgent chat.
  • Write down what the agent should say if nobody answers.

FAQ

Do we need everything written down before we start?

No. Support hours, severity levels and a named person are the essentials. Everything else can grow from the real questions clients ask in the first weeks.

Will an agent replace our support engineers?

It takes over the routine messages and gathers the facts, so engineers spend their time on real faults. Serious, sensitive and technical matters always stay with your people.

How long does it take to get ready?

Many firms are ready in a day or two of focused writing. The slowest part is usually agreeing severity levels and who is on call, which is worth doing anyway.

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.