Client Trip Requests

Your travelers can now tell you what they want to do, right from their portal. They pick a day, pick what kind of thing it is, and write a line. It lands on the trip for you, and one click puts it on the itinerary.

Your clients cannot edit the itinerary, and they never will. A request is a suggestion sitting in your inbox. Nothing a traveler sends changes a single thing on their plan until you add it.

What it replaces: the phone call you took in the car, the text you meant to write down, the four-message email thread that starts "one more thing".

What Travelers See

Open a client portal, open a trip, and there is a Requests tab. The card asks a question rather than showing a blank box:

Which places matter most to you? A day you'd like somewhere specific, a restaurant you'd love, something you don't want to miss.

Underneath, they choose:

"Any day" is a real answer. "Fireworks from the beach at least once" belongs to the trip, not to a Tuesday, and the picker does not force them to invent a date.

If the trip has no dates yet, the day picker is hidden entirely and every request comes in as "any day". The card still works — travelers can send requests before you have built anything.

What You See

A banner appears at the top of the trip, visible from any tab:

✦ 3 requests from your travelers on this trip. [Review]

Review takes you to From your travelers on the Overview tab, where each request shows the type, the day they asked for, their exact words, and who sent it. Three things you can do with each one:

Add

Pick a day (it defaults to the day they asked for) and click Add.

• A park day request goes straight onto the Park Board. If we can tell which park they meant, the button says so — "Adds Magic Kingdom Park to the park board." You are confirming a reading, not trusting a guess.
• Everything else becomes an itinerary block on that day, with their exact wording kept as traveler notes. We never paraphrase — "the girls want the castle show" is the part that matters.

If we cannot tell which park they meant, or the request is not a park day, it becomes an ordinary block and you can retitle it however you like.

Note it

For a request you cannot schedule. The traveler's card flips to Noted, so they know you saw it.

Use this instead of dismissing. An advisor who dismisses a request tells the traveler nothing, and a traveler who hears nothing asks again — usually somewhere you are less likely to see it.

Dismiss

Takes it off your list silently. The traveler is not told.

What Travelers See Back

Their card shows the status of everything they sent:

If you schedule it on a different day than they asked for, their card says so — "scheduled Sep 5" — so a moved request reads as a decision rather than a miss.

Dismissed requests disappear from their card without a status.

Notifications

Every request rings the bell and emails whoever the trip is assigned to (or every owner and admin if it is unassigned). A family sending three requests in one sitting gets you three notifications, not one.

Turning It Off

Requests ride on the same setting as portal messages. If your agency keeps client communication on email, turn off Show Messages in your portal settings and the Requests tab goes with it.

Related

• Client Portal
• Itinerary Builder
• Disney & Universal HQ