Building relationships with executive assistants
Build useful relationships with executive assistants through clear briefs, concise options, defined approvals and a Nowah-supported research workflow.

Build relationships with executive assistants (EAs) by understanding how they organise travel requests and providing concise options they can review or forward. Agree how decisions are approved before any booking or payment proceeds. For the travel-planning and research component, Nowah fits this job well. You still deliver recommendations and confirmations using your agency’s approved client-facing tools and processes.
What EAs are optimizing for (translate this into your deliverable)
Ask each EA what a useful travel service looks like in their organisation. Their needs may include calendar fit, a preferred forwarding format, approval records or cover when another colleague is away. Use those answers rather than assuming every assistant works to the same priorities.
Use Nowah flight and hotel research to build options around the executive's fixed commitments. The corporate needs assessment supplies the right constraints.
Design your service to demonstrate:
- Forwardable clarity: your message can be sent to the executive unchanged.
- Preference accuracy: cabin, airline constraints, connection tolerance, hotel work setup, quiet requirements.
- Decision containment: a small set of options with explicit trade-offs.
- Process control: what happens next, who approves, and what is held until approval.
- Contingency readiness: a calm backup path, not a scramble.
A strong relationship often comes down to whether you consistently deliver these five things, even when the request is incomplete.
A trust path that doesn’t feel like “selling”
EAs are selective about adding new partners. Instead of trying to win a large commitment up front, aim for small “safe yeses” that are easy to authorize.
- Step 1: permission to send a one-page example of your options format (use fictional data).
- Step 2: a short preferences/process call (10–15 minutes).
- Step 3: one contained first request (one executive, one trip).
- Step 4: a quick post-trip preference update to reduce effort next time.
Scripts that EAs can act on (copy/paste)
Use plain language. Promise a process outcome (clarity, control), not prices.
Initial outreach email
Subject: Executive travel support—forwardable options + approvals
Hi [EA Name],
I support executive assistants by providing decision-ready travel options (typically 2 flight paths and 2 hotel options) with clear trade-offs and an explicit approval step before anything is paid.
If helpful, I can send a one-page example of the format so you can see whether it fits your workflow.
Open to a brief call next week?
Best, [Your Name] [Agency] [Phone]
Follow-up (3–5 business days later)
Hi [EA Name],
Should I send the one-page example format, or is someone else the best contact for executive travel support?
Thanks, [Your Name]
Call opener (30 seconds)
“Thanks for the time. My goal is to make requests easier: you send constraints, I send forwardable options with a clear approval step. Can I confirm how you prefer decisions packaged and who gives final approval?”
One intake template: the EA Travel Brief
Most EA frustration comes from repeated clarification. Solve that with a single brief template that’s quick to complete but prevents predictable omissions.
Translate the EA's meeting times into a Nowah day plan before choosing hotel areas. Follow the business-hotel selection guide to investigate location suitability.
Collect and store real client data only through your agency’s approved data-handling process.
Executive Travel Brief (EA version)
A) Trip objective + timing
- Purpose (meeting / event / site visit):
- Must-arrive-by (local time):
- Must-depart-after (local time):
- Date flexibility (none / +/- 1 day / other):
B) Flight rules
- Origin airport(s) acceptable:
- Destination airport(s) acceptable:
- Cabin:
- Preferred airlines/alliances:
- Max connections (0/1/2):
- Red lines (e.g., no overnight layovers):
C) Hotel rules
- Location priority (walkable to venue vs short ride OK):
- Work needs (quiet room, desk, lighting):
- Brand/style preferences (if any):
- Accessibility needs (if any):
D) Ground + connectivity
- Transfers needed? (arrival/departure):
- In-city transport preference:
- eSIM needed? (Y/N; device type):
E) Approvals + payment sequence
- Who approves selection?
- Preferred format to forward internally?
- Confirm: no payment until written approval is received (Y/N)
Use this template to agree the information and approval sequence both sides need. Review it after the first request and remove fields that do not serve the actual process.
The “2×2” forwardable options format (your core deliverable)
Standard: two flight options + two hotel options.
Include only what drives a decision:
- one-line rationale
- the key trade-off
- the exact approval reply you need
Copyable structure
Trip summary: [route], [dates], must-arrive-by [time], cabin [x], hotel area requirement [x]
Flight A (recommended)
- Routing + local times:
- Why it’s recommended:
- Trade-off:
Flight B (backup)
- Routing + local times:
- Why it’s a viable backup:
- Trade-off:
Hotel 1 (recommended)
- Location fit:
- Work/quiet fit (as advertised/available):
- Notes: supplier availability and terms apply; client approval required before payment
Hotel 2 (backup)
- Location fit:
- Work/quiet fit:
Next step: Confirm the preferred options and the person authorised to approve. Collect required traveller details through the agreed secure process, then review the actual offers and conditions before purchase.
This wording protects the EA: it’s clear what you need, and it reinforces approval control.
Worked hypothetical example: turning a vague request into a decision
Scenario (hypothetical): An EA writes: “Need our executive in a major European city for two days next month. Business class preferred. Quiet hotel room with a proper desk near the conference venue. Options by tomorrow morning.”
Compare the sample itineraries in Nowah, then present the schedule differences in the forwardable summary. The flight comparison sheet keeps those differences visible.
1) Ask only three clarifying questions
Your goal is to unlock planning with minimal friction:
1) “What is the must-arrive-by local time on Day 1?” 2) “Are alternate airports acceptable on either end? If yes, which?” 3) “Does ‘near the venue’ mean walkable, or is a short car ride acceptable?”
If the EA can’t answer immediately, proceed with reasonable assumptions—but label them as assumptions.
2) Use Nowah to produce structured candidates
Use Nowah’s conversational trip research, flight search and hotel research to investigate candidates against the confirmed brief. If the executive has multiple stops, use Nowah’s multi-city flight search.
Copyable Nowah planning prompt (fictional, anonymised)
Paste into Nowah:
“Help research a fictional executive trip from New York to Madrid using the future dates I provide next. The traveller prefers business class, at most one connection and arrival in time for the commitment I specify. I will provide the venue address before hotel research. Compare relevant flight and hotel options, explaining the information shown and any missing details about room work facilities or location. Draft an outline of the arrival and work days. Identify assumptions to confirm rather than inventing a venue or promising a quiet room.”
3) What you must verify before you send options
Treat any generated draft as a starting point that needs professional checks.
Confirm:
- Time logic: local times, date changes, and arrival targets make sense.
- Connection risk: layover times are reasonable; backup routing exists.
- Airport fit: alternates are acceptable (or clearly marked as assumptions).
- Hotel location: neighborhood/area matches the venue requirement.
- Work needs: room type notes and property policies align as much as possible.
Check the actual offer and relevant property information. A request for a desk or a quiet room is not confirmation that a particular room meets it.
4) Send the 2×2 in a forwardable table
In your agency’s normal tools (email/doc), send:
Category | Recommended | Backup |
|---|---|---|
Flight | Routing + local times | Routing + local times |
Why | One-line rationale | One-line rationale |
Hotel | Property + area | Property + area |
Why | Location + work-fit | Location + work-fit |
To proceed | “Approve Flight __ + Hotel __” | Same |
This is where the relationship is built: the EA can forward, the executive can choose, and you can proceed cleanly.
Agree who can approve each stage
EAs need to know you will not create exposure by acting without authorization.
A practical approval sequence to adopt:
1) Options delivered (2×2) with assumptions labeled. 2) Written selection approval received (flight + hotel choice). 3) Pre-payment reconfirmation (availability, names-as-on-ID, key terms surfaced). 4) Payment executed only after approval.
Always reflect that supplier availability and terms govern bookings, changes, and refunds, and ensure the client approves before payment.
Where Nowah fits in your EA relationship workflow
Nowah supports the planning work that sits behind your forwardable 2×2.
Use Nowah to:
- convert an EA email into structured constraints via conversational trip research
- test routing patterns with flight search (one-way/round-trip/multi-city)
- shortlist hotels using hotel search and booking
- sketch a day itinerary and validate pace using map/timeline views
- add travel eSIM purchase planning when international connectivity matters
Then you curate and communicate using your agency’s established client-facing materials. For membership terms, check Nowah /pricing for current conditions (avoid relying on old notes).
Your internal QA artifact: the EA Relationship Rubric
After each EA request, score yourself. This is how you systematically improve without “trying harder.”
Score 1–5.
Dimension | 1 | 3 | 5 |
|---|---|---|---|
Forwardability | Needs rewriting | Mostly clear | Forwardable as-is |
Decision containment | Too many options | Some focus | Tight 2×2 with trade-offs |
Preference fit | Generic | Partly tailored | Clearly preference-led |
Approval control | Unclear | Mentioned once | Explicit at the right steps |
Contingency | None | Some | Backup ready and sensible |
Use the scores to identify a discussion point with the EA, not as a claimed service-performance benchmark. Their feedback is more useful than a score awarded without consultation.
Review the working relationship after the first trip
Ask the EA which parts of the brief and options format were useful, which required rewriting and where they needed another update. Agree any changes before the next request. A repeat relationship should reflect that feedback rather than relying on an unchanged template.
Agree realistic response times, cover arrangements and how urgent requests should be escalated. Do not promise continuous support unless your agency can deliver it. Keep those service commitments in the agency’s own process, alongside the travel research you prepare in Nowah. Start planning with Nowah at Open Nowah, and review the supported capabilities at Nowah /features.




