When several customers report the same software bug, keeping track of who needs a follow-up once engineering ships the fix is easy to forget. Frosvo connects reported conversations to tracked bugs so an owner can verify the release, review the customer message and queue updates for selected affected customers.
Linking conversations to a tracked bug
While viewing a customer conversation in the Desk, open the Bug-to-fix loop section in the right-hand context panel:
- Click Link bug to attach the conversation to an existing bug in your workspace (such as
BUG-104), or log a new bug key and title on the spot. - You can link as many customer conversations as needed to the same
TrackedBugrecord, just like linking chats to live incidents. - Each link shows the current tracked status and whether a notification reply has been recorded.
Managing tracked bugs across the workspace
Open Product updates → Bug-to-fix loop in the Desk to see every tracked bug across your workspace. For each bug, you can see how many customer conversations are linked and how many have been notified.
As your engineering team progresses, update the bug status:
- REPORTED: the issue was reported.
- INVESTIGATING: the team is investigating.
- REPRODUCED: the team reproduced the reported behavior.
- FIX_PLANNED: a fix is planned.
- DEPLOYED: the team records the fix as deployed and is verifying it.
- VERIFICATION_PENDING: deployment behavior still needs verification.
- CONFIRMED: the owner recorded production deployment evidence and verified the exact customer conversations for that rollout.
- REOPENED: the issue still occurs and requires investigation. Confirmation is cleared.
An engineering tracker closing an issue is not production verification. The manual workflow retains owner attestations and observation times; it does not independently inspect your deployment provider. The GitHub engineering tracker receives signed issue observations; its source state still does not confirm a deployment. Real provider acceptance remains required.
Notifying every affected customer once confirmed
Open Release context from the bug board. In Release evidence and rollout:
- Choose Deployment. Enter the release version, environment, actual observation time with timezone, and a private evidence note. Optionally attach a public HTTPS deployment link without credentials. Record it. This leaves the fix deployed and unconfirmed.
- Choose Verify customer rollout and select the matching production deployment record. Enter a new private verification note and an optional, separate customer-facing release note.
- Select only the conversations whose customers have received and tested this release. Load more conversations if needed; each verification supports up to 200. Check the verification statement and record it. The environment must be exactly
production. - Close the evidence dialog and open the notification preview. Recording evidence does not itself send a message.
Private evidence notes stay in owner history; customer messages use the separate customer-facing note. Evidence is append-only through the application. Reloading clears recipient selection. Older records load in pages. Deployment observation must precede verification.
For a partial rollout, cases outside the current verified selection are ineligible. Verify the same deployment again when more customers receive it, selecting the intended current group. Pending work from older verification becomes stale; already recorded replies for that deployment are not resent. Newly linked or moved cases need explicit verification.
Choose Rollback to record a withdrawn release. This reopens the bug, clears confirmation and invalidates pending updates. Recorded replies remain in history. A rolled-back deployment cannot be verified again; record the new deployment first. Editing release metadata requires re-verification.
Once confirmed, choose Preview updates & progress. Read the exact customer message, select the linked conversations that are eligible for this rollout, and choose Queue selected updates. Recipients appear in pages of 50; use Load more recipients when needed. Each batch accepts up to 200 selected conversations. Repeat with another selection for larger groups.
Only an unimpersonated workspace owner can preview customer details, queue a batch or cancel its remaining work. Restricted agents see only linked cases from their permitted sites. Queued work continues in the background after you close the window. Return to the preview and choose Refresh progress to inspect recent batches.
Frosvo rechecks the confirmed release generation, selected conversation and current owner permissions before writing each reply. A changed release, moved recipient, reopened issue, revoked owner access or cancelled batch cannot publish a stale queued reply. A failed preparation is retried with a bounded delay; blocked or exhausted work appears as Needs review. Inspect the conversation and channel setup before explicitly selecting that recipient again.
The batch item, notification marker and conversation reply commit together. If a failure occurs before commit, the item remains retryable. If the reply committed but the live update failed, recovery preserves its recorded receipt. An expired worker lease can be recovered by another worker without replaying a committed reply. Owner retries create new batch history rather than rewriting an earlier failed batch.
Reply recorded means that a message was saved in the conversation. Queued and Processing do not mean delivered. Cancel remaining updates stops work that has not committed; it cannot recall a message already recorded or handed to a channel. Historical notification timestamps from before the durable queue are not silently replayed.
For WhatsApp, these bug updates are ordinary text replies. If the reply window is already closed, the batch item needs review and no reply is recorded. If the window closes after recording but before channel dispatch, the channel delivery is blocked. Frosvo does not silently substitute an approved template. Open the conversation to inspect its delivery status and use an appropriate approved template separately when required. An uncertain provider response stays uncertain and is not automatically resent; check the provider before retrying.
Receipts are specific to the recorded deployment identity. Re-verifying the same deployment does not resend recorded replies. A separately recorded new deployment can be verified as a new release. Changing wording never automatically resends a message.
For website chat, a recorded reply is available in the conversation. For other channels, policy checks and their delivery queues determine whether it can be sent. A notification marker does not prove inbox or device delivery. This follow-up uses the normal reply pipeline, which may reopen a closed conversation; it does not automatically resolve every affected customer's case.
If another owner edit wins while you save, reload the current bug before retrying. Never change the status to confirmed solely to bypass a pending production check.
Operator rollout and troubleshooting
Apply both prisma/bug-notification-jobs.sql and prisma/bug-release-evidence.sql before upgrading all writers and starting the worker. Also apply prisma/bug-tracker.sql and prisma/workspace-export-counts.sql, and build from the updated Prisma schema. The raw tables themselves add no generated client models. Drain older writers so they cannot bypass evidence or recipient checks. Existing confirmed rows without evidence are ineligible until an owner records and verifies their actual deployment; never fabricate migration evidence. BUG_NOTIFICATION_WORKER_ENABLED=false disables the dedicated worker.
If a batch remains queued, check the bug-notifications worker's health. A release change requires a fresh preview. An unavailable owner, a channel-policy refusal or exhausted preparation attempts requires review. The queue never relaxes the normal channel's reply policy. Conversation and workspace deletion remove their associated queue items through foreign keys. Workspace deletion removes evidence and rollout snapshots; case deletion removes its rollout targets. Workspace exports include evidence and selected-case snapshots without internal request digests.