Reputation Agent Analytics

How the Reputation Agent will be measured

The intended record for post-visit feedback: requests sent, responses received, concerns worked by staff, and review requests that stayed inside the practice's policy.

  • Feedback requests senttrending up
    190After eligible visits, on the practice's schedule.
  • Responses receivedtrending up
    121A recorded answer, not inferred sentiment.
  • Concerns routed to staffsteady by designStaff first
    14Heard by the practice before the public.
  • Concerns resolved by the teamtrending up
    12Follow-up worked to a status.
  • Approved review requests sentsteady by designPolicy-gated
    64Only where practice policy allows.
  • Opt-outs respectedsteady by designBy request
    7Excluded from the workflow.

Intended reporting for a planned capability — illustrative values, not results from a live deployment. No ratings, review volumes, or response rates are promised.

How the record is intended to work

Product direction, not a generally available capability. Once the agent ships, every post-visit conversation would move through four recorded stages.

  1. 01

    Eligible visits

    Which completed visits entered the workflow, under rules the practice would approve.

  2. 02

    Requests and responses

    Each approved feedback request and the patient's recorded answer — or the absence of one.

  3. 03

    Concerns to people

    A low score or complaint would become a staff task before anything public, with its status tracked.

  4. 04

    Review requests within policy

    Approved public review requests recorded against the policy that allowed them — and no others.

What the practice should be able to review

The intended views, once the agent ships:

  • Request delivery

    Feedback requests sent and their delivery status.

  • Response record

    Who answered, and what they said — structured, not scraped.

  • Concern queue

    Concerns waiting on staff, with the available context.

  • Resolution status

    Where each concern stands with the team.

  • Review request log

    Approved review requests, tied to the policy that permitted them.

  • Opt-out list

    Patients who asked not to be contacted, honoured everywhere.

These numbers would stay honest

The planned agent is not a tool for manufacturing reviews, and its reporting would not be either. Response counts are workflow records — never a promised rating, and never a filter that hides criticism.

The exact reporting fields and availability will be confirmed before launch.

  • No review gating in the numbers

    Concerns are counted and routed to staff — never subtracted to protect a score.

  • Staff-first is reported steady

    Concerns going to people is the design, so that number never wears an up-is-good arrow.

  • Policy is the denominator

    Review requests would only be counted where the practice's policy allowed them.

  • No PII in marketing analytics

    No patient data, health details, phone numbers, insurance IDs, or free text — ever.

FAQ

Frequently Asked Questions

No. The Reputation Agent is planned, and this page shows the intended reporting with illustrative values. The exact fields and availability will be confirmed before launch.