A feature request is rarely submitted in isolation. Often the user who wants a feature has already chatted with your team about the frustration that prompted it. Yaplet keeps this context intact — a feature request ticket is linked to the submitting visitor, and from the visitor's profile you can click through to their full conversation history.
How the link is created
When a visitor submits a feature request form via the widget (logged in or identified with Yaplet.identify()), Yaplet records the visitor on the ticket. If that same visitor has an open or historical chat conversation, the link is visible on the ticket's visitor card.
The link is created automatically — there's no action required from your team.
View the linked conversation from a ticket
- Open the feature request ticket from your board.
- At the top of the ticket's sidebar you'll see a card with the submitter's name and email, followed by a Profile section showing their ID, plan, country, external ID, and last visit.
- If the visitor has a chat conversation, expand the Actions section of the sidebar — you'll find a View chat link that opens the conversation in the Inbox in a new tab.
From there you can click through to one of their chats and see their full chat history in the Inbox — getting the unfiltered context for why this feature matters to this specific user, without asking them to repeat themselves.
Useful for product decisions
When you're evaluating a high-vote feature request, click through to the linked conversations of the top voters. You'll often find nuance that a title and description alone don't capture: edge cases, the workflow it's blocking, the manual workaround they're currently using. This qualitative context strengthens or reshapes the product decision.
Creating a link manually
If you're in the Inbox replying to a conversation and the visitor mentions they've requested a feature, you can find their feature request on the board by searching for their email in the board's filter. The relationship runs in both directions — from ticket to conversation, and from conversation to the visitor's submitted tickets.
Related reading
For an overview of how boards and tickets work, see Boards — the kanban primitive behind tickets, bugs, and feature requests.