Best practices for going live

Launching Userorbit to your users is an exciting step. Before you flip the switch, run through this pre-launch checklist to make sure everything is configured correctly and your team is ready. A smooth launch sets the tone for how users perceive your communication and engagement efforts.

Verify SDK installation

Confirm the Userorbit script tag is present in the <head> of every page where you want the widget to appear.
Open your site in a browser and check the developer console for any errors related to the Userorbit script.
If you are using the identify method, log in as a test user and verify that a contact record appears in the Userorbit dashboard with the correct name and email.
Test on multiple browsers (Chrome, Firefox, Safari) and on mobile devices to confirm the script loads reliably everywhere.

Open the widget on your site and verify it displays the correct modules (announcements, feedback, help center, etc.).
Check that the widget branding — colors, logo, greeting text — matches your product.
Test the widget position on different screen sizes. Make sure it does not overlap with other UI elements like chat widgets or navigation bars.
Click through each module to confirm content loads and interactions work (submitting feedback, reading articles, etc.).
If you are using a custom launcher instead of the default floating button, verify that window.userorbit.open() triggers correctly.

Prepare your content

Announcements — Have at least one published announcement ready so the widget does not appear empty on launch day. A "Welcome to our updates feed" post works well as a first entry.
Help center — Publish your most critical articles before launch. Prioritize FAQs, getting started guides, and common troubleshooting topics. You can add more articles over time.
Feedback categories — If you have enabled the feedback module, set up categories (Feature Request, Bug Report, General) so submissions are organized from the start.
Roadmap — If you are sharing a public roadmap, populate it with a few items in each column (Planned, In Progress, Completed) so it looks active and intentional.

Configure your modules

Review which modules are enabled in Settings > Widget. Disable any modules you are not ready to use yet — you can always enable them later.
For surveys, make sure targeting rules are set correctly so surveys appear at the right time and to the right audience.
For tours, test each tour end-to-end. Walk through every step and verify that tooltips attach to the correct elements and that the flow makes sense.
For checklists, confirm that each task links to the right action or page.

Set up your team

Invite all team members who need access. See the "Invite team members" article for details.
Assign appropriate roles — admins for people who manage settings, members for people who create content.
Brief your team on how Userorbit works. Make sure everyone knows where to find feedback submissions, how to publish announcements, and how to respond to user input.
Decide on a workflow: who publishes announcements, who triages feedback, who maintains the help center? Clear ownership prevents things from falling through the cracks.

Review settings

Workspace settings — Confirm your workspace name, logo, and timezone are correct.
Portal — If you have enabled the customer portal, review its branding and the sections that are visible. Visit the portal URL and check that it looks professional.
Email settings — If you plan to send announcement emails to subscribers, review your sender name, email address, and email template. Send a test email to yourself.
Custom domain — If you have configured a custom domain for the portal, verify it resolves correctly and has a valid SSL certificate.

Launch day checklist

Use this condensed checklist on the day you go live:

Script installed and loading without errors.
Widget opens, displays correct modules, and looks on-brand.
At least one announcement published.
Help center articles published for common questions.
Feedback categories and roadmap columns configured.
All team members invited with correct roles.
Portal branding and content reviewed (if enabled).
Test email sent and received (if using email notifications).
Surveys and tours tested end-to-end (if enabled).

Once everything checks out, you are ready to go live. Monitor the dashboard closely for the first few days after launch — watch for feedback submissions, check analytics, and be responsive to early user engagement. A strong start builds momentum for ongoing user communication.

Help Center