Case study — customer experience + CRM, one system

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

Ask.Remember.Answer.Travel.
01 — The situation

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.

02 — What we built

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.

Three surfaces, one record
01 · The trip page
02 · Ask AI
03 · Her account
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

03 — Arriving to booked

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

search, or the advisor

Asks

four ways in, no lead form
Asks: four ordinary moments, one thread, and nothing to fill inTHE MOMENT SHE ENGAGESNO LEAD FORM — NO NAME, NO EMAIL, NO PHONE TO RE-TYPETYPED UNDER HER BUDDY’S NAME, ON THE TRIP’S OWN PAGE“Gentle enough formy mother?”HER WORDS ARE THE ENQUIRY —KEPT ON THE THREAD, VERBATIMAsks her buddythe question she typesunder her nameHER WORDS, KEPTWants the planthe day-by-day,asked for by emailONE TAPOpens the plana day of the itinerary,opened on the pageONE TAPShapes a journeydates, party, comfort,notes — kept as she goesBESPOKEHer thread on that tripLOOKED FOR FIRSTNONE OPEN · RAISED NOW, FROM HER ACCOUNTONE ALREADY OPEN · THE TOUCH JOINS IT Asks: four ordinary moments, one thread, and nothing to fill inTHE MOMENT SHE ENGAGESNO LEAD FORM — NO NAME,NO EMAIL, NO PHONE TO RE-TYPE“Gentle enough formy mother?”HER WORDS ARE THE ENQUIRY —KEPT ON THE THREAD, VERBATIMAsks her buddythe question she typesunder her nameHER WORDS, KEPTWants the planthe day-by-day,asked for by emailONE TAPOpens the plana day of the itinerary,opened on the pageONE TAPShapes a journeydates, party, comfort,notes — kept as she goesBESPOKEHer thread on that tripLOOKED FOR FIRSTNONE OPEN ·RAISED NOWONE OPEN ·IT JOINS IT

Remembers

every touch, written down
Remembers: one thread, every touch written, and tomorrow already claimedONE THREAD, AND EVERYTHING ON ITEVERY TOUCH LEAVES A DATE ON ITDAY 1 · SHE TYPES“Gentle enough for my mother?”DAY 1 · SHE ASKS FOR THE PLANthe day-by-day, sent to herDAY 3 · SHE OPENS THE PLANday two, openedDAY 5 · HER BUDDY QUOTESbuilt by a person, not a ruleDAY 6 · SHE BOOKSdeposit paid, same enquiryTomorrow’s follow-upevery touch is written with adate on it — the next morningTHE QUEUE IS WORKED EVERY DAYHer quotationbuilt by a person, openedin her accountBOOKING AND PAYMENT, SAME PLACEEACH ENTRY CARRIES ITS KIND — HER WORDS WHEN SHE TYPES THEMTHE THREAD’S OWN STATESDRAFTFOLLOWUPON HOLDRESOLVEDARCHIVEDCLOSED Remembers: one thread, every touch written, and tomorrow already claimedONE THREAD, ALL OF ITDAY 1 · SHE TYPES“Gentle enough for my mother?”DAY 1 · ASKS FOR THE PLANthe day-by-day, sentDAY 3 · OPENS THE PLANday two, openedDAY 5 · HER BUDDY QUOTESbuilt by a personDAY 6 · SHE BOOKSdeposit paid, same enquiryTomorrow’s follow-upwritten with a date on it,the next morningWORKED EVERY DAYHer quotationbuilt by a person, openedin her accountBOOKING AND PAYMENT, SAME PLACETHE THREAD’S OWN STATESDRAFTON HOLDCLOSEDFOLLOWUPARCHIVEDRESOLVEDEACH ENTRY CARRIES ITS KIND — HERWORDS WHEN SHE TYPES THEM

Answers

the person, in one view
Answers: everything the reply knows came from the thread or her profileSERVICE MEMORYWHAT THE SYSTEM HOLDSWHAT HER BUDDY SENDSMEMBERNisha R.CITYPuneBIRTHDAY14 MayTRIPMisty Mountain Reset · 8 MayTHREADopen · day 5ASKED“Gentle enough for my mother?”SENTthe day-by-day, by emailDUEfollow-up armed for todayBUDDYMeera D.LEADSthis trip, 8 MayALL OF IT FROM THE THREAD OR HER PROFILEMeera D.WOW BUDDY · LEADS THIS TRIPHi Nisha — I lead this one myself.Day two is the only long walk, andthere is a car for anyone who wouldrather ride. Your mother will bevery welcome with us.See you in May — and a happy 14th.SENT ON HER THREADDAY 5 · 09:40She is the one who travelsthe buddy on the thread leads thetrip she is answering forthe thread and the person, in one view Answers: everything the reply knows came from the thread or her profileWHAT THE SYSTEM HOLDSMEMBERNisha R.CITYPuneBIRTHDAY14 MayTRIPMisty Mountain ResetTHREADopen · day 5ASKED“Gentle enough for my mother?”SENTthe day-by-dayDUEfollow-up armed todayBUDDYMeera D.LEADSthis trip, 8 MayALL OF IT FROM THE THREADOR HER PROFILESERVICE MEMORYthe thread and the person,in one viewWHAT HER BUDDY SENDSMeera D.WOW BUDDY · LEADS THIS TRIPHi Nisha — I lead this one myself.Day two is the only long walk, andthere is a car for anyone who wouldrather ride. Your mother will bevery welcome with us.See you in May — and a happy 14th.SENT ON HER THREAD · DAY 5She is the one who travelsthe buddy on the thread leadsthe trip she answers for

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

Continuity by design

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.

04 — What this proves

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

Let's find the work AI should be doing in your organization.

Whether you are exploring an idea or improving a system already in use, we’ll help you decide what is worth doing next.

Book 30-min intro

Prefer to start async?

hello@thoughtfulrobots.ai

Hyderabad · Remote

Questions before you book?

Read the FAQ

Follow along

START A CONVERSATION

Tell us about the work.

A few lines about your product and where AI might belong. We usually reply within one business day.