Form, Knowledge Base, and Experience Builder options reference
Look up the controls for support forms, article publishing and experience design.
Where to find the controls
Settings → System → Ticket Form; Knowledge Base → Articles/Categories/Tags/Menus/Widgets/Themes/Customizer/Home Builder; Experience Builder for launcher, chatbox, effects, and KB presentation.
Before you begin
Ticket fields — Type selects text, textarea, email, number, select, checkbox, file, content, or button behavior; Label is customer-facing; Key is the stable stored identifier; Placeholder shows an example; Help text explains requirements; Required blocks submission when empty; Width controls grid span; Rows changes textarea height; Alignment positions button/content elements; Default value pre-fills supported fields; Min/Max constrain numeric or length values; Options define stored value and displayed label for choice controls; Role visibility limits who sees the field; Sensitive excludes the value from AI and some exports; Conditions show/hide a field based on previous answers. Core Subject and Description fields cannot be removed and retain required rules. KB article — Title and Slug define identity/URL; Status is Draft, Published, or Archived; Visibility Public exposes content while Internal limits it; Publish date schedules visibility; Category and Tags drive navigation/filtering; Featured promotes content; Author records ownership; Excerpt supports cards; SEO title, Meta description, and Canonical tune search metadata; AI access allows retrieval; Citation permission allows the answer to cite it; AI priority influences retrieval weighting; Template seeds structure. Categories use name, slug, parent/level, icon, visibility, SEO title, and meta description. Experience launcher — Position, X/Y offsets, Size, Label, Show label, and Icon control the floating entry point. Chatbox Size and Color mode control the panel. Effects — Open effect, Close effect, Duration, Open trigger, Auto-open delay, and one-time Attention motion control animation. KB presentation — Content width, Article width, Category columns, Hero title, Hero subtitle, and Search placeholder tune layout and copy. Presets/themes replace coordinated values; custom CSS is an advanced final override.
Settings reference
A field option has a machine value and a customer label; changing the value can break existing conditions/report grouping, while changing only the label is safer. Required and hidden conditions must never combine into an impossible form. Sensitive is a data-handling control, not encryption. Internal articles must not be used as public Chat AI evidence. Archived removes an article from normal discovery without deleting it. Canonical should normally be blank unless duplicate URLs exist. Auto-open should use a respectful delay and the attention animation should not loop. Content/article widths are clamped to supported ranges; category columns adapt on smaller screens.
Important considerations
Never ask customers for passwords, full payment-card data, or secrets. Deleting or renaming stable keys can orphan historical meaning and automation conditions. A public article with AI access may be quoted to visitors. Auto-open and heavy animation can violate user expectations or accessibility preferences. Custom CSS can override responsive and focus styles.