Skip to content
← Back to blogOperations

New in Latch: feedback history and follow-up tickets

Follow a response from the satisfaction report to a contact, request day, original ticket, and linked follow-up ticket.

See how it worksUnified Triage →
New in Latch: feedback history and follow-up tickets

A lower happy-response rate does not tell a service lead who needs a reply or which ticket needs another look. Feedback becomes operational when the report can connect an aggregate to a contact, a request date, and the work that prompted the response.

Diagram connects customer satisfaction totals to a contact history, request-day view, and a follow-up ticket tied to the original record.

Latch’s Customer Satisfaction report separates sent requests from responses and ratings. From an overview, an operator can open a recipient’s history or select a request day. If a customer submits an unhappy rating and adds details, the feedback page can create a separate triage ticket linked to the original ticket context.

Keep requests and responses in separate counts

The overview starts with sent requests, response counts, and happy or unhappy ratings. A send record does not prove the email was opened. “No response” means a request was sent and that recipient has not rated it; pending, queued, and skipped requests remain separate. The report uses the request’s creation date for its selected window, so a rating received later can still appear on the original request day.

Each recipient’s latest rating is used for the report. The same ticket can have more than one recipient, and a ticket’s customer record is not substituted for the feedback recipient. These rules matter when the service lead decides whether a trend reflects a particular contact or the whole customer base.

Follow a person or a day back to the ticket

The contact history shows tickets addressed to a recipient during the selected window, including sent, responded, and unanswered counts. Contact identity uses the trimmed, case-insensitive recipient email; a ticket is not included merely because it belongs to the same organization. Aggregates cover the full window, while the visible ticket list is paginated.

Contact history for one fictional recipient with sent, responded, unanswered, rating, and ticket details.

Historical capture from 17 September 2026 with fictional sample records. Contact totals keep sent and responded denominators visible.

Selecting a chart day opens the requests created on that UTC calendar day. The page can show each recipient’s latest rating even when the reply arrived later. From a day view, an operator can open a contact and return without losing the selected day.

Daily feedback history for a fictional request date, showing recipients and their latest feedback.

Historical capture from 17 September 2026 with fictional sample records. The day is based on request creation; later responses can appear in the history.

An unhappy response can lead to a “Tell us more” form. The response token and rating are checked against the original feedback record. The original ticket number and contact email are carried into the form when available; the customer’s details then create a new triage ticket that retains the original ticket, site, project, customer, and priority context. The new ticket gives the team a place to own follow-up without rewriting the closure record.

Treat public form defaults as input hints

A separate public intake form can also open with a name, email, or configured field value prefilled. The server filters those values to the fields and types defined for the form, and treats them as display defaults rather than trusted submission metadata. This is a separate form-opening path; it does not decide a feedback rating or create the linked follow-up by itself.

Use the reporting workspace guide to understand the broader date and denominator choices. Once the follow-up enters triage, quick status and priority edits keep routine handling on the board. For the larger path from intake through ownership and resolution, see the operations workflow.

When a customer says the work is not resolved, keep the response attributable, preserve the original record, and create a separate ticket with the context needed to act.

Continue exploring
Next product pathUnified TriageSee how Latch handles email, tickets, and queue routing in one operational workflow.Related pathOperations TeamsMap these patterns into an operator workflow with queue ownership and visible downstream actions.Related pathProduct OverviewSee how unified triage, approvals, audit trails, and plugins connect.
Related reads
Introducing reporting workspaces and Service deliveryUse seven Latch report destinations to inspect the tickets, date basis, and denominator behind an operational signal.Report on the Fields Your Team Actually UsesGroup reports by tag folders and Issue Data Fields, then show the ticket-log columns that explain each result.Introducing staff workload profiles and SLA historySeparate current open tickets from period activity, then inspect the records and SLA outcomes behind a staff profile.
Ready to move beyond reading?

Try Latch with your team's own requests.

Create a workspace and start with one ticket. Or follow the product walkthrough to see the request, review, and recorded result before you try it.

Try LatchSee how it works