Add a clear support-ticket action
Give readers a clear way to request support when an article does not resolve their question.
On this page
Overview
The header and still-need-help blocks open the existing portal new-ticket flow driven by Form Builder.
When to use this
Experience Builder must not hardcode ticket fields.
Where to find the controls
Header primary button and article/home CTA.
Who can make these changes
Anonymous users may be asked to sign in first, matching portal rules.
Before you begin
Form fields live on Ticket Form Builder (portal / chat_widget surfaces).
Follow these steps
Click Add New Ticket. Complete the Form Builder form. Submit creates a real ticket.
Settings reference
No extra CTA field list is stored in es_experience.
Example workflow
A custom “Order number” field on the portal form appears after the CTA, not in Experience Builder.
Good practices
Chat widget Add New Ticket tab is the same Form Builder surface (chat_widget).
Important considerations
Configure submission fields in the global Ticket Form Builder and verify the portal surface before publishing the CTA.
If something does not work
CTA missing: the section may be disabled on KB Appearance.