Meet Tess, IT Ops Manager (AI)

One AI manager. Eight specialists. A senior engineer behind every fix.

Tess is our IT Ops Manager (AI). She answers in the chat at any hour, asks the questions an engineer would ask and hands the request to the INTE SYSTEMS Senior Engineer, who is accountable for the fix. First replies and briefs on every ticket are rolling out.

See what we show you

Watch her think

An example of what she is built to do in the first minute after you send a message. It is a demonstration: her specialists run on example data today. Press play.

An example message

"Since this morning nobody in accounts can send email. Clients are waiting."

  1. Sorts it

    Email, urgent, affects a whole team. Service Delivery opens the ticket and gives you a number.

  2. Checks what we already know

    Finds an approved fix from past tickets: "outgoing relay timing out".

  3. Picks the right check

    Technical Operations chooses one diagnostic and lists the evidence still needed.

  4. Rules out the scary option

    Security and Risk confirms there is no sign of a hacked mailbox.

  5. Hands over, clearly

    The INTE SYSTEMS Senior Engineer gets one clear brief and approves the fix. You get an update in plain words.

Her team

Tess's specialists are AI agents, each with one job and a strict list of what it may do. They have no faces because they are not people: each is a small orb with its job on it.

Service Delivery

Reads every new request

  • Sorts it by category and urgency, and spots sensitive requests
  • Finds an approved fix from past tickets
  • Picks the right first check for the problem

Writes and sends nothing to you without approval.

Technical Operations

Watches your devices

  • Turns a device alert into an incident, linked to the history
  • Checks recent changes and your health score
  • Asks for a read-only check when something looks serious

Changes nothing on a device: a technician does the work.

Security and Risk

First look at anything suspicious

  • Opens an incident for every security event
  • Sorts it and finds approved guidance
  • Puts actions like isolating a laptop to our Senior Engineer

Isolates no device and disables no account on its own.

Financial Management

Keeps the numbers honest

  • Adds up the hours recorded on every ticket
  • Totals a quote line by line
  • Checks a contract against what you are entitled to

No estimates and no invoices: only sums of recorded figures.

Customer Relations

Never lets a follow-up slip

  • Checks every follow-up that is due
  • Reads your feedback score and flags a low one
  • Asks for your consent when something needs it

Sends you nothing and promises nothing without a person.

Business Operations

Your daily brief

  • Counts the day's tickets, incidents, approvals and repeat problems
  • Reads your health score
  • Suggests where to look, with the numbers behind each suggestion

Decides nothing: suggestions go to a person.

Knowledge and Quality

Learns from every fix

  • Turns each solved ticket into a draft article
  • Flags advice that contradicts what we already know

Publishes nothing until a named reviewer approves it.

Tess AutoOps

Ready-made fixes, safely

  • Checks a fix-script is approved for your organisation
  • Reads how reliable it has been on past jobs
  • Asks permission before it may run

Runs nothing on a device today.

Where they are today. All eight are built and tested inside Tess's engine, and every action they ask for is recorded. They are not yet connected to your systems: the work on your devices is done by a named engineer.

Smart, and on a short lead

Intelligence is only useful if you can trust it. Every action an agent can ask for sits in one of four classes.

Does it, and records it

Sorting a ticket, finding an approved fix, adding up recorded hours.

Asks first

Sending you an acknowledgement or a follow-up, preparing a quote, running a read-only check.

Needs our Senior Engineer

Isolating a device, disabling an account, changing a security policy, publishing knowledge.

Try her now

Each one opens the chat and asks it for you. If you are on a plan she gives you the fix where it is safe to. If you are not, she tells you what it will cost and logs a ticket only when you say yes.

What Tess does, and what she does not

"IT Ops Manager (AI)" is her job, not a qualification. She is software, and these are her limits.

She does

  • Answer in the chat at any hour
  • Ask the questions an engineer would ask, so the fix starts sooner
  • Tell you what the work costs, from our published prices
  • Help you log a ticket or send an enquiry
  • Hand the engineer a clear summary of what you told her
  • Say she is AI in the first line, every time

She does not

  • Connect to your systems or change anything on them
  • Give steps that could lose data or need administrator rights: those go to the engineer
  • Promise a time, a price or an outcome on the engineer's behalf
  • Ask for passwords, codes or card numbers
  • Close, cancel or delete a ticket
  • Pretend to be a person

From your message to a fix

Every request follows the same five steps. Steps 1 and 4 are live. Steps 2, 3 and 5 are rolling out on tickets.

  1. You ask

    In the chat, by email or on the request form. A request becomes a ticket with a number.

  2. Tess replies

    In the chat she answers at once and asks for anything that is missing. The first reply on every ticket is rolling out.

  3. She writes the brief

    Rolling out: category, urgency, the likely cause and what to check first, on the ticket for the engineer.

  4. The Senior Engineer fixes it

    A person does the work and every change, and records it on the same ticket.

  5. Tess learns

    Rolling out: she will write up what the fix was, so the next time it happens the answer is already known.

What is live and what is rolling out

Each part is labelled. Nothing moves to live until it is running for clients.

Questions about Tess

If yours is not here, .

Is Tess a real person?

No. Tess is AI, built by INTE SYSTEMS on Claude, a model from Anthropic. She says so at the start of every chat and every reply.

Can Tess get it wrong?

Yes. She is good at diagnosis and explanation, and she can still be wrong. That is why she does not change anything, and why an engineer is accountable for every ticket.

How do I reach a person?

Reply to any message or tell Tess you want an engineer. Every ticket already goes to one, so you are never waiting for Tess to decide.

What does Tess see?

The text of your chat or ticket, and nothing else. She has no access to your systems, files or passwords. That text is sent to Anthropic to produce her reply, which may mean it is processed outside South Africa. See our privacy notice.

Is she available all day, every day?

Tess answers in the chat at any hour. Engineers work the helpdesk hours shown on this site. Urgent out-of-hours cover is agreed per client.

Can we opt out?

Yes. Tell us and your tickets are handled by an engineer from start to finish.

Not sure where your IT stands?

A free IT health check looks at your accounts, backups, updates and network, and gives you a short written report. No obligation.

Get a free IT health check