Start here
The whole picture in one page — what Sarah does, where she does it, what it costs you, and the five-minute install.
Everything before signup is your marketing. Everything after it is Sarah — an AI teammate who lives inside your product, meets a user the moment their state changes, and does the one thing worth the most money there.
| ← your marketing | signup | Sarah → |
|---|---|---|
| ads · content · SEO · launches | the handoff | first success · habit · paid · product feedback |
She is not a support bot waiting to be asked a question. She goes to the user.
Where she works
Four stages, in the order a user travels them. Each one is a page:
- Get them started — first success, and unsticking them on the spot. The gate everything else multiplies by.
- Stop them leaving — catch the cancel, handle the refund honestly, re-warm the ones going cold.
- Grow the account — the right offer to the hesitant, the upgrade for the ones hitting their ceiling.
- Learn from every chat — personas, demand, and bugs verified against your own repo.
The user journey is the long version, including the three states she's still blind to.
Install in five minutes
Paste this before </body>:
<script src="https://www.usersay.ai/sdk/v1/usersay.js"
data-project="your-project-slug" async></script>Then tell her who's using your product, after login:
UserSay.identify({ uid: currentUser.id, plan: currentUser.plan });Only uid is required. Pass whatever else you already have — plan, credits, email, signupAt — and she opens more naturally, and your dashboard shows real people instead of ids.
What that alone gets you
Four moments start firing with no further work:
- First visit — she introduces herself and asks what brought them.
- Pricing page — the URL matches and they linger.
- Out of credits — she watches for HTTP 402 coming back from your own API. If your product already returns 402 when someone runs out, this needs nothing from you, and it catches users in the most convertible state they are ever in.
- Coming back after a gap — the SDK counts sessions itself.
Everything past that is either one line of code where the thing happens (UserSay.trigger('cancel')) or, when you want her to act rather than only talk, a small server you run. How much you have to build draws that line exactly.
Then read one of these
- Meet Sarah — who she is, and why she's built as a character rather than a rulebook. Start here if you're deciding whether you want her in front of your users.
- Plays — the operating experience she arrives with: what a cancel conversation actually is, and why the reflex answer is usually the expensive one.
- The user journey — the four stages in full, and what she can't see yet.
- Install — the complete setup: SDK, React, teaching her about your product, and what happens to your users' data.