Skip to content
FSRevsFSRevs User Guide

Team Performance

What This Helps You Do

Section titled “What This Helps You Do”

Team Performance helps managers understand completed Review Flow results associated with team members. It brings response volume, feedback, review-site visits, rating samples, locations, and Review Flow composition into one place so you can investigate where results differ.

Open Reports > Team Performance. You need Data access for at least one location. The report includes only locations and records you are authorized to see.

Choose a Reporting Period

Section titled “Choose a Reporting Period”

The initial range is Last 30 days. Team Performance has one date meaning:

Responses completed in this period

A response enters the report when its Review Flow was completed during the selected period, even if the request was created earlier. Both requests sent by a person and customer-started Review Flow responses can contribute.

There is no request-created cohort or Custom Form employee reporting in this report.

Filter the Report

Section titled “Filter the Report”

Use the date control to choose a standard or custom period. Expand Locations, Review Flows, and team members to select:

  • One or more authorized locations
  • One or more employee-relevant Review Flows
  • One or more team members with contributing responses

No selection means every matching option in your reportable scope. Select a team member’s name in the comparison table to filter this same page to that person; Team Performance does not open a separate employee-report route.

Understand Attribution Coverage

Section titled “Understand Attribution Coverage”

The report keeps overall response context visible even when some records do not have an employee:

Measurement What it means
All Completed Responses Every matching completed Review Flow response, with or without a linked team member
Employee-linked Responses Matching completed responses with a saved team member
Selected Team Responses Employee-linked responses for the selected team member filter
Employee Attribution The share of all matching completed responses with a saved team member
Team Members Represented Distinct linked team members in the selected results
Team member not recorded Matching completed responses that do not currently have employee attribution

Filtering to a team member changes the linked results, ratings, trend, and breakdowns. It does not hide the overall completed-response population used to explain attribution coverage.

Read the Summary and Trend

Section titled “Read the Summary and Trend”

The summary includes completed-response context, attribution coverage, team members represented, written feedback, and review-site visits.

The trend compares All Completed responses with either Employee-linked responses or the Selected Team Member population. Previous-period comparisons are limited to completed-response volume. The report intentionally omits rating-change comparisons.

Compare Team Members

Section titled “Compare Team Members”

The Team Member Comparison table shows:

  • Completed Responses
  • Written Feedback
  • Review-site Visits
  • Rating Results, with Star Rating and Recommendation Score shown as separately labeled results in one column
  • The number of ratings or responses each average is based on
  • Locations represented
  • Review Flows represented

The default order is completed-response volume. You can sort the comparable activity and coverage columns yourself. The combined Rating Results column is not sortable because Star Rating and Recommendation Score use different scales. A team member associated with several locations is consolidated into one row, while the location and Review Flow counts preserve composition context.

On smaller screens, each team member appears as a comparison card rather than a horizontally scrolling table. The same measures and team-member drill-down remain available.

Select a team member to update all summaries, trends, ratings, and breakdowns for that person.

Read Rating Results

Section titled “Read Rating Results”

Team Performance uses completed, employee-linked Review Flow responses with a valid stored rating.

  • Star Rating uses the 1–5 scale and shows its average, 4–5-star share, distribution, and sample count.
  • Customer Recommendation Score uses the 0–10 scale and shows its average, Advocate share, distribution, and sample count.
  • Review Flows without ratings do not enter either rating denominator.
  • Legacy or unclassified ratings are counted separately.

Only rating scales represented in the selected responses appear. If neither scale has results, the report shows a simple No ratings in this selection message while keeping the other activity and feedback metrics available.

Star Rating and Customer Recommendation Score are never averaged together. The interface uses plain-language labels such as Based on 12 star ratings rather than statistical notation. Keep that response count visible when comparing results: a high average from a few responses does not carry the same context as a similar average from hundreds.

Use Review Flow and Location Breakdowns

Section titled “Use Review Flow and Location Breakdowns”

The By Review Flow and By Location sections show:

  • Completed responses
  • Linked or selected responses
  • Attribution coverage when no team member filter is active
  • Team members represented
  • Written feedback and review-site visits
  • Scale-specific rating results with sample counts

Use these sections before interpreting differences between people. Flow purpose, rating scale, location, and customer population can materially change what a comparison means.

Select a breakdown to open the exact matching records in Flow Activity.

Understand Employee Attribution

Section titled “Understand Employee Attribution”

Employee is the team member currently associated with the customer experience. This is separate from Sent By, which identifies the person the request was attributed to.

Managers can correct the employee saved on a record. Team Performance therefore reflects each record’s current saved team member, not an immutable snapshot of the employee at completion. A legitimate correction can change historical report totals.

Missing attribution remains visible as Team member not recorded coverage. FSRevs does not substitute the sender or interface operator.

Interpret Review-site Visits Carefully

Section titled “Interpret Review-site Visits Carefully”

In Team Performance, review-site visits are counted among completed responses linked to the selected team population.

Google listing rating and review-count changes remain listing-level information in Google Performance. They are not attributed to individual team members.

Locations and Historical Records

Section titled “Locations and Historical Records”
  • Authorized disabled locations remain selectable and are labeled (disabled).
  • Soft-deleted locations and records without a reportable location are excluded.
  • Deleted team members and Review Flows can remain visible when active contributing records reference them. These names are labeled (deleted).
  • Current access determines which history you can see; FSRevs does not reconstruct historical location roles or team rosters.

Troubleshooting

Section titled “Troubleshooting”

The Team Performance report is missing
Ask an administrator to confirm that you have Data access for at least one location.

A Review Flow is missing from the filter
The report includes Review Flows with employee tracking currently enabled or active historical records that contain employee attribution.

A response is in All Completed but not Employee-linked
The completed response does not currently have a saved team member. It contributes to Team member not recorded and the attribution-coverage denominator.

A rating average is missing
The selected employee-linked responses may not contain a valid rating on that scale. Flows without ratings do not create zero values.

Historical totals changed
A manager may have corrected the team member saved on an earlier record. The report uses current saved attribution.

Section titled “Related Pages”