Set up your support workspace
Set your support identity, invite your team and prepare the channels your customers will use.
On this page
Overview
The onboarding wizard is a modal that runs when bootstrap.onboarding.completed is false. Steps: welcome, identity (support name and email), team, tickets (default status and prefix, default ES), email (skippable), KB public slug, AI (skippable), appearance, ready. Optional services can be skipped without blocking tickets.
When to use this
It writes the minimum workspace identity so Inbox, notifications, and the portal have a From name. Skipping email and AI is intentional: HelSup is designed to run without them.
Where to find the controls
It opens automatically after first activation. Restart it from Settings → System → System (Restart onboarding). Routes stay in the SPA; the wizard is a modal over the current hash.
Who can make these changes
The first Support Admin who opens the app. Agents should not be asked to finish onboarding. Additional capability requirements: elegant_support_manage_settings.
Before you begin
Identity maps to company/support fields in Settings → System → General. Ticket prefix and default status map to Tickets settings. KB slug maps to Settings → System → Knowledge Base. Email and AI steps only remind you to configure those catalogs later.
Follow these steps
- Read Welcome.
- Enter Support name and Support email.
- Set a default team name.
- Confirm default status and ticket prefix.
- Skip Email unless a mailbox is ready.
- Set the public KB slug or keep support.
- Skip AI unless you have a BYOK key.
- Keep Elegant Default or change Appearance later.
- Finish.
Settings reference
Support name, Support email, Default team name, Default status, Ticket prefix, Public slug, Skip on optional steps, Continue / Finish.
Example workflow
A shop sets company_name to Nova Support, support_email to help@example.com, prefix ES, skips email and AI, and finishes. Agents can create tickets immediately.
Good practices
You can change every wizard value later in the two-level Settings catalog. Do not hunt for old duplicated Settings tabs; they were removed.
Important considerations
Support email identifies the desk; it does not configure mail delivery. Outbound delivery uses WordPress mail or the configured mailbox transport. IMAP is needed for inbound polling only. Skipping AI leaves normal ticket operations available.
If something does not work
Wizard never appears: onboarding.completed is already true — use Restart onboarding. Save fails: session expired or REST 403; log in again and confirm manage_settings.