RYPLY Homepage Review · Direction A
Hero Recognition Mechanism Demo Ledger Setup Trust Train Receipts Pricing FAQ
Notes ↓ All feedback →
① THE SITE MOCKUP — this is the proposed homepage. Click 💬 Comment on any section to leave feedback.
RYPLY · the WhatsApp reception layer

The message you didn't know you missed.

Someone reached out. You meant to get back to them. The day happened. When you finally found their message, they'd already booked the place down the road.

RYPLY reads your website, picks up your voice, and answers when a message lands. It books, it follows up, and the moment it isn't sure, it stops and brings you in. Built from your site in minutes. It never pretends to be you.

Try it for $7 — seven days→ See how it works
It would rather hand you a message than fake its way through one.
The quiet gap

You know the feeling. You don't always know what it cost you.

If you work alone

A message comes in between clients. You'll reply at lunch. Lunch turns into tomorrow. The customer, who was ready to book an hour ago, has already gone somewhere else.

If your trade is the evening

It's worse, and the usual advice doesn't apply. "Just check at lunch" is useless. Your customers decide at 11pm. You're mid-service until 1am. The leads you couldn't reach are cold before you're free.

If you've just taken on a couple of people

The gap moves inside. A customer gets two replies from two of you with two different prices. Or no reply, because everyone thought someone else had it.

If your business runs on regulars

The cost hides. A rebooking you forgot to nudge. A thread that went quiet. You don't notice for three months. Then the books look thin and you can't quite say why.

The bind

You'd rather lose the booking than send a reply that doesn't sound like you. We know. Most owners would. That's the bind: answer everything personally and the gap eats your edge, or use a template and the template eats your brand.

What RYPLY actually does

What it does with a message.

01 — RECEIVE

Receive

A message lands on WhatsApp. RYPLY sees it in seconds and lets the customer know someone's there. Not silence, not a holding reply — a real answer starting.

02 — GUIDE

Guide

It asks the next question. Which branch. What postcode. When suits. It doesn't guess, because a guessed answer is how you get a customer in the wrong place at the wrong time.

03 — BOOK

Book

It books from your calendar, in your words. Confirms. A day or two before, it nudges.

04 — HANDOFF

Handoff

Here's the part most reply tools skip. The moment it isn't sure — a question needs your judgement, or your memory of a customer, or a price that depends on the job — it stops. Tells the customer you'll pick it up. Comes to you with the whole thread.

05 — LEARN

Learn

It carries the correction forward. Tell it once that you don't quote over message, or that Mark's dog bites, or that Janet always wants the 4pm. It remembers.

Notice what it doesn't do. It doesn't sign your name to a price it made up. It doesn't answer when it should ask. It doesn't pretend to be a person. The honesty isn't a setting you can switch off. It's how the thing is built.
See it work

See it answer from your site.

Put your website in. Message it like a customer.

Illustrative — not a real transcript.

Illustrative — not a real transcript
Customer
Do you do evenings? And roughly what do you charge for a trim and colour?
RYPLY
Hi! We do — Thursdays until 8. For a trim and colour it depends on length and what we're using. Mind if I ask a couple of quick things first so I can give you a real number?
Customer
Sure. Just past the shoulders, half-head of highlights in February.
RYPLY
Got it. Sade has Thursday 6:15 open. Want me to hold it while she puts a quote together? She'll have the number within the hour.
The boundary

What RYPLY handles. What stays yours.

RYPLY handles
  • The first reply — fast, in your voice
  • The clarifying questions
  • Bookings, reschedules, cancellations
  • Confirmations and reminders
  • The rebooking nudge you keep forgetting
  • After-hours reception
Comes to you
  • A complaint that needs reading
  • A regular asking a favour
  • A quote you can't give without seeing the job
  • Anything custom or one-off
  • Anything it's not certain about
RYPLY never pretends to be human. Your customers always know it's an assistant. We would rather it pass you a message you could have handled yourself than let it fake its way through one it couldn't. If that's a dealbreaker, this isn't your product. If it's the thing you've been waiting to hear, it is.
Website in. Concierge out.

From your URL to live on WhatsApp.

No script to write. No decision tree to map. You give it something to read. It does the rest.

01

Paste your URL

One field. yourbusiness.com.

02

It reads

Services, tone, hours, boundaries — pulled from your site. Add a price list or service guide and it folds them in as written.

03

It shapes itself

Voice, scope, where its line is. You can adjust any of it.

04

It's live

On your WhatsApp. Starts in Approval Mode — it drafts, you approve. Dial up autonomy when you trust it.

You're always in control

Start with everything in review. Loosen the leash when you trust it.

Three modes. Begin with it drafting every reply for your sign-off. When it's consistently sounding like you, let it run bookings on its own.

01

Approval Mode

It drafts. You approve every reply before it sends. Start here.

02

Auto-Schedule

It handles bookings in your hours, no approval needed. You see everything.

03

Full Autonomy

It runs standard inquiries. Sensitive moments still come to you.

Train it like you'd train a person

Tell it what missed. It fixes it — and shows its work.

No prompt engineering. No model training. No config screen with forty sliders. Tell it in plain English what didn't feel right, and it prepares the change for your approval — with the boundary it protected while making it.

Every fix is a decision you sign off on. Nothing changes quietly. That's the difference between training software and training a person — the person remembers because they understood. RYPLY remembers because you told it to.

Where it got that from

Receipts, not mysterious confidence.

Customers see a useful answer. You can see what taught it. Every fact RYPLY uses comes from a page on your site or a document you gave it.

Services and pricing +

SOURCE: your services pages + uploaded price listWhat you offer, what it costs, the packages. If your site says it, RYPLY knows it. If you uploaded a price sheet, it folds the exact numbers in as written.

Hours and availability +

SOURCE: your contact page + calendarWhen you're open, when you're booked, what slots are real. Connected to your live calendar so it never offers a time that's gone.

Tone and voice +

SOURCE: learned from your website copyHow you phrase things. The words you reach for. Not a template — your actual voice, pulled from how you already write.

Boundaries — what it won't answer +

SOURCE: you define theseWhat RYPLY should never claim, what needs your review, when uncertainty becomes a handoff. You draw the line. It doesn't cross it quietly.

No invented answers. No pretending a vague page said more than it did. If the source doesn't cover it, RYPLY says so and brings it to you.

The offer

Seven dollars. Seven days. Then you decide.

Point RYPLY at your website. Watch it read your business in a few minutes. Spend a week sending it the messages you actually get. See if it sounds like you, hands off when it should, and catches the things you've been quietly missing.

$7 for 7 days

Everything on. Cancel from inside the app. No retention call.

Start my seven days→
Before you start

The questions everyone asks.

Will it sound like a robot? +
No. It sounds like your website, which sounds like you. It learned your voice from your copy. If a reply ever feels off, tell it in plain language and it adjusts.
Does it pretend to be human? +
Never. It introduces itself as your assistant — not a person. Customers always know what they're talking to. That's a rule, not a setting.
How does it get set up? +
Paste your URL. It reads your site and shapes itself around it. Add documents and it folds them in. You refine anything you want before it goes live.
What happens when it doesn't know something? +
It says so, and routes it to you with the whole thread attached. The customer never repeats themselves.
Is it just WhatsApp? +
Today, yes. WhatsApp is where most of your messages land, so it's where we started. More channels are coming. We'll tell you when they're real.
What's the $7 for 7 days? +
A full week, fully working, for seven dollars. Put it on real customers. Cancel before day 7 and pay nothing more.
Can I cancel? +
Any time, in-system. Month-to-month from day 8. No retention call.
The next one

The next one you miss, you won't know about either.

We only see the cost afterwards — a thinner month, a quieter quarter, a regular who drifted off. RYPLY catches them. In your voice. At any hour. And hands you the ones that need a human, out loud, every time.

Seven dollars. Seven days.→
↑  above = the proposed site  ↑
↓  below = context, copy variations, notes for Ross  ↓
② CONTEXT & NOTES FOR ROSS — copy variations, ICP map, sitemap, design system, continuation prompt
Copy variations

Three directions were tested. A is built above. B and C are here for comparison.

Each direction is a different pre-suasive bet — a different answer to "what's the focal point of the whole page?" They're genuinely different in tone, not three heroes on one body. The full section-by-section copy for each is in the PKB strategy doc.

DIRECTION A · BUILT ABOVE ✅

The quiet miss

Hero: "The message you didn't know you missed."
Focal point: the reply you didn't know you didn't send. Tone: intimate, almost a whisper. The recognition section runs a montage (solo / after-hours / team / regulars) so every visitor shape sees themselves. Lowest execution risk. The only direction whose pain is literally true for all 8 personas.
CTA: "Try it for $7 — seven days"
SECTION FLOW
  1. Hero — The message you didn't know you missed
  2. Recognition montage — solo / evening / team / regulars / the bind
  3. Mechanism — Receive → Guide → Book → Handoff → Learn
  4. Demo — "See it answer from your site"
  5. Ledger — what she handles / what stays yours
  6. Trust — never pretends to be human (the honesty clause)
  7. Pricing — $7/7 days
  8. Final CTA — "The next one you miss, you won't know about either"
Recognition montage punch: "You'd rather lose the booking than send a reply that doesn't sound like you. We know. Most owners would. That's the bind: answer everything personally and the gap eats your edge, or use a template and the template eats your brand." Trust callout: "RYPLY never pretends to be human. Your customers always know it's an assistant. We would rather it pass you a message you could have handled yourself than let it fake its way through one it couldn't. If that's a dealbreaker, this isn't your product. If it's the thing you've been waiting to hear, it is."
DIRECTION B · ALTERNATIVE (not built)

Who's replying to this one?

Hero: "Who's replying to this one?"
Focal point: the unowned thread, the shared-inbox shambles. Tone: a beat more exasperated. Serves Alex (team lead) and Daniel (two-location) hardest. The strongest unity play — "we've all been in this inbox." But it alienates solo practitioners and undersells the after-hours reality.
CTA: "Try it for $7 — seven days"
SECTION FLOW
  1. Hero — Who's replying to this one?
  2. Recognition — The shared inbox nobody actually shares
  3. Mechanism — One front door. The right person behind it.
  4. Demo — "See it route, before you trust it to"
  5. Trust — Your team's voice. Your team's judgement.
  6. Pricing — $7/7 days (team tiers foregrounded)
  7. Final CTA — "You meant to sort the WhatsApp out. This is sorting it."
Recognition: "It started simple. One number, a few of you, whoever's free replies. Then the customer got two answers. Or one answer from Marcus's personal phone, and now they have his cell forever. Or the 'read' receipt went on when Priya opened it, so you assumed she'd handled it, and she assumed you had." Mechanism (team-specific): "It asks the routing question before it commits. Which branch. Which service. Who's best placed. It doesn't assume the location or the team member. It hands off with the thread — not a forwarded message the next person has to decode."
DIRECTION C · ALTERNATIVE (not built) — best trust-builder

It sounds like you

Hero: "It answers for you. Never pretends to be you."
Focal point: voice and fidelity. The reputation-protective objection front and centre. Tone: confident, almost a dare — "we know you don't believe this, so look." Nails the one objection that blocks every persona (off-brand reply). But as the opening frame it loses Priya (after-hours) and Tom (trades) in the first 2 seconds. Its best line ("sounds like you because it read your site") was relocated into Direction A's proof section.
CTA: "Hear it sound like you — $7 for seven days"
SECTION FLOW
  1. Hero — It answers for you. Never pretends to be you.
  2. Recognition — "You'd rather lose the booking than send the wrong words"
  3. Mechanism — How it learns your voice — and knows when to stop using it
  4. Demo — "Send it a message. See if you'd have written that."
  5. Trust — The one rule that doesn't bend
  6. Pricing — "Seven dollars to find out if it sounds like you"
  7. Final CTA — "The next message can sound like you. Even at midnight. Even on holiday."
Recognition (Sade's wound, made the centre): "If you've built your business on your voice, a templated reply isn't a shortcut. It's a betrayal of the exact thing people pay you for. So you answer every message yourself. And the messages you can't get to — because you're in session, or asleep, or on holiday — those messages cool. You can't win. Reply personally always, and the gap eats your referrals. Use a template, and the template eats your brand. There hasn't been a third option. This is the third option."

Why A won (and what was folded in from B and C)

A won on universality. "The message you didn't know you missed" is the only hero whose pain is literally true for all 8 personas — Neri missed it between clients, Priya missed it at midnight, Lou missed it for three months, Alex's team collectively missed it, Tom missed it under a sink, Sade missed it on holiday.

From C, folded in: the "sounds like you because it read your site" line (now in the proof beat), the "you'd rather lose the booking" Sade-catch line (now in the recognition montage), and the triple-stated honesty clause (now in the trust section).

From B, folded in: one line in the recognition montage — "maybe you've got a team now" — so Alex and Daniel see themselves without the whole page becoming team-only.

The audience

8 ICP shapes. Most visitors blend 2-3.

Harry's feedback was clear: "they are all of these, not just two." The page can't live inside one persona's day. It has to lead on the one pain all 8 share (the silent miss) and let the mechanism do the unifying. Here's the full set.

Neri — Solo practitioner

One service, one number. Replies herself between clients. Can't be in two places. Fears the wrong reply more than the slow one.

Alex — Small team lead

Shared inbox, no owner. Two people answer the same customer with different prices.

Priya — After-hours owner

Takeaway, mobile beauty, emergency trades. Customers decide at 11pm. "Reply at lunch" is useless.

Marco — Growing-pain owner

Was solo, just hired 2-3. The business outgrew owner-as-inbox. He's the bottleneck.

Sade — Reputation-protective

WhatsApp IS the brand. Would rather lose the booking than send an off-brand word. The honesty clause is her only unlock.

Lou — Returning-customer biz

Salon, clinic, groomer. A dropped regular is a lost year. The cost hides for 3 months.

Daniel — Two-location owner

Two branches, one number. Cross-branch fumbles. Needs it to ask "which branch" before confirming.

Tom — Trades / quote-by-message

Plumber, sparky. Every message is "how much for X" with a photo. Needs triage, not chat.

The overlapping visitor: Neri+Sade+Lou is the most common blend — a solo, word-of-mouth, high-repeat business. The page must land all three pains without picking one.

Site structure

Sitemap — what stays, what's cut, what's new.

The live wa.ryply.com is a 6-page Vite SPA. The rebuild consolidates around the mechanism. Here's the proposed structure.

/ Homepage — the full journey (all 10 sections above) ├── /pricing Tier detail (Studio/Practice/Enterprise) + trial + FAQ ├── /signup 8-step wizard (website → intent → voice → WhatsApp number) ├── /login Returning users ├── /privacy NEW — required for $7 trial billing ├── /terms NEW — required for trial billing ├── /404 NEW — branded not-found │ ├── /product CUT — folded into homepage (was a thin subset) └── /workflows CUT — folded into homepage (was a thin subset)

Homepage section order (the pre-suasion chain)

Each section pre-suades for the next. You can't skip ahead without losing the visitor.

1. Hero (frame the gap) ← visitor recognises the pain 2. Recognition montage ← visitor sees themselves (all 8 shapes) 3. Mechanism (Receive→Guide→Book→Handoff→Learn) ← visitor wants the solution 4. Demo (see it work) ← visitor believes it might work 5. Ledger (handles / yours) ← visitor trusts the boundary 6. Trust (never pretends human) ← visitor's last objection answered 7. Pricing ($7/7 days) ← visitor is ready for the offer 8. Final CTA (close the loop) ← visitor acts
Design system

How to read this page — site vs notes.

This page has two zones. Here's the visual language for each so you always know what you're looking at.

Site mockup (Zone 1)

Warm paper background, sharp buttons, the actual proposed homepage. This is what would ship to agent.ryply.com.

Context & notes (Zone 2)

Cooler grey background, cobalt zone label at top. Copy variations, ICP map, sitemap, prompts. NOT part of the live site.

Lime = signal / ready

Used only for active states, CTAs on dark, "ready" tags. Never decorative. Never large background blocks.

Cobalt = trust / action on light

Primary CTA on light surfaces, links, trust accents. The "RYPLY brand" colour.

Amber = handoff / human

Reserved for "comes to you" moments. Never used as general highlight.

Ink = dark sections

Hero threshold, mechanism section, final CTA. The dark/light rhythm is intentional.

Design tokens (locked)

Font: Geist + Geist Mono  ·  Colours: ink #0a0b12, lime #85fa79, cobalt #0b46e0, amber #f59e0b, paper #fff, warm #f7f4ee
Radius: buttons 8px, cards 16px, large panels 24px (sharp, not pill)  ·  Motion: 160ms cubic-bezier(.32,.72,0,1), no linear easing
No: pill buttons, Lucide icons, purple gradients, glassmorphism blobs, em-dash chains, rule-of-three lists

Decision state

What's locked. What Ross should push back on.

✅ LOCKED

• Name: RYPLY (all caps)
• Mechanism: Receive → Guide → Book → Handoff → Learn
• Trust line: "Always ready to receive. Human when it matters."
• Honesty rule: never pretends to be human
• WhatsApp-first (no multi-channel claims)
• No fabricated metrics
• $7/7 days → Studio $249 / Practice $597 / Enterprise
• Visual: Geist, ink/lime/cobalt/amber, sharp buttons
• Direction A selected (universal pain hero)

⚡ OPEN — push back

1. The hero line — universal but is it memorable?
2. Recognition montage — covers spread or feels like a list?
3. Honesty clause — "dealbreaker" too aggressive?
4. Demo trade — salon (Sade) right one to show?
5. Pricing lead — $7 trial first, any concern?
6. Missing: social proof (none exists), founder note?
7. Should B or C replace A for a specific audience?
8. Put your own flavor on the copy — it's yours to shape

Pick it up

Where everything lives + how to continue.

Full strategy doc (PKB)

All 8 personas at depth, all 3 directions with complete section copy, the comparison table, the pre-suasion application, and the humanized final:

/Users/harry/quantumreports/pkb/docs/RYPLY-HOMEPAGE-WAVE-1.5-COPY-STRATEGY-20260713.md

Brand doctrine (read these for the rules)

ryply-brand-shared/references/brand-voice-library.md — voice rules, proof doctrine
ryply-fast-lane/SKILL.md — pricing, trust line, CTA rules
ryply-sidewalk/references/pkb-sidewalk-knowledge.md — hero copy, recognition blocks
ryply-slow-lane/references/pkb-slow-lane-knowledge.md — mechanism, differentiation, objections
pre-suasion-copy/SKILL.md + pre-suasion-page-architect/SKILL.md — Cialdini applied to RYPLY

Local files

/Users/harry/development/websites/ryply-site/index.html — the local build
/Users/harry/development/websites/ryply-site/COPY.md — the copy spec
/Users/harry/development/websites/ryply-site/DESIGN.md — the design system
/Users/harry/development/websites/ryply-site/PLAN.md — sitemap, phases, skill map

Continuation prompt (copy/paste to pick up the work)

# Picking up the RYPLY homepage work Context: I'm continuing the RYPLY homepage rewrite. Wave 1.5 is done — 8 ICP shapes mapped, 3 directions tested, Direction A selected and built. Harry wants me to review / continue. Read first: - RYPLY-HOMEPAGE-WAVE-1.5-COPY-STRATEGY-20260713.md (in PKB docs) - ryply-brand-shared/references/brand-voice-library.md - ryply-slow-lane/references/pkb-slow-lane-knowledge.md - pre-suasion-copy/SKILL.md The built page: this mockup (Direction A). What I want you to do: # Fill in your actual ask. Examples: # "audit the copy against voice rules and push back where it drifts" # "rewrite Direction B (team-first) as a full page so we can compare" # "build the missing sections — founder note, social proof strategy" # "crucible the honesty clause — is 'dealbreaker' the right word?" # "take the copy in your own direction — put your flavor on it"

Server access (if you need to deploy)

rsync -av -e "ssh -i ~/.ssh/mcp_logs" <file> root@208.87.135.180:/var/www/<subdomain>.sal8.com/

SSH key: ~/.ssh/mcp_logs. New subdomains need a DNS record (Porkbun for ryply.com), then certbot on the server.

Comment on this section

—
No comments yet. Be the first.
View feedback →