Quick Start
The fastest way to understand Repuvane is to go through the loop once, start to finish.
1. See the demo first
Before creating an account, click See demo from the homepage. It's a full, no-login walkthrough of the real dashboard — Overview, Reviews, Reply History, Escalations, and Voice Settings — seeded with realistic sample data. Actions feel real (there's a short delay, like a real save) but nothing is ever written to a database. Refreshing resets it. It's the fastest way to feel out the product before signing up.
2. Subscribe
Repuvane has no free tier or separate sign-up — click View pricing, pick a plan, and complete checkout. Payment comes first; your account is created from that. Once checkout confirms, you'll sign in with the email you paid with. Repuvane uses Clerk for authentication — email/password or a social provider, your choice.
3. Set up your business
Right after your first sign-in, you'll set up the workspace Repuvane will watch:
- Business name — what shows up in the reply itself (e.g. "Bright Smiles Dental").
- Business type — used to tailor voice defaults.
- Organization name — the umbrella company name, shown in the dashboard sidebar. Only matters once you invite a teammate; defaults to your business name if you skip it.
4. Teach Repuvane your voice
Head to Voice Settings. The single highest-leverage thing you can do here is paste 2-3 replies you've actually sent before — Repuvane uses them as a direct style reference instead of guessing from a one-line description. Set your tone, sign-off, and any phrases you'd never say, and use the sliders to fine-tune formal-vs-friendly, concise-vs-detailed, and how conversational it sounds.
5. Add your first review
Until a live platform connection exists, use Add review on the Reviews page to paste one in by hand — the exact same approve/edit/reject/escalate flow runs on it as it would on a real one.
6. Make a decision
Read the draft. If it sounds right, Approve. If it's close, Edit it first. If it's wrong, Reject. If it needs your personal judgment — a refund demand, angry language — Escalate it instead.
That's the whole loop. Everything else in the product supports this one decision, over and over, faster than doing it by hand.