--- title: "Travel Agency Automation: Enquiry Intake, Supplier Coordination and Proposals | Kylon" description: "How a travel agency runs custom trip enquiries, supplier follow-up and proposal drafting in one Kylon room, with the advisor approving every client-facing document. Industry figures sourced and dated." url: "https://kylon.io/use-cases/travel-agency-operations" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>[Hospitality & travel](https://kylon.io/use-cases/topics/hospitality-travel)\>Travel Agencies: From Custom Trip Enquiry to a Priced Proposal the Same Day Use Case9 min read # Travel Agencies: From Custom Trip Enquiry to a Priced Proposal the Same Day Custom trips now arrive faster than an advisor can price them. This is how enquiry intake, supplier email and proposal drafting run in one Kylon room, with the advisor still setting the itinerary and the price. [Start in Kylon](https://app.kylon.io/launch/travel-agency-operations) [Book a call](https://cal.com/forms/5bd983bd-70e5-4afa-afd7-098b78cde6c3) Kylon TeamProduct September 21, 2026 The trip desk running: an enquiry read into fields, supplier quotes filling in, and the proposal held for your approval. Families, suppliers and prices are invented. Get this setup in your workspace The Travel Desk template builds this App with a full demo pipeline. Start in Kylon and your agent builds it in your workspace. [Start in Kylon](https://app.kylon.io/launch/travel-agency-operations) [See the Travel Desk template](https://kylon.io/apps/sales#travel-desk) Step by step ## From a trip enquiry to a priced proposal. One card per step. The agent prepares, and a named person decides. 1. 01 ### Read the enquiry into fields Today A web enquiry arrives as a paragraph of free text. In Kylon A trip record captures party, dates, budget band and what the brief leaves unsaid. Who decides The advisor decides whether to take the enquiry. 2. 02 ### Draft supplier requests Today The same dates and party are retyped into every supplier email. In Kylon Each supplier request is drafted from the trip record with the same dates, party and requirements. Who decides The advisor chooses the suppliers and sends each request. 3. 03 ### Compare the quotes Today Quotes come back over several days in different formats and threads. In Kylon Each reply is read onto the trip record, with unreadable lines flagged rather than guessed. Who decides The advisor makes the selection and sets the margin. 4. 04 ### Assemble the proposal Today Proposals are rebuilt by hand from quotes scattered across the inbox. In Kylon A proposal is drafted from the selected quotes and the approved itinerary, then held. Who decides The advisor checks every price and inclusion, then sends it. Set it up ## Start with the Travel Desk template. 1. 1\. Start in Kylon A new Room opens in your workspace with this prompt. 2. 2\. Connect what it lists Nothing to connect for the first run: it starts with demo data. 3. 3\. Give it your rules Your agent asks one at a time and writes them into the Room's guideline. Set-up prompt Download https://kylon.io/app-templates/travel-desk-template.zip and build me a travel agency trip desk from it. Unpack it, read README.md and TEMPLATE\_GUIDE.md, and follow them: create the App, provision its database, copy the source into the checkout, replace the placeholder app id and base URL, then push a draft and send me the link. Never run SQL by hand. The numbered files in db/migrations apply themselves in order to a new empty database and seed the demo trips, travellers, suppliers, quotes, proposals, bookings and departure checks, so the pipeline is full on the first open. Leave those rows in. Then stop. Do not import our real clients, do not connect our mailbox, calendar or payment accounts, and ask me before anything real goes in. [Start in Kylon](https://app.kylon.io/launch/travel-agency-operations) Rolling this out with a team? ## How it works in detail ## Custom is now the default, and custom does not scale by hand The trips getting booked are bigger, more expensive and more specific than they were a year ago. WeTravel's 2026 report, built on aggregated booking activity covering **1.3 million travelers across 800,000 bookings and 350,000 trips**, found average total trip prices up **59 percent year over year**, and **56 percent of operators reporting increased interest in private or custom trips**. Among travel advisors surveyed, **72 percent say custom or private trips are among their most requested offerings** ([WeTravel, Travel Trends Annual Report 2026](https://academy.wetravel.com/travel-trends-annual-report-2026), checked 21 September 2026). Group size moved in the same direction. In that dataset, bookings through travel agencies and advisors went from an average of **2.6 travelers per booking in 2025 to 3.0 in 2026** ([WeTravel, Travel Trends Annual Report 2026](https://academy.wetravel.com/travel-trends-annual-report-2026), checked 21 September 2026). More people on the booking means more preferences, more rooming permutations and more approvals before anyone pays. The demand is not the problem. ASTA's own figures put travel agency sales at **26 percent of the total travel market by 2026, expected to reach 141.3 billion dollars**, with **30 percent of advisors saying over half their clients are using an advisor for the first time** ([ASTA press kit](https://asta.org/common/Uploaded%20files/ASTA/ASTAPressKit.pdf), checked 21 September 2026). New clients ask more questions and need more written explanation. The constraint is the hours between the enquiry arriving and a priced itinerary landing in the client's inbox. ## One room per trip, one record for the pipeline The agency keeps a Kylon room for trip operations and a Database App behind it. Every enquiry becomes a record: party size, dates, budget band, destination, travel style, accessibility and dietary notes, the suppliers approached, what each one quoted, and where the proposal stands. The point is not the tracker. It is that the record is written in a form the agent and the advisor both read, so a supplier reply updates the trip rather than sitting in one person's inbox until Monday. - **Trip records** holding the brief, the party and the constraints in fields rather than prose - **Supplier quote lines** against each trip, with what was asked and what came back - **Room guidelines** that fix tone, what may be promised and what must be priced by a person - **One pipeline view** covering enquiry, quoting, proposal sent, deposit and departure The trip pipeline inside the room. Trips, suppliers and names are illustrative. ## What arrives, what gets prepared, who decides The rule on this page is the same one on every Kylon page: an agent prepares, a person commits. In travel that line matters more than usual, because the commitments are contractual and the margins are thin. | What arrives | What is prepared for you | What a person decides | | --- | --- | --- | | A web enquiry with a paragraph of free text | A structured trip record with party, dates, budget band and the three things the brief does not say | Whether to take the enquiry, and the questions to ask back | | The brief mentions a region you have run before | A first-draft shape of the trip, drawn from past trips in the record and current supplier notes | The actual itinerary, the pacing and the substitutions | | Six suppliers need the same availability request | Six drafted emails with the correct dates, party and special requirements in each | Which suppliers to approach, and the send | | Quotes come back over four days in four formats | One comparison against the trip record, with what each quote includes and what it leaves out | The selection and the margin | | The client is ready for a proposal | A drafted proposal built from the selected quotes and the itinerary you approved | Every price and inclusion before it is sent | | Ninety days before departure | A checklist position: deposits, passports, insurance, final rooming, outstanding balance | What to chase and what to escalate | The split between prepared work and committed work, set once in the room guidelines ## Supplier email, which is most of the job A custom trip with three hotels, two transfers, a guide and a restaurant block is seven conversations that all have to hold the same dates and the same party. Retyping those details seven times is how a party of six becomes a party of five in a confirmation nobody reads until arrival. In the room, the agent drafts each supplier request from the trip record, so the party, dates and requirements are the same in all seven. When a reply comes back, it reads the quote, writes the numbers onto the trip record, and flags what it could not read rather than inventing it. The advisor sees one comparison instead of seven threads. None of that sends without an advisor. Supplier relationships are the asset here, and a wrong request costs more than a slow one. Six supplier replies in six formats, read into one table. Suppliers, prices and dates are illustrative. ## See it in action The advisor names the pairing in one line and the proposal comes back assembled from the quotes on the record, held until she sends it. The client proposal drafted from the trip record and held for approval. Prices and names are illustrative. ## The proposal is the product, so the advisor writes the last version A proposal that reads like a template loses to one that reads like someone listened. The agent assembles the structure, the confirmed inclusions and the prices from the record. The advisor writes the paragraph that explains why this hotel and not the cheaper one two streets away. That division holds up in the survey data too. Among advisors, **66 percent say AI improves efficiency and creativity** in their business, positioning it as support for their work rather than a replacement for the judgement clients pay for ([WeTravel, Travel Trends Annual Report 2026](https://academy.wetravel.com/travel-trends-annual-report-2026), checked 21 September 2026). ## After the deposit, the part that gets forgotten Most agency software is good at the sale and thin after it. The window between deposit and departure is where the reputational damage happens: a passport that expires inside six months, a final rooming list nobody confirmed, a balance that goes unpaid until the supplier cancels. Because each trip record carries its own dated checklist, the room raises those items on their own schedule and drafts the client message that goes with each one. The advisor decides what is sent and what needs a phone call, which for a family trip leaving in three weeks is usually the phone call. ## What has to be connected Kylon is not a booking engine, a GDS or a reservation system. It sits across the tools the agency already runs and holds the coordination between the enquiry, the suppliers and the client. - **Email**, so supplier threads and client threads attach to the trip instead of a person - **A Database App** as the trip and quote record the team and its agents both read - **File storage** for quotes, vouchers and signed proposals - **Room guidelines** setting what may be promised, and what has to be priced by a person - **Scoped permissions**, so an agent works the trips it is assigned and nothing else If most of your enquiries arrive as inbound email, the intake pattern is the same one in [sales email as a managed pipeline](https://kylon.io/use-cases/sales-email-managed-pipeline). For the wider hospitality picture, see [hospitality and travel use cases](https://kylon.io/use-cases/topics/hospitality-travel). ## Where to start Take one destination you sell often. Put its trip fields and its supplier list into a Database App, connect the mailbox the enquiries already arrive in, and write the one rule that matters: an agent may draft a supplier request and a proposal, and an advisor sends both. > “The advisor still designs the trip. What changed is that the seventh supplier email now says the same thing as the first.” ## More Use Cases [View all](https://kylon.io/use-cases) [ Before: 1,000 to email today, Re: group rates?, call notes: who?, hot lead, unread, OOO reply x40. With Kylon: 12 meetings booked from one send. Scored 214 replies by intent. Workflow tools: Gmail, Outlook, Fathom. ### How a US Hospitality Firm Built an AI Sales Pipeline with Kylon Agents run 1,000-contact outreach, score replies and route leads. - ![HubSpot](https://kylon.io/v2/integrations/small/hubspot-com.webp) - ![Apollo](https://kylon.io/v2/integrations/apollo.png) - ![Cloudbeds](https://kylon.io/v2/integrations/small/cloudbeds-com.webp) - ![Fathom](https://kylon.io/v2/integrations/small/fathom-video.webp) - ![Calendly](https://kylon.io/v2/integrations/small/calendly-com.webp) - ![Gmail](https://kylon.io/v2/integrations/small/gmail.webp) - ![Outlook](https://kylon.io/v2/integrations/small/outlook.webp) - ![Slack](https://kylon.io/v2/integrations/small/slack-com.webp) ](https://kylon.io/use-cases/ai-sales-pipeline)[ Before: resume\_final2.pdf, Re: still keen?, interview: TBD, 47 unread applicants, which role is this?. With Kylon: 12 interviews booked this week. Scored 47 resumes vs roles. Workflow tools: Gmail, Outlook, Google Calendar. ### How an AI Startup Automated Talent Sourcing with Kylon Resumes parsed, candidates scored and outreach managed from one room. - ![Greenhouse](https://kylon.io/v2/integrations/small/greenhouse-io.webp) - ![LinkedIn](https://kylon.io/v2/integrations/small/linkedin-com.webp) - ![Airtable](https://kylon.io/v2/integrations/small/airtable-com.webp) - ![Google Calendar](https://kylon.io/v2/integrations/small/google-calendar.webp) - ![Gmail](https://kylon.io/v2/integrations/small/gmail.webp) - ![Outlook](https://kylon.io/v2/integrations/small/outlook.webp) - ![Slack](https://kylon.io/v2/integrations/small/slack-com.webp) ](https://kylon.io/use-cases/talent-sourcing)