Response Speed
92/100
Fast initial acknowledgment
Human Score™ report example
Illustrative fictional example only — not a client audit or verified outcome.
This report format shows how a Human Audit turns a customer journey into specific evidence, a practical scorecard, and a prioritized view of what to fix first.
Scorecard
Response Speed
92/100
Fast initial acknowledgment
Human Connection
38/100
Urgency is not recognized
Sales Experience
61/100
Next step lacks context
Follow-Up
74/100
Prompt, but generic
Customer Friction
47/100
Handoff creates repeat work
Fictional example · not a benchmark, certification, or outcome promise
At a glance
58/100
Illustrative overall score
Fictional journey timeline
Time stamps and interactions are illustrative test observations only.
00:00
Phone call
Test caller describes a no-cooling issue and asks for same-day help.
00:22
AI response
Automated receptionist confirms the business is open and requests a ZIP code.
01:41
Handoff
Caller is asked to repeat the issue after choosing an appointment window.
06:08
Text follow-up
An automated message offers a booking link without acknowledging the urgency stated on the call.
00:00
Phone call
Test caller describes a no-cooling issue and asks for same-day help.
00:22
AI response
Automated receptionist confirms the business is open and requests a ZIP code.
01:41
Handoff
Caller is asked to repeat the issue after choosing an appointment window.
06:08
Text follow-up
An automated message offers a booking link without acknowledging the urgency stated on the call.
Evidence record
High-level evidence remains visible below; open the additional fictional observations when you want the detail.
Illustrative/test observation 01
The initial response arrives quickly, but no language signals that the stated loss of cooling is urgent or understood.
Illustrative/test observation 02
The phone path collects the issue, then the scheduling handoff asks the test caller to restate it before offering a next step.
Illustrative/test observation 03
The follow-up text is prompt and clear, but it reads the same for an urgent repair request and a routine service inquiry.
Illustrative/test observation 04
A human callback is mentioned in the automation, but this fictional sample does not show a clear ownership cue or expected callback window.
Illustrative/test observation 02
The phone path collects the issue, then the scheduling handoff asks the test caller to restate it before offering a next step.
Illustrative/test observation 03
The follow-up text is prompt and clear, but it reads the same for an urgent repair request and a routine service inquiry.
Illustrative/test observation 04
A human callback is mentioned in the automation, but this fictional sample does not show a clear ownership cue or expected callback window.
Fictional example
Prioritized friction findings
Priority 01
Preserve the stated problem and urgency from the first interaction so the next person—or system—does not reset the conversation.
Priority 02
Keep the fast text-back, then add the specific context the customer already shared and a clear owner for the next step.
Priority 03
If a human callback is offered, state who follows up and when, rather than leaving the customer to interpret an automated message.
Apply this to your journey
Use a Human Audit to review your own customer-facing experience, not this fictional example.
What the Human Audit includes
Included in the Human Audit
Separate paid implementation
Your actual customer journey
After checkout, you confirm the journey to review; HumanEyes Labs assesses your own customer-facing experience, not this fictional example.
Prefer to review the scope first? Explore the Human Audit or contact HumanEyes Labs.