/loop in practiceTours and activities

One platform for every channel you sell on.

A solution developed through the /loop model for operators of tours, activities and experiences who sell through a channel manager and on online travel agencies. We connect to the systems you already use, starting in read-only, and bring bookings, departures, sales and reviews into one platform, with reports that run on their own.

Built on Bókun, which has an official MCP server. A channel manager is the program that gathers bookings from every portal. Using another system? Type it in our tool finder.

The problem

Many channels, no single view.

  1. 01

    Bookings arrive from five or more portals, each with its own reports.

  2. 02

    Reviews are copied by hand into a spreadsheet, one portal at a time.

  3. 03

    Guide fees and bonuses are recalculated by hand at the end of the month.

  4. 04

    Seats can differ between systems, and a channel can sell places that no longer exist.

What you receive

One platform, four tools in it.

  • Operating platform.

    Overview, departures, sales, portfolio, reviews and bookings, with a page for every tour. Access by invitation only.

  • The Monday report.

    The week in one email: sales, departures to watch, new reviews.

  • Reviews read by AI.

    Every review from every portal, classified by topic and by tour.

  • Seat checks.

    Every morning, the departures where a channel can sell places that are no longer available.

How it works

Three weeks, three steps.

  1. Week 1

    Read-only connection

    We connect to your channel manager with credentials that can only read, and list the data available.

  2. Week 2

    Checked data

    Your sales history is loaded and checked against the system, to the cent. The first reports start running on their own.

  3. Week 3

    Platform online

    The platform goes online behind a login, after a security review by someone who did not build it.

  4. Then

    With your approval

    Automations that write, such as realigning seats between systems, are added one step at a time, each approved by a person, and you widen them as you see the results.

Measured on the first project

Numbers from the first project.

18 days
from kickoff to platform online
51,804
rows of sales history, checked to the cent
91%
agreement with the team on how reviews were classified
536 of 582
monthly guide bonuses matched the team’s own calculation
3 of 8
departures where a channel could sell seats that were no longer available, found in read-only

Your company

Your channels, the same platform.

What changes

Your channel manager, your portals, your tours, and your rules for guides and seats.

What stays the same

The read-only start, the approval by a person, the checked data, the security review and the platform.

What we need from you

Read-only access to your channel manager to start, your review records and one contact person.

Is it for you

It fits if

  • You sell tours, activities, experiences or tickets on online travel agencies.

  • Your bookings go through a channel manager or a booking system with an API.

  • Your team spends hours each week collecting numbers from different portals.

Selling on several channels? We connect them in read-only first.

Tell us which channel manager and which portals you use.

Let’s build your AI product