Merlewood Row

AI agents and the customer service they promise. Reviews and practical guides for teams in FCA-regulated UK firms.
Last updated:

Buying guide

A faster reply is not a finished task

A policyholder asks for a replacement document. Use that ordinary request to decide what an agent should do, what staff should keep and how you will recognise success.

Published
Updated
Contents
  1. Start at the customer’s end
  2. Count the requests still waiting
  3. Choose the job before the platform
  4. Write down what a pass looks like

Start at the customer’s end

Imagine a policyholder asking an insurer for a replacement document. Finding a file and pressing send sounds like the job. But the customer needs the right, current document, delivered through a channel they can use. They also need to understand what they received and where to ask for help. Use that fuller description when writing the brief. A quick message to the wrong address, or an obsolete attachment, should not count as a resolved request.

Put the job on a short sheet: who the service is for, what they ask, which information it may use and what a finished request looks like. Add what it must leave alone. In this example, keep changes to cover, prices, renewal choices and claims decisions outside the agent’s job. Send those questions to the appropriate team. Your compliance colleagues should decide which requirements apply to the service; a supplier’s sales description cannot make that decision.

Count the requests still waiting

Nexus says each deployed agent has a measurable business KPI. Kore.ai describes its optimisation engine improving agents against defined goals.1,2

That makes the choice of goal part of the buying decision. In the document example, count correct deliveries, requests passed to staff, repeat contacts and cases still waiting, as well as handling effort. Agree how someone checks that the document is correct and current. Keep that judgement attached to the original request. Otherwise, a report showing fast replies can leave the service manager unable to tell which customers received the help they asked for.1,2

Before setting targets, choose approved examples of the work: a routine request, someone unable to use the default channel, an unclear policy reference and a request for a different service. Compare them with the process you run today. Look at each group separately; a single average could hide the difficult case. Choose any numerical targets from that starting point and your firm’s risk appetite. This guide supplies the questions, not a promised success rate.

Choose the job before the platform

Hebbia describes Max producing research spreadsheets, slides and reports with traceability back to findings. WRITER describes grounding agents in brand, product and customer knowledge.3,4,5

These are useful starting points for different jobs. For a research pack, you may care most about checking where a finding came from. For a letter draft, approved information and staff review may matter more. Sending the document adds another question: is it going to the right person? Decide where the agent stops and an existing service or colleague takes over. The ability to automate a step is not, by itself, a reason to include it.3,4,5

For the insurer, a useful first version might prepare the document and proposed recipient for staff to check. Any move to automatic sending becomes another decision, supported by what that narrower trial shows. Ask suppliers to quote for the same work, including staff review and the cases that need help. A cheaper proposal that leaves those jobs out is describing a different service. Keep them visible when you compare the offers.

Write down what a pass looks like

Nexus’s published launch rule covers sign-off on data flow, access and the audit trail. Microsoft documents approval gates between development, test and production.6,7

Give those launch discussions a customer example. Your acceptance sheet might say: the correct current policy was found; the intended recipient was checked; sending was authorised and recorded; delivery was confirmed. If delivery remains unresolved, someone in customer service takes the case. Add a rule to stop when identity is unclear and a route for questions outside the agreed job. These are checks we suggest discussing with the supplier, not results we have observed in a product.6,7

Finish with a decision: proceed with the agreed job, change the design and repeat the affected cases, or keep the existing service. Name the evidence and the person responsible for any conditions. A launch date should not expand what the agent is allowed to do. If the team changes the job, update the customer result you expect and the checks that establish it. That leaves the next reviewer a decision they can understand.

How to read the evidence

We used supplier material checked on 8 November 2026 and wrote these examples on 9 November 2026. Information supplied directly by Nexus is identified separately. The exercises are suggestions for your team; Merlewood Row has not run them. Your firm’s reviewers decide which obligations apply and whether the proposed use is acceptable.

  • Our suggested approach to this example. It is not a result we have measured.
  • A question to settle with the supplier for your service. It is not a finding about capability or compliance.
  • Supplier material checked on 8 November 2026. We have not tested the described feature or measured the result.
  • The suppliers describe work against goals. The customer-service measures here are our suggestions.
  • We use the documented outputs to suggest which part of the service each product might suit.
  • We suggest turning the published launch checks into results your service team can examine.

Sources

  1. Every agent deployed has a measurable business KPI from day one. agent.nexus/blog/nexus-raises-4-3m-seed-shipping-cue, checked 8 November 2026.
  2. Autoloop is the optimization engine that improves agents against goals from first build through production (vendor claim). kore.ai, checked 8 November 2026.
  3. Max is described as: "Max works the way your firm works, researching and analyzing any deal to produce client-ready spreadsheets, slides, and reports.". hebbia.com/product, checked 8 November 2026.
  4. Max runs analysis over documents with traceability: "Reason over any volume of documents or companies with precise analysis and complete traceability back to every finding.". hebbia.com/product, checked 8 November 2026.
  5. Enterprise Brain is described as the universal context layer that grounds agents.. writer.com, checked 8 November 2026.
  6. Blog: the agent does not ship unless a CIO can sign off on data flow, access model and audit trail. agent.nexus/blog/nexus-raises-4-3m-seed-shipping-cue, checked 8 November 2026.
  7. Release pipelines and approval gates support Dev-Test-Prod promotion.. microsoft.com/en-us/copilot/products/copilot-studio, checked 8 November 2026.