Activity Logs
What This Page Covers
Section titled “What This Page Covers”Use a Review Flow record’s activity log to trace events FSRevs recorded, such as a request-link visit, a rating update, a delivery failure, or a review-site click.
Accessing Activity Logs
Section titled “Accessing Activity Logs”- Open the Review Flow’s Activity and find the customer record.
- Open the card’s more-options menu and select System logs, or use View Logs in the record workspace.
- Compare the Created time and Log Entry descriptions. Device and masked network details may be available as tooltips when recorded.
You need access to the underlying response. Form Responses also provide logs from their response workspace.
What Gets Logged
Section titled “What Gets Logged”The activity log includes customer interactions and system events associated with the record. It is not a screen recording, and it cannot show activity that happened after the customer left FSRevs for another site.
Common log events include:
| Event | Description |
|---|---|
| Record created | A request record was prepared or a public visit reached a record-creating interaction |
| Email/SMS sent | A message was dispatched to the customer |
| Request link visited | The request page was opened |
| Rating submitted | The customer submitted their sentiment rating |
| Feedback submitted | The customer submitted written feedback or a message |
| Review site clicked | The customer clicked through to a review platform |
| Followup redirected | The customer was sent to a followup destination |
| Delivery update | A delivery, bounce, unsubscribe, or failure was recorded |
| Notification sent | A configured team notification was sent through the named channel |
| Device send prepared | A message was prepared for sending through a team member’s own app; final delivery is not tracked |
Using Logs for Troubleshooting
Section titled “Using Logs for Troubleshooting”| Situation | What to check |
|---|---|
| The customer did not receive a request | Open Message History for the recipient, channel, and delivery status, then compare delivery events here. |
| The customer says they submitted feedback | Look for a feedback update, check the full response, and search for another request under the same Customer. A review-site click is a different action. |
| A review-site click exists but no public review is visible | The log confirms the handoff only. Review publication happens on the external platform. |
| A team member expected an alert | Look for a notification event, then check their notification preferences and eligibility. Review-click alerts have a delay. |
| Times differ from another report | These logs use the associated location’s timezone when present, with UTC as the fallback. Compare timezone context before treating timestamps as inconsistent. |
Use Audit Trail when you need changes made to a record or its configuration. Use the Customer Journey for the observed path across several connected resources.