# Guide Users Through Onboarding Without a Ticket

> How Peeve guides new SaaS users through setup in-app: it shows each step on the live screen, completes setup actions with confirmation, and hands off.

Canonical: https://peeve.ai/use-cases/onboarding/

Peeve guides new users through setup inside your product. It shows each step on the user's live screen, moving the cursor to the control they need, and, where you allow it, completes a setup action after confirming the effect. Showing the steps is on every plan; completing actions is a Do feature on the Growth plan and up.

## How do users ask for this?

- "How do I get started?"
- "What do I need to set up first?"
- "Can you walk me through connecting my account?"

## What does Peeve do: show or do?

Peeve turns a setup checklist into motion: it shows the user where each control is and walks them through, step by step, on the real interface. Where a step is a backend action you have allowed, it can complete it after confirming, so onboarding finishes rather than stalling.

## Guardrails: confirmation and audit log

Peeve runs only the actions you allow, within the logged-in user's permissions, and it confirms the exact effect before anything changes. Every action is written to a signed audit log, and the model never sees a password or token: it requests a capability by name.

## Which plans include it?

Guiding the user step by step is on every plan, including Starter (Answer and Show, read-only). Completing setup actions as backend tasks is a Do feature, on the Growth plan ($199 a month) and above.

## Questions

### Can Peeve onboard new users on its own?

Yes. Peeve shows each setup step on the user's live screen and walks them through in order, on every plan. Where a setup step is a backend action you have allowed, it completes it after confirming the effect, on the Growth plan and up, so onboarding finishes instead of stalling on a support ticket.

### What if a user gets stuck during onboarding?

Peeve resolves the step on the screen rather than linking a help article, and if a request genuinely needs a person it hands off to your team with the full session attached: what the user was doing, where they stuck, and a replay, so your team continues from context.
