IRIS8 Talk to us

For customer service

Replies drafted from your own policies

A model trained on your policies and past tickets drafts the reply, and your agent sends it.

The brief

What this team answers for

  1. 01Replies that match the policy
  2. 02Complaints handled and recorded properly
  3. 03Customer account details kept inside the firm

The workflow

The workflow, step by step

Sample workflow · reply drafting for a support ticketSample workflow
Frontier modelOptionalOff by default. Only for ticket types you allow, with account details masked
Yours

Your VPC or data centre

Your people

Support agentReviews and sends
Head of Customer ServiceSets the pass mark

Your systems

Ticketing system
Knowledge base and policy library
Customer account records
Call and chat transcripts

Added by IRIS8

GatewayMasks, routes and logs
Your modelTrained on your policies and past tickets

IRIS8 engineerScoped, logged access

Your records

Request logEvery request and response
Model recordData, training runs, scores, approvals
Benchmark reportYour cases, your pass mark

Your model and the rest

Where your own model fits

Yours

On your own model

  1. Ticket sorting and routing

    The model tags each ticket by type and urgency.

    A team lead reviews the routing rules.

  2. Reply drafts from your policies

    The model drafts the reply and cites the clause.

    The agent sends it.

  3. Call and chat summaries

    The model summarises the conversation.

    The agent checks it before it is saved to the account.

  4. Complaint categorisation

    The model sorts complaints into your categories.

    The complaints officer reviews them.

  5. 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 data

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.

Questions

Five questions heads of customer service ask us

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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 pilot

A first workflow to pilot

Reply drafting for the most common ticket types in one product line.

Ticket · refund questionSample data

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

Next step

Bring your most common ticket type