Request Activity

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.

Review Request Results Step by Step

Choose a date range and When requests started to follow a batch of requests from creation to later outcomes.
Set Request type and, if needed, narrow Locations, sources, and senders.
Read Requests You Send and expand What Happened to These Requests? if the sent total is lower than the created total.
Review completed Review Flow outcomes or Custom Form results, then open matching activity records to investigate.
Use When responses were completed for work completed in the period, or View team activity patterns to inspect when requests were created.

Use the same period, count basis, and filters when comparing results with a colleague. Record Results through as well: requests can receive more opens or completions after the original period ends.

Choose How Activity Is Counted

The initial range is Last 30 days. Count activity by determines which records enter the report.

Count activity by	What enters the report	What it answers
When requests started — default	Direct requests created during the selected period, plus QR code and Smart Link entries opened during the period. Later opens, completions, and other outcomes are shown through report generation.	What did the requests and link entries that started during this period achieve?
When responses were completed	Direct and customer-started responses completed during the selected period, even when the request or link entry started earlier.	How many responses finished during this period, and how did those customers start?

When requests started follows the group of requests and link entries that began during the selected period. A recent group has had less time to open or complete than an older one, so compare completion rates carefully. The report shows the exact Results through time used for later outcomes.

When responses were completed is not based on a group of requests that started together. It therefore shows completed-response volume rather than a completion rate.

Understand the Two Activity Paths

Request Activity keeps direct requests and customer-started activity separate because they begin differently:

Requests You Send contains Review Flow and Custom Form requests your team creates for a specific customer. Each request counts once, even if it produces several email, text, reminder, or delivery events. Creating a request does not by itself prove that it was sent.
QR Code & Smart Link Activity begins only when a customer opens a tracked public link and enters a Review Flow or Custom Form. FSRevs cannot count people who saw a QR code or link but did not open it.

A sender filter applies only to direct requests and hides the QR code and Smart Link section. A configured sender on a public link does not mean that person actively sent a request when the customer opened it.

Filter the Report

Use the primary filters for:

Date range and Count activity by
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. Source filters also narrow customer-started activity when its Flow or Form can be resolved. Sender choices come from direct 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 Requests You Send

In When requests started mode, the direct-request funnel shows:

Stage	What it means
Requests Created	A direct Review Flow or Custom Form request was created for a specific customer. It may not have been sent.
Requests Sent	FSRevs confirmed that an initial email or text was sent. This does not prove receipt or delivery.
Request Links Opened	A request in the confirmed-sent group later had its request link opened. This is not email-open tracking.
Responses Completed	A request in the confirmed-sent group later received a completed response.

The Opened and Completed percentages are based on Requests Sent. A separate callout reports completions from requests whose send could not be confirmed, so those outcomes remain visible without changing what the percentages measure.

For example, if 100 requests were created, 80 have a confirmed send, 40 of those were opened, and 20 completed, Opened is 50% and Completed is 25%. Both percentages use 80 as the denominator. Any completion from the other 20 requests is reported separately.

Expand What Happened to These Requests? to reconcile every created request into one sending-status row:

Sent by email or text
We couldn’t confirm the send
Opened on a device to send
No send recorded

Each row shows its request, open, and completion counts. Opened on a device to send means the request was prepared in a person’s email or text app; FSRevs cannot confirm what happened afterward.

Typical Time to Open and Typical Time to Complete use the middle eligible result rather than an average, include a sample count, and show 24-hour maturity context. Invalid intervals are omitted. Older Review Flow completion dates backfilled from request creation remain in completion totals but are excluded from completion timing.

Read timing alongside the sample count. Requests created today may still complete later, so a short response time among the first few completions does not describe every request in the group.

Read QR Code and Smart Link Activity

In When requests started mode, this section shows:

Link Opens
Responses Completed
Completion After Opening
Opens with no recorded response
Typical Time to Complete

The trend groups customer entries by Review Flow and Custom Form. A Flow or Form may be unresolved when someone left before a complete record was available; those entries remain in overall link-open counts but cannot be included by a source filter.

In When responses were completed mode, Completed Responses compares responses from requests your team created with responses that began from QR codes or Smart Links. Applying a sender filter intentionally removes the customer-started comparison.

Previous-period context is limited to comparable request, link-open, or completed-response volume. It does not treat rating groups or recent requests that have had less time to complete as equivalent comparisons.

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 When requests started mode, compare Created, Sent, Opened, Opened %, Completed, Completed %, and Locations. Opened % is the share of that sender’s confirmed-sent requests whose request link was opened. Completed % is based on that same confirmed-sent total. The request total also shows the Review Flow and Custom Form mix.

In When responses were completed mode, compare total completed responses and their Review Flow and Custom Form composition.

Choose View team activity patterns to compare sending timing across the team, or select a sender’s name to open Request Activity Patterns for that person. Use View Outcomes from the pattern view when you want to intentionally apply that sender to the report’s outcome filters.

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.

Review Request Activity Patterns

Request Activity Patterns presents request-creation timing as facts. The team overview compares each recorded sender by:

Requests
Days With Requests
Requests created fewer than 3 minutes after that sender’s previous request
The sender’s busiest rolling 30-minute period on one day

Select a team member to inspect their timeline and individual requests. Timing patterns can identify activity worth reviewing, but they are not a score and do not determine whether a request was appropriate.

The pattern view always uses request creation time and the selected Locations. It includes both Review Flows and Custom Forms. Request type, Flow, Form, completion, outcome, and overview sender filters remain available when you return to Request Activity but do not narrow this view.

For a selected person:

The initial All Activity chart compares total requests with requests created fewer than 3 minutes after the previous attributed request. Both bars use one shared linear scale.
Short ranges let you choose a day directly. Longer ranges let you choose a week or month, then a day.
The All Activity → period → day trail shows your position. Back controls return one level, and browser Back and Forward work because drill state stays in the URL.
Busiest 30 Minutes is the largest same-day group whose first and last actual timestamps fit within a rolling 30-minute window.
A selected day’s time-of-day chart uses 48 fixed clock half hours. Those columns visualize the day; they do not define the rolling peak.

The individual-request list is oldest first and keeps exact gaps such as +30 sec, +2 min, or +3 min. Gaps under 3 minutes are highlighted; gaps of 3 minutes or more use the standard style. The first request without an earlier request in the report shows a dash. Recipient email addresses and phone numbers are not shown.

Sent By is the person whose activity is being reviewed. Created By identifies the operator and shows direct, proxy-created, or unavailable creator context. How It Was Sent can show Email, Text message, Email + text, Opened on a device to send, or No send recorded. A device handoff is not confirmation that the person sent or delivered the message.

Understand Review Flow Outcomes

Review Flow Outcomes starts with the number of completed review requests, then shows what those customers did. Every completed request appears in exactly one category:

Continued to a review site and left written feedback
Continued to a review site without written feedback
Left written feedback without continuing to a review site
Left a rating only
Completed without one of those recorded actions

A completion in the final category can be valid for a simple Review Flow. If it is unexpected, use its link to inspect the matching records and review the flow setup.

Review-site handoffs that were not recorded as completed are shown separately, so they do not inflate or overlap the completed outcomes.

Star Rating and Customer Recommendation Score remain separate. With fewer than five ratings on a scale, the report shows only nonzero counts. At five or more, it adds a proportional distribution and percentages. Legacy or unclassified ratings remain separate rather than being forced into either scale.

Use an outcome, incomplete-handoff, or per-Flow link to open the exact matching records in Flow Activity.

Understand Custom Form Results

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

Requests
Opens
Completions
Completion rate when counting by request start
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 Email and Text Delivery

Email & Text Delivery appears only in When requests started mode and covers tracked initial request messages. Reminders are excluded.

Email and SMS are shown separately. Each channel card leads with its initial attempts and successful provider handoffs.

When a card has tracked attempts with no delivery issue or complaint, it intentionally stays simple and shows No delivery issues recorded. Informational details such as accepted-but-unconfirmed messages or queued processing are not repeated in that healthy state.

Actual delivery problems and complaints continue to show their relevant detail. Cards without a tracked provider attempt can still explain a device handoff or another untracked state.

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

Ready on a device 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

Authorized disabled locations remain selectable and are labeled (disabled).
Locations in the trash 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

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 or clear filters. Direct requests and customer-started QR code or Smart Link activity are shown separately; a sender filter intentionally hides the customer-started path.

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 when the report follows requests that started during the selected period. When responses were completed reports finished responses without using a request-started total.

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.

Sent is lower than Requests Created even though requests were prepared

The Sent stage includes only requests FSRevs can confirm were sent by email or text. Expand What Happened to These Requests? to see unconfirmed, device-prepared, and untracked requests with their outcomes.

An older period’s completion totals increased

When requests started follows the requests created in that period through the report’s Results through time. Later completions can change the result even though the original request count stays the same.

A sender selected on a QR code is not counted as a direct request

Public-link attribution does not prove that person actively created or sent a request. Customer-started activity stays in its own section, and a sender filter hides that section.

Sender Tracking — Understand Sent By, Created By, and employee attribution
Flow & Form Reports — Analyze one Review Flow or Custom Form
Flow Activity — Explore individual Review Flow records
Form Responses — Explore individual Custom Form records
Roles & Permissions — Understand Data access and location scope
Usage & Limits — Review monthly request allowances and notification usage