Steps

Welcome modal with personalization

Open with a friendly welcome that addresses the user by name if possible. State the ONE thing they will accomplish in this tour. Example: 'Hey [Name]! Let me show you how to create your first project in under 2 minutes.' Keep it warm but brief.

Highlight the primary action area

Point to the main CTA or creation button. Explain what happens when they click it. Use language like 'This is where you will spend most of your time' or 'Click here to get started.' Make the action feel exciting, not administrative.

Show the workspace or dashboard

Briefly orient users to the main layout — where to find key sections. Do NOT explain every menu item. Focus on the 2-3 areas that matter most for their first task. Example: 'Your projects live here, and your settings are here.'

Guide to first meaningful action

Walk them through creating, building, or completing their first task. This step should directly lead to the activation event. End with a congratulatory message: 'You just created your first [thing]! You are all set.'

Variations

Minimal Welcome (2 steps)

For simple products: (1) Welcome + what you will do, (2) Click here to start. Best for tools where the UI is self-explanatory.

Data-First Welcome

For analytics or data products: Start by guiding users to connect their first data source before showing the dashboard. The empty dashboard is meaningless without data.

Role-Based Welcome

Ask the user's role first, then show a tour tailored to their persona. Admin sees settings and team management. End user sees their daily workflow.

Implementation Guide

Using Escourtly, install the Chrome extension and navigate to your app as a new user would see it. Create 4 steps matching the template above, customized with your product's actual UI elements. Set the tour to trigger on first login only (frequency: once). Target new users who signed up within the last 24 hours. Write tooltip copy in second person ('You can...' not 'Users can...'). Keep each tooltip under 40 words. Use the product's existing terminology consistently. Test the tour with a team member who has not seen the product before. If they cannot complete the guided task in under 3 minutes, simplify.

Frequently Asked Questions

Should the welcome tour auto-play or be opt-in?

Auto-play for new users on their first login. Display a brief intro modal (Step 1) that the user can dismiss if they prefer to explore alone. Most users will engage — welcome tours have 70-80% start rates when auto-triggered.

What if my product requires setup before the tour makes sense?

Defer the tour until setup is complete. For example, if users need to connect an integration first, guide them through that separately, then trigger the welcome tour once data is available.

How long should each step take?

Each step should take 10-20 seconds to read and act on. The entire 4-step tour should complete in under 2 minutes. If a step requires more than 20 seconds, break it into two steps.

Ready to Build Better Product Tours?

Create interactive onboarding guides in minutes. No coding required.

Start Free Trial