For customer serviceIRIS8
Replies drafted from your own policies
A model trained on your policies and past tickets drafts the reply, and your agent sends it.
The briefIRIS8
What this team answers for
- 01Replies that match the policy
- 02Complaints handled and recorded properly
- 03Customer account details kept inside the firm
The workflowIRIS8
The workflow, step by step
Your VPC or data centre
Your people
Your systems
Added by IRIS8
IRIS8 engineerScoped, logged access
Your records
Your model and the restIRIS8
Where your own model fits
On your own model
Ticket sorting and routing
The model tags each ticket by type and urgency.
A team lead reviews the routing rules.
Reply drafts from your policies
The model drafts the reply and cites the clause.
The agent sends it.
Call and chat summaries
The model summarises the conversation.
The agent checks it before it is saved to the account.
Complaint categorisation
The model sorts complaints into your categories.
The complaints officer reviews them.
Conversation quality checks
The model marks conversations against your checklist.
The quality lead reviews the marks.
Keep on a frontier model
Long complaints that span several products and need open-ended reasoning, sent through your gateway with account details masked.
Your dataIRIS8
Why not a public AI tool
A support ticket carries an account number, an address and often the details of a complaint. Pasted into a public tool, those leave the firm. Your own model reads them where they already sit, and the request is logged.
QuestionsIRIS8
Five questions heads of customer service ask us
- 01
Will the model talk to customers directly?
In a pilot, no. It drafts and your agent sends. The agent can edit any draft or reject it, and the record shows who sent each reply. Whether any reply type is ever sent without review is your decision, taken later and on the evidence of your own benchmark.
- 02
How do we know a draft follows our policy?
Before go-live the model is scored on past tickets your team has already answered well, at a pass mark you set. Each draft shows the policy clause it used, so the agent can check it in seconds and a reviewer can check it later.
- 03
What happens with a question it has not seen before?
It goes to a person. You can also set a rule at the gateway that sends named ticket types to a frontier model, with account details masked first. Nothing takes that route unless you have allowed it.
- 04
Where do our customers' details go?
They stay in your environment. The model runs in your VPC or on-prem, next to your ticketing system. Named IRIS8 engineers work there with scoped access, and every action they take is logged.
- 05
How do we start?
With an 8-week fixed-price pilot on one use case, credited to year one. You pick the ticket types, your team sets the pass mark, and we report the scores against it whether the model passes or not.
First pilotIRIS8
A first workflow to pilot
Reply drafting for the most common ticket types in one product line.
Draft reply
Thank you for getting in touch. A refund for a cancelled order is paid back to the card you used. You do not need to do anything further.
Policy clause usedRefunds and cancellations, clause 3
Waiting for the agent to review
For your teamIRIS8
Take back to your team
Next stepIRIS8