Build, preview, and launch your first experience
Understand the difference between editing content, previewing it, and making it available to customers.
Last updated 9 September 2026
On this page
Start with one goal
Choose Feedback for a brief question, Surveys for a sequence of questions, or In-app messages for an announcement or next step. Push is for native notifications outside your app. The Customer Portal is where customers browse requests, progress, updates, and help.
Work through the composer
Build: write the content and choose the question or message format. Use a descriptive internal name so you can find the experience later.
Design: check its appearance in the live preview. Where available, compare Native, Web desktop, and Web mobile.
Target: choose eligible platforms, the audience, the trigger, and frequency limits.
Review the final content and delivery settings, then use Publish or the appropriate activation control when you are ready.
What each state means
Draft content is not available for normal delivery. Active experiences are eligible when their delivery rules match. Paused experiences stop being eligible while you review them. Archived experiences are retained separately from your current work. Pausing cannot undo something a customer has already seen.
Test the whole journey
Use your own test identity, trigger the experience from the connected product, and complete its action. Open Analyze or Reports to check the result. Keep your test audience narrow until the wording, layout, timing, and response collection all work together. Changing active content can affect later deliveries, so review live edits carefully.