Waymarker

Checkfront integration

The booking agent that finishes the job

It is 21:40. Six people have just decided to do something on Saturday, and one of them is on your site with a card in their hand. Your phone is off. A chat tool answers their question, congratulates itself, and hands them a link to a booking page where they have to start the whole conversation over in a new tab. Most of them do not. That handover is where the booking dies, and it is the only part of the job that was ever hard.

Waymarker is a chat agent that sits on your Checkfront account, reads your real availability, creates the booking, and takes the guest through to payment. It confirms a booking as paid only by reading the status back from Checkfront, never from what the guest says in chat.

What it does with your account

It reads live availability per item and per timeslot, using your own prices, not a cached copy. It creates a real Checkfront booking. It then hands the guest your hosted payment page and watches the booking until Checkfront itself reports it paid.

The confirmation a guest sees is driven by the booking record, not by the conversation. A guest can type "I have paid" all night and the agent will keep saying the booking is still open, because it is asking Checkfront rather than believing the chat.

What it refuses to do

Trust in this category is on the floor, and it deserves to be. These are the limits the code enforces, not a tone of voice.

  • Never invents a price. Prices come from your booking system, and if the price at creation does not match what the guest agreed to, the booking is refused rather than charged and a human is brought in. That is a deterministic check, not a matter of the model behaving well.
  • Answers policy questions only from what you gave it, and hands off when it does not have the answer. We will not claim a model can never phrase something loosely, because nobody can honestly claim that.
  • Never books outside a group-size limit it cannot verify. An unknown bound is a reason to stop, not a reason to guess.
  • Never pretends to be a person, and says so before the first message.
  • Never asks for card details in chat. Payment happens on your hosted page, not in the conversation.

Three Checkfront traps that cost real money

Not general advice. Each one is a bug that reached a live booking on a real venue, and each one was silent: no error, no warning, nothing in a dashboard. If you are evaluating anyone who plugs into Checkfront, these are good things to ask them about.

  1. The guest-count parameter is per item, not per account

    One product calls it `adult`, another calls it `participant`. Send the wrong one and Checkfront does not reject it. It ignores it and prices the booking at the default party size. A party of nine gets charged for four, and the booking looks perfectly normal in your dashboard.

  2. The invoice pay link is off by default

    Checkfront only puts a Pay Now button on a booking invoice when the account has enabled it under Manage, Layout, Invoice. Until that box is ticked, a guest sent to that page sees a balance due and nothing to click. Anything that tells a guest to pay there is promising something the account cannot deliver.

  3. The MIN and MAX party fields lie

    A product reporting 0 and 0 is not unbounded, it is undisclosed, and it will still reject a party below its real minimum at the moment of booking. Read those fields as limits and show them to a guest, and you have produced a confident, wrong answer about who is allowed to book.

A European supplier, stated precisely

Waymarker is built and run by a Danish company. Most chat agents aimed at tour and activity operators are built in North America or Australasia, so for a European venue this is often the part that decides whether procurement says yes.

Here is the honest version, because "EU-based" is the easiest half-truth in this market. Your database and our backend are in the EU: Supabase in Paris, Hetzner in Germany. Your contract is with an EU company, we are the processor and you stay the controller, and there is a data processing agreement to match.

What does leave the EU: the conversation text goes to the model providers, Anthropic and OpenAI, both US companies, and our email and crawling suppliers are US too. That is true of essentially every AI product on the market, including the ones telling you they are EU-native. We list every subprocessor and its region on our security page rather than making you ask.

The EU AI Act is also our problem rather than a surprise waiting for you. Guests are told they are talking to an automated agent before the first message, which is the Article 50 transparency duty that became applicable on 2 August 2026. The Act puts an AI literacy duty on you as the deployer too, so we publish a short guide for owners instead of leaving you to discover that on your own.

9.4minutes from booking created to paid

One real guest, with nobody from our side involved, paid EUR 144 through the agent nine and a half minutes after it created their booking. Availability, booking, payment, confirmation, unattended.

That is one paid booking, not a conversion rate. We are early and would rather say so than imply a track record we do not have. Anyone quoting you a percentage this early is guessing.

Questions

Does it need access to my Checkfront account?

Yes, an API token and secret from your account. They are encrypted before storage and only ever used from our backend, never from a browser. You can revoke them in Checkfront at any time and the agent stops immediately. There is no lock-in to escape from.

Will it double-book a slot?

It re-checks availability at the moment of booking rather than trusting the price and slot it quoted earlier, so a slot taken mid-conversation is caught before the booking is created.

What happens when it does not know something?

It hands the guest to a human and tells them that is what it is doing. It does not fill the gap with a plausible answer. For a booking product, a confident wrong answer about a price or a policy is worse than no answer at all.

Which other booking systems do you support?

Checkfront is the only one running today. The integration sits behind an internal adapter so others can follow, but we are not going to list platforms we have not shipped.

Does it work in languages other than English?

Yes. Each venue sets its own languages and the agent holds the booking state across a mid-conversation language switch. Danish, German and English are in live use.

Will it replace my staff?

No, and we would rather you did not buy it for that. It earns its keep on the enquiries nobody is there to answer: after closing, mid-game, on your day off. If you are answering all of them already, it will not pay for itself.

Apply to join

We take on a few venues at a time so each one gets set up properly. Give us your address and we will build the agent on your own times and prices, then send it back so you can watch it work before you decide.