Multiple pages
Run more than one branded support form from a single SupportPage account.
A single SupportPage account can run multiple support pages — each with its own URL, branding, form fields, inbox, and settings. Use this when you support more than one product, brand, or audience segment.
Availability depends on your subscription plan. If Add page is disabled, upgrade from Invoices and subscription.
When to use multiple pages
| Scenario | Example setup |
|---|---|
| Separate products | billing.acme.com and api.acme.com support forms |
| White-label clients | One page per client agency brand |
| Language or region | Different fields per locale (manual duplication today) |
| Staging vs production | Draft page for testing before swapping links |
Each page is isolated — requests do not mix in the inbox unless you switch pages in the UI.
Creating a new page
- Open Support pages in the dashboard (or Add page).
- Complete naming and slug — same constraints as onboarding step 1.
- Configure branding, fields, and spam protection.
- Publish when ready.
The onboarding wizard may run again in abbreviated form for additional pages.
Switching between pages
Use the page switcher at the top of the dashboard:
- Inbox shows requests for the selected page only
- Settings apply to the selected page
- Notifications may be per-page — verify each configuration
It is easy to reply from the wrong inbox when switching quickly. Confirm the page name in the header before sending customer replies.
URLs and domains
Each page has:
- Its own slug →
https://{slug}.support-page.dev - Optional custom domain — one hostname per page in typical setups
You cannot attach the same custom domain to two pages simultaneously.
Billing and limits
Plans cap how many published pages you can run. Draft pages may or may not count toward the limit — check your plan details in the app.
Adding pages does not merge billing; one subscription covers the account subject to plan limits.
Team workflow tips
| Practice | Benefit |
|---|---|
| Naming convention for slugs | acme-app, acme-billing — instant recognition |
| Per-page notification addresses | Route API issues to engineering alias |
| Document which app links to which URL | Prevents customers on wrong form |
Archiving a page
When a product sunsets:
- Unpublish to stop new intake.
- Resolve or export open requests.
- Archive or delete the page per General settings.
Keep DNS records for retired custom domains pointed away to avoid confusion.