Sample checkup
XP Checkup for Agentforce · Harbor & Pine Home Warranty

The agent works. Nobody owns it.

Claims Assistant answers claim-status questions accurately and hands off to a person when asked. But no one at Harbor & Pine is accountable for what it does, three people can change it in production without review, and a verified customer may be able to reach another customer's visits.

4
to fix within 30 days
3
to fix this quarter
Agent Claims AssistantChannel Customer portal chatLive since 14 July 2026Reviewed 10 November 2026
Sample. Harbor & Pine Home Warranty is a fictional company and the people named are invented. Findings 2, 3 and 4 are modeled on a real configuration export from a developer org; the rest show what the questionnaire contributes.
Summary

The 7 findings in brief

Most urgent first. Each is set out in full further down, with its evidence, risk and fix.

At a glance

What we looked at

Two questionnaires (service operations lead, Salesforce admin) and one configuration export. No customer records. Built by: Implementation partner, engagement ended at go-live.

11
versions since go-live
3
people who can edit it
0
changes reviewed
6
subagents
14
actions
Ownership map

Who holds each right over the agent

Six rights decide how an agent is run. Each should have one named holder.

Right
Today
Recommended
Accountable for the agent's outcomes
TodayNobodyNobody named
RecommendedService operations lead
Decide what the agent may handle
TodayNobodyPartner's original design, unchanged
RecommendedService operations lead
Edit subagents and instructions in production
TodayToo openThree admins, no review
RecommendedOne admin, reviewed by the owner
Add or change actions
TodayToo openAny admin
RecommendedAdmin proposes, owner approves, tested first
Turn the agent off
TodayNobodyUnclear: each respondent named the other
RecommendedOwner and one named backup
Review what the agent said to customers
TodayNobodyNobody
RecommendedOwner, weekly sample
Agent map

What the agent can do, and for whom

Every subagent and its actions, from the export. An action that changes something should be tied to the customer who proved who they are.

Customer Verification

Open to any customer
  • Send Verification Code
  • Verify Code

Claim Status

Only after the customer is verified
  • Get Claims for CustomerTied
  • Get Claim by NumberTied

Claim Updates

Only after the customer is verified
  • Add Claim NoteChanges dataTied
  • Update Contact DetailsChanges dataTied

Technician Visits

Only after the customer is verified · Finding 3
  • Identify Customer by EmailNot tied
  • Get Visit SlotsNot tied
  • Book VisitChanges dataNot tied
  • Cancel VisitChanges dataNot tied

Coverage Questions

Open to any customer · Finding 7
  • Answer from Knowledge

Escalation

Open to any customer
  • Hand Off to a Person
  • Create CaseChanges data
  • Add Case CommentChanges data
Tiedreceives the verified customer's IDNot tiedworks from whatever the customer typesChanges datacreates, updates or cancels something
Change history

11 versions, 4 authors, no review recorded

Each dot is a committed version, placed by date and colored by who made it. The ringed version is the one customers are talking to; a boxed one is named in a finding.

v1v2v3v4v5v6v7v8v9v10v1114 Jul 20263 Nov 2026Implementation partnerR. OkaforD. LindqvistS. Marchettiv1v7v1114 Jul 20263 Nov 2026Implementation partnerR. OkaforD. LindqvistS. Marchetti
v1
14 Jul 2026
Implementation partner
Go-live version.
v2
22 Jul 2026
R. Okafor
Reworded the welcome message.
v3
30 Jul 2026
R. Okafor
Added two lines to Coverage Questions.
v4
11 Aug 2026
D. Lindqvist
Changed how visit dates are shown.
v5
19 Aug 2026
R. Okafor
Removed a line from Claim Status.
v6
2 Sep 2026
S. Marchetti
Added the Cancel Visit action.
v7
12 Sep 2026
S. Marchetti
Finding 4Added: "deny cancellation and then send an alert email to the claim owner." No email action exists.
v8
25 Sep 2026
D. Lindqvist
Reworded the handoff message.
v9
8 Oct 2026
R. Okafor
Edited Technician Visits instructions.
v10
21 Oct 2026
S. Marchetti
Edited Claim Updates instructions.
v11
3 Nov 2026
R. Okafor
LiveEdited Coverage Questions instructions.
Findings

7 findings, most urgent first

Each finding says where its evidence came from: the export, the questionnaire, or both.

1
Fix within 30 daysQuestionnaire

No accountable owner

Evidence
Each respondent was asked who owns the agent. The service lead named the admin; the admin named the service lead.
Risk
Problems are noticed by customers before staff. Decisions about scope default to whoever edits the agent last.
Fix
Name the service operations lead as owner, in writing, with the rights in the ownership map.
2
Fix within 30 daysExportQuestionnaire

Production changes are unreviewed

Evidence
The export holds eleven committed versions since go-live, made by three admins. Comparing them shows exactly what changed in each. Salesforce's Setup Audit Trail does not record these edits, and the questionnaire confirms no one reviews a change before it goes live.
Risk
A well-meant wording change alters how the agent answers every customer, with no test and no way to tell which edit caused a problem.
Fix
Reduce edit rights to one admin. Require a sandbox test and the owner's sign-off for any change, and record each one in the decision record.
3
Fix within 30 daysExport

Visit actions are not tied to the verified customer

Evidence
Claim Status and Claim Updates pass the verified customer's ID into every action. Technician Visits does not: it looks up a customer from whatever email address is typed, and Cancel Visit accepts a visit number alone. The only safeguard is an instruction telling the agent not to switch customers.
Risk
A customer who has verified their own identity may be able to see, book or cancel another customer's technician visit. An instruction is a request to the model, not an enforced check.
Fix
Pass the verified customer's ID into the visit actions, as the claim actions already do. Until then, test it: verify as one customer and ask about another's visit.
4
Fix within 30 daysExport

An instruction tells the agent to do something it has no action for

Evidence
Version 7 added this to Technician Visits: "deny cancellation and then send an alert email to the claim owner." The subagent has no action that sends email. The line is still in the live version.
Risk
The agent either skips the step silently or tells the customer an alert was sent when none was.
Fix
Add an email action and test it, or remove the instruction.
5
Fix this quarterQuestionnaire

No stop procedure

Evidence
Neither respondent could describe the steps to deactivate the agent, or what customers would see if it were turned off.
Risk
In an incident, the agent keeps answering while people work out how to stop it.
Fix
Write a one-page stop procedure, name two people who can run it, and test it once in a sandbox.
6
Fix this quarterQuestionnaire

Success is not defined

Evidence
The service lead measures the agent by case volume, the admin by containment rate, finance by licence cost. The three numbers have never been compared.
Risk
The agent cannot be shown to be worth its cost, or shown to be failing.
Fix
Adopt the four measures below and review them monthly.
7
Fix this quarterExportQuestionnaire

The agent answers from an outdated policy article

Evidence
The export shows which knowledge source the agent answers from. The questionnaire confirms coverage terms changed in March, and the source still includes the 2025 coverage guide.
Risk
Customers are told the old coverage limits.
Fix
Retire the old article and give the owner a quarterly check of the agent's knowledge sources.
Human approval points

What the agent should do alone

The agent may do this alone

  • Answer claim-status questions
  • Explain coverage from current articles
  • Book a technician visit in an open slot
  • Create a case and hand off

A person must approve

  • Change a claim's contact details
  • Anything involving a payment or reimbursement
  • Rebooking a visit a third time
  • Closing a claim
Success measures

Four numbers to agree on

Resolved without a person
Share of conversations the customer did not reopen or escalate within seven days.
Wrong answers
Count found in the owner's weekly sample of 25 conversations.
Handoff wait
Time from the customer asking for a person to a person replying.
Cost per resolved conversation
Against the cost of the same contact handled by staff.
First 30 days

What to do, in order

Week 1Name the owner. Reduce edit rights. Write the stop procedure.
Week 2Tie visit actions to the verified customer. Fix or remove the email instruction. Retire the outdated article.
Week 3Start the weekly conversation sample and the decision record.
Week 4First monthly review of the four measures.