Skip to content
Skip to content
Skip to content

Insight

About 70 % of tickets can close on their own. The other 30 % is where the setup matters.

2 Sep 2026 · 6 min read

Insight

About 70 % of tickets can close on their own. The other 30 % is where the setup matters.

2 Sep 2026 · 6 min read

Insight

About 70 % of tickets can close on their own. The other 30 % is where the setup matters.

2 Sep 2026 · 6 min read

An AI agent in your helpdesk can answer most of what arrives. The question is which messages it should answer, which it should draft, and which it should never touch.

Answer outright

Questions with a factual answer that exists in your own material: delivery times, how to reset a password, what the returns window is, where an order is. The agent reads the order record and the help centre, answers in your voice and closes the ticket. We measure these at about 70 % of volume for online retailers.

Draft for a person

Anything that involves a decision: a goodwill refund, a change to a contract, a complaint about a person. The agent prepares the reply and the context; a human reads it and presses send. The reading takes 20 seconds. The writing used to take five minutes.

Never touch

  • Legal threats and anything mentioning a regulator
  • Safety issues
  • A customer who has written three times about the same thing

These go to a named person within minutes, with everything attached.

Give it the facts, not the internet

An agent that answers from your help articles and your order data is accurate. One that answers from general knowledge is confident and wrong. The difference is the setup, not the model.

Every answer the agent sends is logged with the source it used. If a customer disputes it, you can see exactly why it said what it said.

Measure three things

Tickets closed without a person, the reopen rate on those tickets, and the satisfaction score on them compared with human replies. If the second number climbs, narrow what the agent is allowed to answer.

Something in your week that should run itself?

Tell us what eats the hours. A 20-minute call, a map of the first workflow, no deck.

Book a 20-minute call

An AI agent in your helpdesk can answer most of what arrives. The question is which messages it should answer, which it should draft, and which it should never touch.

Answer outright

Questions with a factual answer that exists in your own material: delivery times, how to reset a password, what the returns window is, where an order is. The agent reads the order record and the help centre, answers in your voice and closes the ticket. We measure these at about 70 % of volume for online retailers.

Draft for a person

Anything that involves a decision: a goodwill refund, a change to a contract, a complaint about a person. The agent prepares the reply and the context; a human reads it and presses send. The reading takes 20 seconds. The writing used to take five minutes.

Never touch

  • Legal threats and anything mentioning a regulator
  • Safety issues
  • A customer who has written three times about the same thing

These go to a named person within minutes, with everything attached.

Give it the facts, not the internet

An agent that answers from your help articles and your order data is accurate. One that answers from general knowledge is confident and wrong. The difference is the setup, not the model.

Every answer the agent sends is logged with the source it used. If a customer disputes it, you can see exactly why it said what it said.

Measure three things

Tickets closed without a person, the reopen rate on those tickets, and the satisfaction score on them compared with human replies. If the second number climbs, narrow what the agent is allowed to answer.

Something in your week that should run itself?

Tell us what eats the hours. A 20-minute call, a map of the first workflow, no deck.

Book a 20-minute call

An AI agent in your helpdesk can answer most of what arrives. The question is which messages it should answer, which it should draft, and which it should never touch.

Answer outright

Questions with a factual answer that exists in your own material: delivery times, how to reset a password, what the returns window is, where an order is. The agent reads the order record and the help centre, answers in your voice and closes the ticket. We measure these at about 70 % of volume for online retailers.

Draft for a person

Anything that involves a decision: a goodwill refund, a change to a contract, a complaint about a person. The agent prepares the reply and the context; a human reads it and presses send. The reading takes 20 seconds. The writing used to take five minutes.

Never touch

  • Legal threats and anything mentioning a regulator
  • Safety issues
  • A customer who has written three times about the same thing

These go to a named person within minutes, with everything attached.

Give it the facts, not the internet

An agent that answers from your help articles and your order data is accurate. One that answers from general knowledge is confident and wrong. The difference is the setup, not the model.

Every answer the agent sends is logged with the source it used. If a customer disputes it, you can see exactly why it said what it said.

Measure three things

Tickets closed without a person, the reopen rate on those tickets, and the satisfaction score on them compared with human replies. If the second number climbs, narrow what the agent is allowed to answer.

Something in your week that should run itself?

Tell us what eats the hours. A 20-minute call, a map of the first workflow, no deck.

Book a 20-minute call
A logistics depot at dusk, the loading doors still lit

Book a call

Pick what fits. On the call we map the first workflow, the tools it touches and the week it goes live.

Your brief0 / 2 picked
01Team size
02What eats your timepick several
Book a 20-minute call

No contract · First workflow live in 14 days

A logistics depot at dusk, the loading doors still lit

Book a call

Pick what fits. On the call we map the first workflow, the tools it touches and the week it goes live.

Your brief0 / 2 picked
01Team size
02What eats your timepick several
Book a 20-minute call

No contract · First workflow live in 14 days

A logistics depot at dusk, the loading doors still lit

Book a call

Pick what fits. On the call we map the first workflow, the tools it touches and the week it goes live.

Your brief0 / 2 picked
01Team size
02What eats your timepick several
Book a 20-minute call

No contract · First workflow live in 14 days

Book a call
An open-plan office at dusk, screens still lit

London3 workflows running

Runs on Zapier · Make · n8n · custom agents

Book a call
An open-plan office at dusk, screens still lit

London3 workflows running

Runs on Zapier · Make · n8n · custom agents

Book a call
An open-plan office at dusk, screens still lit

London3 workflows running

Runs on Zapier · Make · n8n · custom agents

Create a free website with Framer, the website builder loved by startups, designers and agencies.