Message History
What This Page Covers
Section titled “What This Page Covers”Check the email and SMS messages associated with a Review Flow request: what FSRevs prepared, which recipient it used, tracked delivery updates, and replies linked to that record. The same message view is available for Form Responses.
Accessing Message History
Section titled “Accessing Message History”Open the response record and select Message History, or choose Messages from an Activity card’s more-options menu. You need access to that response. To inspect content, use a message row’s View Message Record action.
What You’ll See
Section titled “What You’ll See”Each message in the history shows:
| Column | Description |
|---|---|
| Message Type | The kind of message — e.g., “Email Review Request”, “Email Review Reminder” |
| Status | Current delivery state (see table below) |
| Method | Whether FSRevs handled sending or prepared a send from your device |
| Delivery | A summary such as Queued, Sent, Not delivered, Received, Canceled, or Not tracked |
| Opened | Whether an email open was tracked; the tooltip shows the recorded count or that tracking is unavailable |
Status gives the detailed message state; Delivery is a simpler summary. For example, a Delivered or Opened message can still show Sent in the Delivery column.
Message Statuses
Section titled “Message Statuses”| Status | Meaning |
|---|---|
| New | Message created but not yet sent |
| Sent | Message handed off to the delivery provider |
| Delivered | The delivery service reported delivery to the destination. This does not prove a particular inbox category or that the person read it. |
| Opened | An email-open event was recorded. It is an activity signal rather than proof that the customer read the message. |
| Bounced | Email delivery failed temporarily or permanently; inspect the related delivery details before retrying. |
| Unsubscribed | The recipient opted out via the unsubscribe link |
| Complaint | The recipient reported the email as spam |
| Undelivered / Failed | SMS delivery did not succeed; inspect the recipient and delivery information. |
| Blocked | A sending restriction prevented use of the SMS destination. |
| Canceled | The prepared send was canceled. |
| Inbound Received | A reply was received and linked to this record. |
| Prepared for direct sending | FSRevs prepared the message for your phone’s SMS or email app. FSRevs cannot confirm whether it was sent or delivered. |
Viewing Message Details
Section titled “Viewing Message Details”Click on any message to open a detail view showing:
- Message Type — The specific message tag (e.g., “Email Review Request”, “Email Review Reminder”)
- Method, Channel, and Recipient — How sending was handled and the exact email address or phone number used
- Subject — The full subject line
- Content — The message body as it was sent (note: links are not clickable in the preview and original formatting may differ slightly)
- Status — The current delivery status
Messages prepared for sending from your own device show Not tracked for delivery. Check your phone’s messaging app or sent-mail folder to confirm the final send, content, and replies. Editing the prepared text on your device does not update the copy stored in FSRevs.
Customer Replies
Section titled “Customer Replies”Replies received through supported FSRevs email or SMS routes appear alongside outbound messages when they can be linked to this request. Messages and replies handled by your own device’s apps remain in those apps.
Troubleshooting a Missing Request
Section titled “Troubleshooting a Missing Request”- Confirm the Recipient, Channel, and Method on the message record.
- If it is queued, check whether sending is still pending before preparing another request.
- If it failed, use Delivery, Bounces & Unsubscribes to investigate the recorded reason.
- If delivery was reported, ask the customer to check filtered folders and search for your business name. Delivery does not prove inbox placement.
- If the message was prepared on a device, check that app’s sent messages instead.
An empty open count can mean the email has not been opened or that tracking was unavailable. Use recorded request visits and completed responses to understand whether the customer continued.