The problem
Member requests come in at all hours, by phone and chat, and wait until someone is on the desk. When they are answered, the service depends on who is on shift and what they remember about that member.
What goes wrong
- The agent sounds like a call center. It asks the member to spell their name, reads a disclaimer, and offers a menu, which is the opposite of what a membership pays for.
- It cannot act. It takes the request and promises someone will follow up, which is what the voicemail and the unread chat already did.
- It forgets. The member asked for the same villa and the same car last spring, and the agent starts from a blank form, so the member repeats themselves and the coordinator looks like they were not paying attention.
The approach
- Write the standard down first: how members are greeted, what the agent may confirm on its own (a table, a car, a reservation inside the preferred vendor list), and what always goes to a coordinator.
- Connect the agent to the member profile, the vendor list, and the request board, so a request becomes a tracked task with an owner, not a message in a thread.
- Give the agent the member's history before it answers, so the second request starts from what the club already knows.
- Run it beside the desk with every transcript reviewed, and keep the review after launch so each miss becomes a rule.
When it works
When most requests fall into a short list (a table, a car, a reservation, a change to one of those) and a coordinator takes the rest. The agent takes the call, confirms the details, and opens the task. The coordinator handles the villa, the complaint, and the moment that needs a person.
Why the phone and the chat first
A members club sells one thing: the request gets handled, and handled well, whoever is on shift. The phone and the member chat are where that promise is tested. A member texts at 11:40 on a Saturday: a table for six tomorrow, somewhere new, the usual wine. The thread sits until the desk opens. By morning the member has booked it themselves and wonders what the membership is for.
An AI agent on the line and in the chat fixes the thing that was actually broken: nobody was there, and when someone was, they were working from a thread and a memory. The agent picks up at any hour, in the club's voice, and opens the request properly. Answering is the easy half. The agent has to act, and it has to know who is asking.
What the agent should do
Four beats, in the order they happen.
Request
The member calls or sends a chat. The agent greets them by name, takes the request in plain conversation, and confirms the details back: the date, the party, the one thing that must be right. No menu. No spelling the name. The request is opened as a tracked task before the conversation ends.
Knowledge
Before it answers, the agent reads what the club already knows: the member's profile, past bookings, standing preferences, the vendor list, and the rules you wrote for what it may confirm on its own. A member who wanted a quiet table last time gets one this time without being asked.
Action
Inside the rules, the agent acts: a table at a preferred vendor, a car at the usual time, a change to an existing booking. It confirms with the member, on the call or in the chat, and writes the task to the board with an owner and a status. Outside the rules, it does not guess. It opens the task and says a coordinator will take it from here.
Handoff
Some requests belong with a person: a villa for a week, a complaint, a member who wants the manager. The agent hands off warm, with the transcript, the member's history, and a one-line summary attached. The coordinator opens the task knowing everything. The member never repeats themselves.
How we build it
First comes setup. We write the standard with your desk lead: greeting, voice, what the agent may confirm alone, and what always goes to a coordinator. We connect the member profiles, the vendor list, and the request board. You hear the agent on a test line and change what you do not like.
Next is the shadow run. The agent answers beside the desk. Coordinators read every transcript and correct it in a review queue. Every correction becomes a rule.
Then it takes the line and the chat. Monthly operation starts: monitoring, updates when vendors or rules change, and a report of what it handled and what it handed off.
Where we already work
Vluxure is a members-only luxury club. Webaroo built the member platform and runs the technology behind the club.
When it does not work
It does not work when most requests are one of a kind: then nearly every call becomes a task for a coordinator. And it does not work if nobody reads the transcripts in the first weeks, because a miss becomes a rule only when someone reviews it.
Where to start
If the phone and the chat are the first thing to fix, start with the Voice Agent. The same agent books visits for clinics in healthcare operations. If you are not sure, ask Roo, Webaroo's AI: Could an AI agent take member requests after hours?
Book 15 minutes with Connor