Skip to content
FSRevsFSRevs User Guide

Request Activity

What This Helps You Do

Section titled “What This Helps You Do”

Request Activity shows who is creating customer requests, how consistently they are doing it, and what those requests achieve. It combines the shared activity of Review Flows and Custom Forms while keeping their different results separate.

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

Choose the Date Meaning

Section titled “Choose the Date Meaning”

The initial range is Last 30 days. The Date meaning determines which records enter the report.

Date meaning What enters the report What it answers
Requests Created — default Requests created during the selected period. Opens, completions, and other outcomes are shown through today. Who created requests during this period, and what have those requests achieved so far?
Responses Completed Responses completed during the selected period, even when the original request was created earlier. Who is represented in the customer responses that were completed during this period?

Requests Created is a cohort view. A recent cohort has had less time to open or complete than an older cohort, so compare completion rates carefully. The report labels these outcomes Results through today.

Responses Completed has no request-created denominator. It therefore shows completed-response volume rather than a completion rate.

Understand Which Requests Count

Section titled “Understand Which Requests Count”

Request Activity includes system-origin requests created by a person through FSRevs. Each Review Flow request or Custom Form request counts once, regardless of how many email, SMS, reminder, or delivery events it produces.

Customer-started Smart Link activity is excluded from this sender report. A Smart Link may carry configured sender information, but that does not mean the person actively sent a request when the customer opened it.

Customer-started activity can still appear in other reporting when its attribution and outcome are relevant.

Filter the Report

Section titled “Filter the Report”

Use the primary filters for:

  • Date range and Date meaning
  • Request type — Review Flows and Custom Forms, Review Flows only, or Custom Forms only

Expand Locations, sources, and senders to filter by:

  • One or more authorized locations
  • One or more Review Flows or Custom Forms
  • One or more senders, including Sender not recorded

No location selection means every reportable location you can access. Sender choices come from requests that contribute to the available report scope, so deleted historical senders can remain selectable. The report does not add current team members who had no activity during the period.

Read the Summary and Trend

Section titled “Read the Summary and Trend”

In Requests Created mode, the headline shows:

  • Requests Created
  • Senders with Activity
  • Opened So Far and Open Rate
  • Completed So Far and Completion Rate

Supporting metrics show sender attribution coverage, average time to first open, and average time to completion. Timing metrics include a sample count and omit invalid intervals. Older Review Flow completion dates that were backfilled from request creation remain in completion totals but are excluded from completion timing.

In Responses Completed mode, the headline shows:

  • Responses Completed
  • Review Flow Responses
  • Custom Form Responses
  • Senders Represented

The trend separates Review Flow activity from Custom Form activity. Previous-period context is limited to request or response volume so that immature cohorts and unlike rating populations are not presented as fair comparisons.

Compare Senders

Section titled “Compare Senders”

The sender table uses Sent By attribution:

  • Sent By is the person the request is attributed to.
  • Created By is the person who operated the interface and remains separate audit information.
  • Created By is never substituted when Sent By is missing.
  • Missing attribution appears as Sender not recorded.

In Requests Created mode, compare Requests Created, Active Days, Opened, Completed, Completion Rate, and Locations. The request total also shows the Review Flow and Custom Form mix.

In Responses Completed mode, compare total completed responses and their Review Flow and Custom Form composition.

Select a sender’s name to filter the same page to that person. The filtered view adds detailed Flow, Form, location, rating, feedback, and review-site-visit context without turning those unlike outcomes into one sender score.

On smaller screens, sender comparisons use cards instead of a horizontally scrolling table. Each card keeps the request total, source mix, activity, completion, and location context visible.

Understand Review Flow Results

Section titled “Understand Review Flow Results”

Review Flow results keep each outcome tied to the population that can support it:

  • Completed responses require a recorded completion date.
  • Review-site visits count requests where the customer opened a review destination.
  • Written feedback and ratings come from completed responses with finalized values.
  • Star Rating and Customer Recommendation Score remain separate and include sample counts and distributions.
  • Legacy or unclassified ratings are identified separately rather than forced into either scale.

Only rating scales represented in the selected responses appear. If neither scale has results, the report leaves the other Review Flow outcomes visible and shows a brief no-ratings message.

In Requests Created mode, a review-site visit counts for a request in the cohort even when the customer did not return to complete the FSRevs flow.

Use the per-Flow links to open the matching records in Flow Activity.

Understand Custom Form Results

Section titled “Understand Custom Form Results”

Custom Form results show only measurements with consistent meaning across Forms:

  • Requests
  • Opens
  • Completions
  • Completion rate in Requests Created mode
  • Per-Form breakdowns

Answers from different Custom Forms are not normalized or combined into a general outcome. Open an individual Form report for its question and answer summaries, or use Form Responses for matching records.

Read Delivery Health

Section titled “Read Delivery Health”

Delivery Health appears only in Requests Created mode and covers tracked initial request messages. Reminders are excluded.

Email and SMS are shown separately, including:

  • Infrastructure attempts
  • Confirmed delivered
  • Issues and complaints
  • Queued or canceled states
  • Requests without a tracked initial message

These are message attempts, not request counts. One request can have different delivery activity by channel.

Prepared on device — delivery not tracked means FSRevs prepared the message for a person’s phone or email app. It does not prove that the message was sent or delivered.

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.
  • A sender, Review Flow, or Custom Form that was later deleted can remain in historical results when an active contributing record still references it. These names are labeled (deleted).
  • A person associated with several locations appears once, with their contributing locations shown in the count and breakdowns.

FSRevs uses current access to decide which history you can see. It does not reconstruct historical roles, work schedules, expectations, or quotas.

Troubleshooting

Section titled “Troubleshooting”

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

No matching request activity appears
Try a wider date range, clear filters, or confirm that the activity came from a request created by a person. Customer-started Smart Link records are intentionally excluded.

A sender is missing from the filter
The sender list is based on contributing system-origin records. Current users with no matching activity are not added as zero-activity rows.

A completion rate is missing
Completion rate is available for a request-created cohort. Responses Completed mode has no request-created denominator.

Delivery attempts do not match Requests Created
Delivery counts describe tracked messages and channels, not distinct requests. Device-prepared requests may also have no tracked delivery result.

Section titled “Related Pages”