Use case
When a customer submits a website form, a ticket is created as expected. However, the form submission on the ticket is only shown as a list of properties—with internal field names and no option to forward.
The nicely formatted, forwardable message of the form submission exists only in the Inbox/Help Desk as a conversation.
Problem
This conversation “email” is not visible on the ticket, even though the conversation is technically associated with the ticket.
On the ticket we only see ticket properties, but not:
- the localized/translated field labels as the customer saw them,
- all submitted fields (both contact and ticket properties),
- a forwardable message we can use to reply or route internally.
Requested solution
Show the original form conversation (“email”) directly on the ticket as a fully forwardable message.
Ideally:
- identical to the Inbox/Help Desk rendering (layout + translations),
- visible as a Conversations thread on the ticket itself,
- clearly marked as the original form submission,
- fully forwardable (to internal stakeholders or external recipients).
Why this matters
- Many teams work primarily in Tickets, not in the Inbox.
- The email-like rendering is ideal for customer communication (clean, readable, forwardable).
- Current workarounds (workflows, custom code, manual copy/paste) add friction and risk inconsistencies.
- A native solution improves efficiency, data quality, and end-to-end support experience.
Benefits
- Professional customer replies directly from the ticket
- No need to juggle Inbox and Ticket views
- One source of truth with all form details in context
- Easy internal/external routing via Forward
Summary
Please make the form conversation visible 1:1 on the ticket as a forwardable mail thread, exactly like it already appears in the Inbox/Help Desk. This would be a major improvement for all teams using support forms and tickets.