# The person who answers you *travels with you.*#

WOW Club runs women-only group trips, where trust is the product. So the member’s experience and the company’s working view are one build on one set of records: enquiries raise themselves out of what she was already doing, everything she does lands on one thread, and the buddy who answers the first question is the woman who leads the trip.

Storefront and CRM in production · advisor component live since mid-2026 · built on the Apex commerce backbone

one thread · both sides of the counter

“Someone will get back to you.”

a form · a queue · a stranger with your name on a screen

## Interest is a relationship, not a ticket.#

Most travel companies run two systems: a site that collects interest, and a CRM where it lands as a ticket for whoever picks it up. WOW Club’s members are women travelling alone, choosing a group on trust — and trust does not survive that handover. So the storefront and the company’s working view are one build on one backbone: the same records, both sides, a named woman at the other end.

## One system, seen from both sides.#

Everything a member does on the site is already the company’s working record. She never fills in a lead form — no name, no email, no phone — because the site already knows who she is.

We’re four friends — is this one gentle enough for my mother to join?

→ goes straight to her · with a follow-up date on it

a quiet 4-day trip with women my age, somewhere cool in May

Both are four days, cool in May, and an easy pace. More details →

Asked gentle enough for my mother?

Sent the day-by-day, by email

Opened day two of the itinerary

→ the booking is made here, against the same enquiry

Three surfaces, drawn — (01) The buddy who leads a trip is named on its page, with her face and her bio on the page; the question typed under her name goes to her, and raises the enquiry by being sent. (02) The advisor answers from what WOW Club has published — the catalogue is rebuilt for it on every deploy, and each member gets her own session — and the questions it cannot ground go to a person. (03) The quotation her buddy builds arrives against that same enquiry in her account, and the deposit is paid there.

> The system remembers, **so the buddy can.**

Service memory — every touch becomes context for a person

## Enquiries aren’t filed. They happen.#

She arrives, finds a trip and asks — and from that first touch to the deposit, all of it happens on one thread. Some steps repeat; the journey doesn’t restart.

#### Arrives

#### Asks

#### Remembers

#### Answers

05 Books — quotation to deposit

The journey, whole — she arrives, she asks, the thread remembers, her buddy answers, she books. Asks — four ordinary moments raise the thread; nothing to fill in, and never a second one. Remembers — every touch is written down, and every touch claims a morning. Answers — the woman replying has the thread, the profile and the trip in one view. Books — on the same thread, against the quotation her buddy built.

↪ some steps repeat — but the journey runs one way, from arriving to booked

## The same woman, *end to end*.#

Every trip names the buddy who leads it, and she is the one on the thread from the first question to the last night of the trip.

### One thread, not an inbox.#

Whatever a member does about a trip joins the same thread — a question, a schedule, an itinerary, a quotation. Her buddy opens one conversation, not a search.

### Tomorrow is already claimed.#

Every touch is written with a follow-up date on it, for the next morning. The queue is worked daily, and a manager can see each promise kept.

### Birthdays are business.#

Her city, her birthday and every question she has asked are surfaced to the buddy who has her thread open — brought forward at the moment they matter, not looked up.

**Warmth you can staff** — remembering is the system’s job, so it stops depending on who happens to be at the desk.

## Build the CRM into the product.#

The portable pattern: put the customer surface and the company’s working view on one backbone. Let enquiries raise themselves at the moment of real interest, and keep one per person per trip. Write every touch down so a person picks the thread up warm. And let the booking happen where the conversation already lives.

> The advisor is one component, not the system. **Grounded on published content · the questions it cannot ground go to a person**

Stack — SvelteKit storefront · Apex commerce-and-CRM backbone · Razorpay payments · advisor: Mastra + PostgreSQL on AWS · English-language advisor work