Travel Assistant
How the Ghloria assistant supports proposal work, operations, and day-to-day agency decisions.
Travel Assistant
The travel assistant is a chat experience inside Ghloria for operational support. It is designed to help agency teams think through proposal work, trip planning, and daily decisions without making AI the whole product experience.
The assistant is available from /assistant. The Portuguese path /assistente redirects to the same assistant page.
What The Assistant Does
The assistant accepts free-form messages and streams the response back into the chat. The app keeps the current conversation thread while the user remains on the page, so follow-up questions can continue with context from the same exchange.
Use it for support tasks such as:
- Drafting or refining proposal ideas.
- Comparing destination options for a client profile.
- Asking for operational guidance while building a trip.
- Turning rough travel requirements into a clearer plan.
- Exploring itinerary direction before entering structured proposal data.
Example Prompts
These examples show the kinds of requests the assistant handles well:
Destination research
"My client wants a 10-day honeymoon in Southeast Asia with a beach finish. They like boutique hotels and dislike large resorts. What three destination combinations would you recommend?"
Itinerary structure
"Build a rough day-by-day structure for a 7-day Japan trip starting in Tokyo, ending in Kyoto, with one night in Hakone. Include main activity categories for each day."
Comparing options
"A family of 4 with two children aged 8 and 12 is asking between Maldives and Mauritius for August. What are the practical differences in terms of flights from Lisbon, family resort availability, and value?"
Proposal copy
"Write a short destination introduction paragraph for the Azores — Pico Island — for a proposal targeting active travelers who enjoy hiking and whale watching."
Operational questions
"What are the typical lead times I should communicate to a client booking a safari in Kenya for January, and what documents do Portuguese nationals need?"
Budget sense-check
"Is €4,500 per person realistic for 10 nights in Bali including flights from Lisbon, mid-range boutique hotels, and daily breakfast?"
How Messages Are Handled
Write The Request
Enter a message in the assistant input. Messages are limited to 8,000 characters, which keeps the request focused and avoids sending oversized context.
Ghloria Opens Or Continues A Thread
If the page already has an active assistant thread, the next message is sent with that thread. Otherwise, Ghloria starts a new conversation.
The Response Streams Back
The assistant response is delivered as a server-sent event stream. Ghloria renders the response progressively so the user can start reading before the full answer is complete.
Reliability And Limits
The assistant route validates the request before it reaches the AI service. Empty messages are rejected, long messages are capped, and upstream errors are converted into user-facing error states.
If the assistant cannot respond, the chat keeps the user's previous messages and shows an error instead of creating a false response. This keeps the workflow transparent and helps agents retry or adjust the prompt.
What the Assistant Does Not Do
The assistant does not have access to your workspace data — it cannot read your existing proposals, client records, supplier contracts, or pricing history. It also does not make live bookings, check real-time availability, or retrieve current pricing from GDS or supplier systems.
| Not supported | Use instead |
|---|---|
| Access your existing proposals or clients | Open the record directly in Ghloria |
| Real-time pricing or availability | Contact the supplier or use your GDS |
| Direct booking or reservation | Your existing booking workflow |
| Guaranteed factual accuracy | Verify any specific claims before presenting to a client |
The assistant can produce plausible-sounding text that contains errors — especially on specific dates, pricing, visa requirements, or recent news about destinations. Always review output before including it in a client-facing proposal.
Using Assistant Output in a Proposal
When the assistant produces useful text — a destination description, itinerary structure, or inclusion list — copy it into the relevant proposal block:
- In the proposal editor, open the block where the content belongs (a Text block, Itinerary Day block, or similar).
- Paste the assistant's output and edit it to match the specifics of the offer.
- Verify any factual claims — dates, operating hours, entry requirements — before the proposal is sent.
The assistant does not write directly into proposals. All content moves through your review before it enters the structured record.
Position In The Workflow
The assistant is best understood as an enabling layer for agency operations. It can help an agent reason, draft, and decide faster, but structured proposal records still belong in the proposal editor, client records, destination fields, pricing, and delivery workflows.
Use the assistant to accelerate thinking. Use the rest of Ghloria to manage the agency workflow with structure and control.