Skip to main content
Available on request, with the Fetchski Reservation System. Fetchski sets this workflow up inside the Reservation System for each organization that wants it. You don’t install any code. To have it enabled, contact your Fetchski representative.

The situation

You change your pricing in the Reservation System: a new price for a service, a service you no longer run, a new one added to a range, new peak dates, a discount moved. Your website doesn’t hear about it. Months later a pricing section still states the old price, an FAQ answer quotes last year’s discount, and a list of services still offers one nobody can book.

What it does

Notices each change to your pricing

A change to a service or to your rates starts a check, after a short wait so a burst of edits is checked once. A weekly check runs as well, on the day and hour you choose.

Reads your services and rates

Your services (name, price and its unit, whether it is an add-on, how many can be offered at a time, whether it is retired) and your rates, peak dates, discounts, loyalty levels, insurance and transport, straight from the Reservation System.

Finds where your website advertises them

Your Attract site’s published pages, every section on them (pricing cards included), and your FAQ answers, under whatever names you use for your offerings. It remembers where they are, and only a page or answer that changed is read again: while nothing changes, a check costs nothing.

Finds what is advertised and wrong

A price the site states differently, a retired or unknown service still offered, a claim your configuration contradicts (a unit, a limit, an add-on, peak dates, a discount, a level, insurance or transport), and an active service missing from a list of its own kind on your site.

Drafts the fixes, if you want them

Optional: your CMS’s own site agent edits each affected page as a draft, submitted for review. When it is not clear where a fix belongs, you get two or three options to pick from.

Emails you the report

For each page: what your site says, what your configuration says, and the drafted fix or “report only”, then what the check spent on AI. Options are marked as a multiple choice: publish just one and remove the rest. If a check fails, you get an email saying why and what to do.

What it never does

Publish

Fixes are drafts in your CMS’s Submitted Drafts. Nothing goes live until a person publishes it.

Report what you don't advertise

It never asks you to advertise something new. It only flags what your site already says and gets wrong.

Invent a price

Every price and percentage in a draft comes from your configuration. An instruction stating any other price or percentage is refused before it reaches your site.

Touch your customers

It reads your services and rates only. Customers’ own prices, bookings and payments are never read or sent to a model.

What you need

  • An organization on the Fetchski Reservation System, with your services and rates kept there.
  • An Attract site for the same organization.
  • Your Fetchski representative to enable the workflow. They connect it to your site with a read-only API key, and agree with you who receives the report, which day the weekly check runs, and whether it drafts fixes or only reports. Drafts are made by your CMS’s site agent and use your CMS’s AI budget.