Holiday Wish, a feature of Travels

Every request in one list, and none of them forgotten

Requests from your form and your chat land in the same place, complete. Each has an owner, a status and a clock that shows how long the traveller has been waiting, so the next one to answer is never a guess.

  • Form and chat in one list
  • An owner for every request
  • From request to offer in one click
How it works

From a new request to a closed one

Holiday Wish is the list your agents work from. A request is never just an email in somebody’s mailbox.

  1. 01

    It arrives

    A request from the form or the chat appears at the top of the list, and your agency gets an email with a Create offer button.

    • Form
    • Chat
  2. 02

    Someone takes it

    An agent takes the request or is given it. Everyone can see whose it is.

    • Take it
    • Assign it
  3. 03

    It is answered

    Create offer opens the search filled in from the request. Or let an offer be prepared automatically.

    • Create offer
    • Generate offer
  4. 04

    It is closed

    The status follows what happens: offer sent, sold, or rejected with the reason.

    • Offer sent
    • Sold
The request

One request, and the whole story with it

Open a request and everything about it is on one page: what the traveller asked for, what was said, what was offered and what they did next.

  • What the traveller asked for, field by field, with their own comment
  • The chat conversation, and a box to write back
  • The hotels the traveller liked in the chat
  • Every offer made for the request, and what the client did with it
  • The client’s record, matched by email or phone
What it does

Built so that no request waits unseen

The list answers three questions at a glance: what is new, whose is it, and who has been waiting longest.

One list for every channel

  • Form, chat wizard, AI assistant and live chat create the same request.
  • New requests appear at the top without reloading the page.
  • A badge in the menu shows what arrived since you last looked.
  • Search by code, email or phone, and filter by any column.

An owner for every request

  • Assign a request to an agent, or take it yourself.
  • Take over from a colleague, or make the offer and leave it theirs.
  • Return a request to the pool.
  • Filter to your own requests or to the unassigned ones.

A clock on every request

  • Waiting time is on every row and turns red after two hours.
  • See whether the notification was opened, the request viewed and the offer shared.
  • Median time to first response, on top of the list.

Statuses that follow the work

  • New, contacted, offer sent, sold, rejected.
  • Offer sent is set when the offer goes out, not by hand.
  • A rejected request records the reason.
  • A count on each status, and one click to filter by it.

The conversation stays with the request

  • The traveller’s chat with the assistant is kept as history.
  • Write back from the request; the reply appears in the chat within seconds.
  • A traveller who has left gets the reply by email.
  • A counter in the header for chats that are waiting.

From request to offer in one click

  • Create offer opens the search filled in from the request.
  • Generate offer prepares one automatically.
  • A request nobody has answered can get an offer by itself.
  • Agents who are out of office are skipped.

What the list tells you

  • In queue, new today, unassigned and without an offer, at a glance.
  • Requests that depart within 30 days.
  • Sold in the last 30 days, against the requests received.
FAQ

Questions agencies ask

Overview

Where do the requests come from?

From the client request form and the chat on your website. Both create the same request, so your agents work one list whatever the traveller used.

How does an agent know a new request has arrived?

By email, with buttons to view the request or to create an offer, and by a badge in the menu. A traveller waiting in the chat also raises a counter in the header, with a sound and a browser notification.

Can two agents work on the same request?

A request has one owner. A colleague can take it over, or make an offer for it and leave the owner as it is.

What happens to a request nobody answers?

It stays in the list with its waiting time in red. The system can also prepare an offer for it automatically, as a draft for an agent to check or sent straight to the traveller.

Do I need the travels system for it?

Yes. A request asks for a tour operator holiday, and answering it means searching those packages and sending an offer from them.

For travel businesses

Tell us how you work. We’ll show you where Waavo fits.

Every agency, tour operator and travel startup runs differently. Answer a short inquiry about your business and daily challenges, and a Waavo specialist prepares personal recommendations for a free call.

  • 7 questions
  • About 2 minutes
  • No obligation
What we’ll ask about
  1. Your businessType of company, team size and main market
  2. What you sellFlights, hotels, packages, tours or something else
  3. How you sell todayOffice, phone, website or supplier portals
  4. Your challengesIn your own words, what takes the most time