SupportSites
Choose and build the correct customer-facing asset for one acquisition, conversion, or communication goal.
How this fits into Lead360Explore the white label platformBuild, brand, deliver, and resell connected client experiences.- 01
How Lead360 helps
- 02
Choose the right asset
- 03
Plan before building
- 04
Use Ask360 here
How Lead360 helps
Lead360 Sites provides a managed place to build and publish web pages that connect with forms, surveys, chat widgets, campaigns, catalogue content, and supported tracking. Draft and published states let teams review changes before a public route is updated.
When to use this area
Use Sites for a public web experience that should live inside the Lead360 customer journey and use the platform data and conversion tools.
Before you begin
- Define the page goal, audience, route, content owner, and conversion action.
- Prepare approved copy and optimized media.
- Identify forms, links, consent, tracking, and structured data requirements.
Choose the right asset
- Funnels organize an ordered page journey and own page-level flow and tracking.
- Forms collect structured contact data and can redirect after submission.
- Surveys collect multi-step intake, qualification, assessment, or feedback.
- Chat Widgets start a structured contact or AI-assisted website conversation.
- Email Templates store reusable HTML and plain-text content for staff and automations.
Plan before building
- Define the audience, traffic source, conversion goal, owner, required data, consent, destination, and success test.
- Open the exact Sites tab before using its Help icon so Ask360 receives the correct controls, operations, and safety boundary.
Use Ask360 here
Ask360 can explain the selected asset, request its missing details, and prepare only a server-supported reviewed change. It must remain scoped to the current Sites tab, wait for Accept before a live write, and never substitute an unrelated reporting table for the requested build or explanation.
Confirm the result
A completed Sites workflow should be visible in the product area that owns the final record. Use these checks before relying on the result or moving to the next customer-facing step.
- Preview desktop and mobile layouts.
- Test every link, form, widget, and customer action.
- Publish explicitly and confirm the public route, metadata, canonical URL, and tracking.
Troubleshooting
A published page still looks old
Confirm the correct site and page were published, then check route selection, asset caching, and the public URL.
A form or widget does not work
Test its own published configuration, integration, permissions, consent fields, and browser console before editing the page layout.
Frequently asked questions
What should I confirm before using Sites?
Define the page goal, audience, route, content owner, and conversion action. Prepare approved copy and optimized media. Identify forms, links, consent, tracking, and structured data requirements. Start with a small, reviewable change whenever the workflow can affect customers, money, published content, or shared records.
How does Lead360 help with Sites?
Lead360 Sites provides a managed place to build and publish web pages that connect with forms, surveys, chat widgets, campaigns, catalogue content, and supported tracking. Draft and published states let teams review changes before a public route is updated.
Continue with Lead360
Use this workflow in Lead360
Put this guide into practice with a 14-day free trial of Lead360 Pro early access, or continue learning through the related collection.