You can ask your charter broker to use WingStack while keeping the relationship you already trust. Start by asking for one shared place to follow the itinerary, raise questions and see what changed. A specific request is easier for a broker to evaluate than a broad request to adopt another app. This guide gives you a practical way to introduce WingStack while keeping your existing relationship at the center.
Start with the coordination problem
Describe a recent handoff that took more effort than it should have. Perhaps an updated itinerary disappeared in an email chain, two assistants worked from different departure times, or the traveler asked a question that only the broker could answer. Explain the effect on your work without presenting it as a failure by the broker.
Choose one outcome for the first conversation: a current itinerary, a visible place for requests, or a clear way to confirm changes. Your broker can then show whether WingStack fits that workflow. Avoid starting with a long feature list; the goal is to make the next trip easier for both teams.
Send a concrete request
Adapt this message to your relationship. It asks for a discussion and a limited trial, rather than assuming the broker has already agreed to change their process.
Hi [broker name], Could we look at using WingStack for one upcoming trip? We would like one place to follow the itinerary, keep trip questions together and see confirmed updates. We want to keep working with your team. The goal is to reduce the back-and-forth around [specific coordination issue]. Would you be open to a joint walkthrough using [trip or example itinerary]? We can agree on who updates the trip, how changes are confirmed and what our travelers receive before we start. Here is the platform: https://wingstack.ai Thanks, [your name]
Agree on a one-trip pilot
Pick a straightforward itinerary with enough lead time to learn the workflow. Ask the broker which parts they will manage in WingStack and which remain in their existing process. A pilot does not require moving every historical document or changing every supplier at once.
- Choose one planner and one broker contact to own the setup.
- Confirm which travelers and assistants should have access before inviting anyone.
- Agree where requests are submitted and how a requested change becomes a confirmed update.
- Keep a direct contact method for time-sensitive questions during travel.
- Set a short review after the trip to decide whether to continue.
Judge the result by the handoffs
Review a few observable questions together. Could you find the current itinerary without searching your inbox? Could the broker tell which request was still open? Did the traveler know whom to contact? Record the friction that remains instead of treating account creation as success.
Ask for a joint demo if either team is unsure about access, signing, invoicing or the passenger experience. Review current pricing together rather than assuming every trip-related charge is a software fee. WingStack supports the coordination; your broker and operator still confirm the arrangements and flight details. The strongest reason to continue is a workflow both teams can explain and use.
Explore the product
Explore the referenced resources and related WingStack guides. Confirm your trip details and available services with your provider.