Check the Approved Process Before Booking for Another Traveler

A caller says they are booking on behalf of someone else, gives you a name, a loyalty number, and asks you to send the confirmation to their own email address instead. It sounds routine. It happens on almost every shift you work. But the moment you add someone else's loyalty details to a reservation without checking who is actually authorized to touch that account, you have created a problem that lands back on you, on the property, and on the traveler whose information just moved without their knowledge.

Why this conversation goes wrong

Most agents do not get this wrong because they are careless. They get it wrong because the caller sounds legitimate, is often in a hurry, and frames the request as something small. An executive assistant booking for a director. A spouse booking for a partner. A colleague covering for someone who is traveling already. None of that is suspicious on its face, and treating every caller like a suspect is not the answer either.

The real problem is ambiguity. The caller might be authorized to book a new stay but not to view or change an existing reservation. They might be allowed to use a company card but not to receive loyalty account details. They might be a family member who books every trip for a relative, right up until the one time they are not actually authorized for that particular account. When you skip the verification step because the conversation feels friendly and normal, you are guessing at authorization instead of confirming it, and a guess in the reservation record does not protect anyone.

How to prepare before you pick up the call

Know your property's approved process before the call starts, not while the caller is waiting on the line. Most reservations systems separate a few things that agents tend to blur together under time pressure. There is the traveler who will actually stay in the room. There is the caller who is on the phone right now. There is the payment method being used. And there is the account or loyalty profile tied to the stay. Each of those can belong to a different person, and each one carries a different authorization requirement.

Before you touch loyalty details or discuss anything about an existing reservation, confirm whether the request is a new booking or a change to one already on file. A new booking with a company card is often straightforward. A change to an existing reservation, a request to view stay history, or a request to add someone as a contact on another traveler's account usually requires a higher level of verification. If you do not know where that line sits at your property, ask your manager to walk through it before your next shift, not during a live call.

What to say when someone books for another traveler

Here is how that conversation can go. A caller named Priya says, "I need to book a stay for my director, Marcus Ellison. Use his loyalty number and send the confirmation to me."

The agent responds, "I can help look at booking options right now. Before I add any loyalty details or discuss anything on Marcus's existing account, I need to follow our authorization process for his profile. Are you setting up a new stay, or making a change to a reservation already in his name?"

Priya answers, "It's a new stay, and I have the company card for the payment."

The agent says, "Thank you, that helps. I can take the travel dates and guest name now, then check what our process allows for using that card and for adding a contact to the reservation. I will only add anything to his account once the required authorization is confirmed on our end."

Priya asks, "Can I get the itinerary sent to my email?"

The agent replies, "Where the confirmation goes depends on the authorization level and what our system accepts as a valid contact for his account. I will tell you exactly what the process allows before we finish booking, so nothing goes out that shouldn't."

Notice what the agent never does here. The agent never says no outright, and never accuses Priya of anything. The agent also never promises an outcome before checking the process. The agent narrows the request down to what can move forward immediately, the new stay and the dates, and holds the account level details until authorization is confirmed.

Mistakes to avoid

A few patterns show up again and again in these calls, and each one creates real exposure.

1. Adding a loyalty number or account details to a reservation because the caller already knows them. Knowing a number is not the same as being authorized to use it, and callers sometimes have information through entirely innocent means that still does not grant them account access.

2. Assuming a relationship implies authorization. A spouse, an assistant, or a direct report might be fully authorized, or might not be, and the only way to know is to check the process, not to guess based on how the caller describes the relationship.

3. Sending confirmation details to whichever email address is easiest in the moment. The delivery destination is part of what your process controls, not a convenience you decide on the fly.

4. Explaining the verification step in a way that sounds like an accusation. Callers with legitimate authority get frustrated fast if they feel suspected of something. State the process plainly, as a standard step you take for every caller, and keep your tone the same whether you believe the caller instantly or not.

This is the same discipline that shows up in other reservations conversations where the process, not your instinct, has to lead. If you want to see how that plays out in a different context, look at how an agent separates booking pace from a forecast in an owner review or explains an unusual cancellation pattern with clear data limits. The pattern repeats. State what the data or process actually supports, and hold back anything it does not.

How to practice and score this conversation

This kind of call is hard to get right the first time you hit it live, because the pressure to just be helpful is strong and the authorization rules can feel like they are slowing everyone down. Practice it before it happens with a real traveler on the line.

Roleplay two versions of the caller. One is an executive assistant who books frequently and is fully authorized, so the agent should move quickly once that is confirmed. The other is a family member who assumes access that has not actually been granted, so the agent has to hold the line without sounding accusatory. A manager listening in should score whether the agent asked what task was actually requested before doing anything, whether the agent named the approved process out loud instead of skipping it, and whether the agent avoided revealing or assigning account access before verification was complete.

DealSpeak lets you run both versions of this call against an AI counterpart and get scored on exactly those points, so you can find the gaps in your phrasing before a real caller finds them for you. The Hospitality and Travel practice conversations hub has more scenarios built around the same kind of judgment call, where the right answer depends on process, not instinct.

Keep your notes on traveler name, caller identity, and payment method separate every time, and let the approved process decide what moves forward. Do that consistently and this conversation stops being a source of risk and just becomes a routine part of the job. The caller gets an answer, the traveler stays protected, and you are covered either way.

When you have this one down, read Separate Booking Pace From a Forecast in an Owner Review next.