Sender Tracking

What This Page Covers

Sender tracking helps you understand who a customer request was sent as and, when applicable, which employee the request and response are associated with.

This applies to both review flow requests and custom form requests.

It also applies when you send from your own device. FSRevs records who prepared the request even though the final SMS or email is sent manually through that person’s phone.

Sent By

Sent By identifies the team member the request is tracked under. For normal sending, this is the person who sends the request.

Users with the Send for others role can use Send as to send on behalf of another available team member. For email, the selected person’s name appears as the sender, while the underlying From address stays the same. The request is also tracked as sent by that person. This is useful when one person is entering the request but another team member should receive the sender attribution.

Created By

Created By records the person who operated the request interface. It remains separate from Sent By so the operator’s actions are not attributed to the person they selected in Send as.

Request Activity’s Sending cadence report uses Sent By as its subject and presents Created By as direct or proxy-created context for each request. When the older operator value is unavailable, cadence says Operator not recorded rather than guessing.

Employee the Customer Worked With

Employee the customer worked with is separate from Sent By. It connects the request and response to the employee who helped the customer.

Use this when the customer interaction should be associated with a specific employee, even if someone else sent the request.

Where You See This Data

You can use sender and employee tracking in:

Request Activity — compare human-requested activity using Sent By attribution across Review Flows and Custom Forms
Sending cadence within Request Activity — review the attributed sender’s complete Review Flow and Custom Form creation sequence, then inspect direct and proxy-created context
Team Performance — compare completed Review Flow results using the saved Employee attribution
Flow Activity — filter and export review flow records by Sent By or Employee
Form Responses — filter and export form submissions by Sent By or Employee
Exports — include sender and employee columns when reporting on request activity

Sending cadence keeps session boundaries, rolling 30-minute peaks, and fixed half-hour chart periods separate. Its single workspace moves from the complete range to a selected week or month when needed, then to a day, its sessions, and records. The drill-down trail and one-level Back action preserve that context.

Exact request gaps and session median gaps use a fixed timing key: under 1 minute is red, 1–under 2 minutes is orange, 2–under 3 minutes is amber, and 3 minutes or more is green. This shading helps locate tightly spaced activity; it does not assign a behavioral score or conclusion. Sessions may cross midnight, so selected-day record counts can be smaller than the visible full-session count.

Requests prepared for sending through a person’s own device remain attributed to their saved Sent By and Created By values. The device handoff does not confirm that the message was ultimately sent or delivered.