From enquiry to ticket: a day on an agency desk

A realistic day at a small travel agency, from live chat enquiry to approved itinerary and payment, showing how the Trip Planner and operator console fit in.

View full page

One invented Tuesday at a small agency, told hour by hour, showing where the Trip Planner, the storefront chat and the operator console fit in. Only the parts we can stand behind are in the software.

By Traviology · Published 2026-11-14

What follows is made up. Dana, the agency and the client are invented, and the day is a composite of the days we hear about from agents. The software described is real, and we've kept to what it does. Where it stops, we say so.

07:50: the chat lights up

A message arrives through the live chat on the agency's own storefront. It lands in the agent inbox, which is where Dana is looking. If nobody picks up, TravioBot is the fallback. This morning she does.

The client wants eight days in one country, two cities, with a train between them and one big day out. No dates yet, a rough budget, two adults. Dana asks four questions, gets three answers and says she'll send something by the afternoon.

08:30: a rough shape on a map

She opens the Trip Planner and places the stops on the live Google Map: city one, city two, the day-trip town in between. Seeing the route is half the conversation, because clients often don't realise how much they're asking from a Tuesday.

Then she pairs things to each leg: flights, a hotel for each city, the train, a transfer from the airport and a tour for the big day out. As she adds each piece, the running trip total updates, so she can tell the client where the budget stands without a calculator.

The markup and currency rules are the same ones the rest of the storefront uses, so she's not keeping a second set for itineraries.

10:40: a local hotel

For city two, Dana has a small guesthouse she contracts with. She's already published it as local inventory, seasons and rates included, so it sits in the results right beside the hotels that come from the supplier API. She takes it for two nights and picks a network hotel for the rest. Flights and trains are different: they come only from the API. Nothing to publish there. That's fine.

11:15: interrupted

A phone call about a different client takes forty minutes. Drafts are resumable, so she saves, deals with the call and comes back to the same trip. Nothing is lost.

14:30: the itinerary goes out

She reads the trip through once, as the client would, and cuts the second day, which is too packed. Then she sends it off for the client's approval. It's branded, it sits on the agency's own domain, and it's in the agency's colours.

The software doesn't do the judging. It puts the pieces together. Deciding that the guesthouse suits this couple, and that a gentler second day will make them happier, is Dana's job.

16:00: approved, and paid

The client approves and asks about paying. Card payments run through Stripe Checkout.

17:15: the console

Before closing she opens the operator console, which covers support, content, markup, clients and bookings. She checks the booking and the client's record, and fixes a typo in the storefront's welcome text. Site content is editable per brand without a redeploy, so the fix is hers to make, not a developer's.

What the software didn't do

It didn't call the client. It didn't tell Dana the guesthouse was the right choice, and it can't make a flight cheaper. What it did was remove the copying between tabs, so the afternoon went on the trip instead of the paperwork.

If you'd like to see the planner on your own domain, the Trip Planner page explains how it works, and a live demo is open at try.traviology.com.

Sources

This is an invented story based on Traviology's own product facts, so it has no external sources. Product details are from the Traviology website, checked October 2026.