A short welcome
Use the name and company already known. No repeated profile questions.
Onboarding concept / 08 October 2026
A smoother first hello.
One useful thing, done.
Help a new tenant experience Suvi’s value in a real conversation. Ask for setup only when their task needs it.
A proposed walkthrough, not a live application. All names, messages and outcomes below are illustrative. No accounts connect and no tasks execute in this file.
01 / The main journey
From welcome to a useful result.
Four moments in one continuous experience. The task takes place in normal chat, so the conversation remains available afterward.
Pick one task
Three relevant starters, or type your own request.
Work with Suvi
Ask for missing details. Connect an app only if needed.
See the result
Confirm what actually happened. Stay in chat and keep going.
An equally valid route: Welcome → Explore on my own → normal chat. Getting started stays available whenever the user wants help.
02 / What the tenant sees
A concrete example.
Expand or collapse each card. The sample follows a reminder from first visit to confirmation; the controls shown inside are illustrative.
01 Welcome without a questionnaire
SUVI · ACME WORKSPACE
Welcome, Priya.
Let’s take one thing off your plate.
Try your first task →Explore on my ownBehind the experience: Reuse known information. If a name is unavailable, simply say “Welcome.” Keep the assistant named Suvi; owners can rename it later in Settings.
02 Give them an easy starting point
YOUR FIRST TASK
What would you like help with?
◷ Remind me about something
▤ Summarize a document
✎ Draft a message
Behind the experience: Show supported tasks for this user. A document starter opens the existing attachment input; a draft does not send a message.
03 Learn by doing, in the real chat
SUVI · NEW CONVERSATION
SUVIWhat should I remind you about?
PRIYAFollow up with Rahul tomorrow at 10 AM.
SUVIThat’s 9 October at 10 AM, India time. Where would you like the reminder?
PRIYAHere in the app.
Behind the experience: This example assumes an in-app delivery option is supported. Confirm delivery support during research; ask about timezone or destination only when needed.
04 Confirm an actual outcome
✓ EXAMPLE SUCCESS STATE
Your reminder is set.
Follow up with Rahul
9 October · 10:00 AM IST
Delivery: in-app notification
What else can I help with?
Optional: Message Suvi on WhatsApp ↗Behind the experience: Only show success after the task succeeds. WhatsApp appears only when available. Keep the person in this conversation instead of opening a separate completion screen.
03 / Only when needed
A connection is a short detour.
For “What’s on my calendar?”, explain why access is needed. After connecting, continue the original request rather than leaving the user in Settings.
Task → check required access
- Access available: run task → confirm actual success → continue in chat.
- Access missing: explain why → connect app → resume the same task.
- Connection skipped or failed: keep request → offer retry or another task.
- Task failed: explain the problem and offer retry. Do not count it as success.
04 / Make it forgiving
No dead ends.
Finishing setup and successfully using Suvi are different things. Both the interface and measurement should reflect that.
Skip without losing help
“Explore on my own” opens normal chat. A Getting started entry lets people return later. Skipping does not count as a completed task.
Resume without repeating
Keep the conversation and unfinished request through refresh or app connection. Retry without creating duplicate messages or reminders.
Respect each person’s role
Owners manage workspace settings and connections. Members get relevant starters within their access, without repeating company setup.
05 / The design decisions
What changes from the current tour?
| Moment | Current active tour* | Proposed experience |
|---|---|---|
| First decision | Name the assistant after the welcome. | Choose a useful task; rename later in Settings. |
| Learning | Click through spotlights for chat, apps and WhatsApp. | Do one real task with brief, relevant guidance. |
| Connections | General introduction and optional Google permission warning. | Explain and request access when the task needs it. |
| Completion | Finish or skip sets the workspace’s tour-completed flag. | Record dismissal separately from actual task success. |
| Explain the shared direct-message and group numbers. | Offer the appropriate channel as optional continuation. |
*Based on the local-code review from 7 October. Deployed behaviour still needs verification.
Measure the first useful result.
Track time to first successful task, the share of new users who complete one, where they stop, and whether they return. Establish a baseline before setting numerical targets.
06 / Smallest implementation
Build on what already exists.
1. Reuse the chat
Use the existing greeting, composer, attachments and starter prompts. Replace the long tour with the brief entry shown above.
2. Keep the essentials
Expose owner renaming in Settings, preserve permissions, and support skip, retry and task resumption.
3. Validate before rollout
Confirm reminder delivery and task-success signals. Test mobile, members, connection failure and returning users, then pilot with new tenants.