Confirm Dietary Requests With the Supplier Before Booking

A traveler mentions a dietary restriction almost as a side note, and it is tempting to treat it as handled once you write it down. But a note in a booking file is not a guarantee that a kitchen on a river cruise, a beach resort, or a small group tour can actually act on it. Your job is to capture what the traveler needs in specific terms, then get a real answer from the supplier before you tell anyone the trip is set.

Why this conversation goes wrong

Advisors want to reassure the traveler quickly, so they say things like "I'll make sure they take care of you" before checking with anyone. That sentence sounds caring, but it is a promise you cannot keep on your own. A resort buffet, a small cruise ship, and a rural tour each run different kitchens, with different notice periods, different suppliers, and different limits on what they can prepare safely. A hotel restaurant might handle a dairy allergy without much notice, while a five day trek through a remote area might need two weeks to source ingredients, or might not manage it at all. When you skip the supplier check and go straight from the traveler's request to your own reassurance, you turn their dietary need into your liability. If the meal falls short once the trip starts, the traveler remembers what you told them, not what the supplier actually agreed to.

How to prepare before you ask

Before you bring up the supplier, get the request right from the traveler. Ask which specific foods or ingredients they need to avoid, not just a general category. Gluten free can mean strict avoidance of cross contact, or it can mean skipping obvious wheat products, and those two versions call for very different kitchen handling. Ask whether the concern applies to every meal on the trip or mainly to certain settings, like shore excursions or packed lunches, where kitchens have less control. Ask which parts of the itinerary matter most to the traveler, since a missed breakfast is a different problem than a missed dinner on the one night they were most looking forward to.

Do not ask for medical details or a diagnosis. You do not need to know why someone avoids a food, only what they need you to communicate on their behalf. Write the request in the traveler's own words and read it back so you both agree on what you are about to send. Then find out who actually answers dietary questions for that supplier. On a cruise it might be a shore side reservations team rather than the ship itself. On a small tour it might be the local operator or guide. Identify that contact before you promise a timeline for an answer.

What to say

Once you have the request in clear terms, tell the traveler what you are going to do and what you are not going to do yet. Traveler Marcus says, "I need dairy free meals for the whole safari, every day. Can you just make sure the camps handle it?" Advisor Priya says, "I'll send that request to the camp operator today, using the words you just gave me. Before I do, are there other ingredients beyond dairy you want me to flag, or any meals you're most concerned about?" Marcus says the sundowner snacks worry him most, since he has seen cheese trays at other trips. Priya replies, "Good to know. I'll ask the operator how each camp handles dairy free requests, including the sundowner service, and how much notice they need. I'll bring you their answer in writing before we book anything."

Notice what Priya does not say. She does not say the camps will handle it. She does not guess at a timeline before she has one from the supplier. She tells Marcus exactly what she is sending, invites him to add detail, and commits to bringing back the supplier's own words. When the operator responds, read the answer to the traveler plainly, including any limits. If the operator says every camp can accommodate dairy free requests except one remote outpost, say that directly and let Marcus decide whether that outpost matters enough to change the itinerary. That decision belongs to him, once he has real information in front of him.

Mistakes to avoid

The most common mistake is offering assurance without confirmation. An advisor hears the request, feels pressure to sound helpful, and says the meal will be handled before anyone at the supplier has agreed to anything. A second mistake is collecting a vague version of the request. If you write down gluten free and stop there, the supplier has to guess how strict to be, and you have no way to check their answer against what the traveler actually needs. A third mistake is asking for more than you need. A traveler does not owe you a diagnosis, and asking for one can make a basic request feel like something they have to justify.

A fourth mistake is letting the supplier's response sit in your inbox instead of attaching it to the itinerary. If the confirmation lives only in an email you read once, nobody can check it later, and the traveler has no record to point to if the meal falls short. Keep the supplier's written answer with the booking, along with the name of the person who gave it. If a problem comes up during the trip, that record shows what was actually promised, not just what everyone hoped would happen.

How to practice and score this conversation

This exchange rewards a specific order of operations. Ask before you promise. Confirm before you commit. Report the supplier's answer plainly, including any limits, instead of softening it for the traveler's comfort. A manager reviewing a recorded or roleplayed version of this conversation should check three things. Did the advisor collect specific, usable detail from the traveler instead of a vague label. Did the advisor avoid promising a result before checking with the supplier. Did the advisor bring the supplier's actual response back to the traveler, limits included, rather than smoothing it over.

DealSpeak lets advisors run this exact scenario against an AI traveler, with different pressure points each time, a traveler who pushes for an immediate yes, one who has had a bad experience before, one who adds a new detail halfway through the conversation. The scoring flags language that sounds like a guarantee and rewards advisors who ask precise questions and report supplier answers without editorializing. You can find more scenarios like this one among the Hospitality and Travel practice conversationsincluding Handle a Booking Inquiry With Different Arrival Dates for another case where the details you gather up front decide whether the trip goes smoothly.

Keep the record straight

A dietary request is not solved when you write it down. It is solved when the supplier confirms what they can actually do and the traveler sees that confirmation before committing to the trip. Get the specific request, find the right contact, and pass along the real answer, even when it includes a limit. That habit protects the traveler's trip and your own credibility later, the same way a clear checkpoint helps in a situation like the one described in Recover a Digital Key Access Failure With a Clear Checkpoint.