Ticket View
Comprehensive ticket management interface displaying submitted form data, visitor information, and workflow controls for processing customer tickets.
Overview
Click a card on the board and the ticket opens in a panel that slides in over it. The header shows Back to board (the arrow at its top left) and the board's name followed by the ticket's number, for example Bugs / #24.
The panel has two parts: the report itself on the left — title, description, attachments, the submitted answers and the team's comments — and the ticket's properties on the right: status, priority, assignee, labels and board, then the reporter, then a few more actions. On a narrow screen the two parts stack, with the properties first, so the status and the owner are never scrolled out of sight.
Title & Summary
Every ticket has a title and a short summary shown on its card and — for feature requests — on your public roadmap. At the top of the report, a line shows the ticket's number, the form it came through, and Created {date}.
For tickets submitted through the widget, the title and summary are generated automatically by AI from the visitor's answers. Generation is privacy-safe: it never includes personal or contact details (names, emails, phone numbers, and the like), so the result is safe to display publicly even when the form itself collected private information.
You can refine both at any time:
- Edit in place — click into the title or the description at the top of the panel and type. A change is saved when you click away from the field (in the title, Enter does the same)
- Rewrite — click the Rewrite button (the Yaplet button, tooltip Generate with AI) to (re)generate a clean title and summary from the ticket's answers. The new text is saved at once. If it replaced an existing title or summary, a notice ("Title and description replaced") offers Undo for 10 seconds, which puts the old text back and saves it again
Attachments and answers
- Screenshot: Shown right under the description. Click it to open it full size in a new tab
- View replay: If session replays are switched on for the brand's chat widget (Brand → (your brand) → Chat widget → Install tab, SDK Features → Session Replays, which needs the Session Replays permission), a View replay button appears when the ticket has one. It opens a fullscreen Session Replay window with a complete replay of the visitor's session — every click, scroll and page navigation leading up to the ticket. This gives you immediate visual context for the reported issue without leaving the ticket. Learn more in the Session Replays documentation
- View recording: Opens the visitor's screen recording in a new tab, if they recorded one
- Submitted answers: Everything the reporter filled in on the form, one field after another, read-only
The replay player
The player has Play / Pause, Back 10 seconds and Forward 10 seconds, a Skip inactivity switch (it jumps over the stretches where nothing happened), a Playback speed menu (from 0.5x up to 8x; your choice is remembered), Full screen (and Exit full screen), and Open this page in a new tab, which opens the page the visitor was on at that moment. While it loads you see "Loading recording…". If it cannot be shown, the player says "This recording couldn't be loaded" with a Try again button, or "The recording contains no events."
Properties
On the right, under Properties:
- Status: The column the ticket sits in; pick another to move it. Each column shows its color dot. A ticket you archive has no status
- Priority: Set urgency with color-coded levels (Low, Medium, High)
- Assignee: Assign the ticket to a team member, or choose Unassigned
- Labels: Pick any of the board's labels to tag the ticket — they show as colored chips on the board card, and you can filter the board by them (see Board View). This row appears once the board has labels
- Board: Move the ticket to another board; it lands in that board's first column. The picker offers the boards you have been granted; an organization owner sees every board, even without explicit grants
Reported by
Under Reported by you see the reporter's name and email, their country flag, and a red Banned badge when the visitor has been banned, so you can spot blocked users at a glance. Below that: Plan, Country, Last visit, External ID and Id (the last two can be copied), where known.
Two buttons can follow:
- View chat — opens the reporter's conversation in the inbox in a new tab, when they have one
- Send decision — email the reporter your decision (see below)
Comments
The Activity section holds your team's discussion of the ticket, oldest first, with the count next to the heading.
- Team discussion: Comments are visible only to team members. Write in the box under the thread ("Leave a comment for your team…", up to 2,000 characters) and press Comment — or Ctrl + Enter (Cmd + Enter on a Mac), as the hint under the box says
- Live for the team: A colleague with the same ticket open sees a comment appear without refreshing
- With no comments yet it says "No comments yet"
Decision emails
Send decision opens Send decision to the visitor:
- Visitor email: The email goes only to the reporter's own address, which the dialog shows as fixed text — there is no field to type another recipient. A ticket with no reporter address has no Send decision button
- Sender name (optional) and Source email: Pick a verified organization address to send from, or the shared Yaplet address
- Decision content: Your message
- Previous decision: Once a decision has been sent, the dialog shows it — who it was from, who it went to, and the text — and the send button reads Resend
- Hourly limit: Ticket emails have an hourly limit per organization. Emails sent from the dashboard and those sent by an AI assistant connected through the MCP Server count together
- Cost: A ticket email is free with a paid plan or during your free 14 days; otherwise it costs 1 credit from the credit you have bought. With no credit it is not sent, and you are told so
More
The More section holds the technical side of the ticket:
- Event log: A timeline of the user's interactions — clicks, network requests and events — opened in a side panel
- Metadata: Technical data and system-generated information about the ticket, opened in a side panel
- Copy for AI: Puts the ticket on your clipboard as readable text, ready to paste into ChatGPT or another assistant. It never includes customer details or technical logs
- Export ticket…: Download the ticket as Markdown, a CSV row, or a Yaplet backup. Trello JSON isn't offered here, because a Trello file is a whole board rather than a single card
At the bottom of the properties are two buttons:
- Archive: Remove from active workflow while preserving data. It asks you to confirm
- Delete: Permanently remove the ticket (requires confirmation). The ticket disappears immediately for everyone including the mobile app, and the deletion is written to your audit log