All guaranteesHotel Booking Engine
Eight guarantees on your booking engine
We guarantee the system works and own our mistakes. Occupancy we do not guarantee.
- What it means
- Three things are guaranteed: the booking engine is live, the channels are in sync, and payments land in your account.
- For example
- Day 25 after go-live, your calendar still is not closing automatically on Booking.com. You tell us, and we fix it at no cost. If it still does not work on day 60, we send your final instalment back, less any late-delivery discount already given.
- How to claim
- One WhatsApp message as soon as something does not work. We check it together and fix it. If it genuinely still does not work on day 60, we transfer the final instalment, less any late-delivery discount already given, without you chasing us.
- Worth knowing
- The first two instalments pay for work that is finished and stays yours: the website, the accounts, the configuration and the connected channels. The final instalment is paid at go-live, so that is what comes back if the system does not work, less any late-delivery discount already given.
- What it means
- The date your booking engine starts taking orders is written into the contract, not said in a chat.
- For example
- The contract says 21 working days. On that last working day, a guest can book and pay on your website.
- How to claim
- Nothing to claim. We calculate the discount ourselves on the final invoice.
- Worth knowing
- If your photos, rates or OTA account access are what run late, the date moves with them. The same applies while merchant activation from DOKU or Xendit, an onboarding slot from STAAH or Cloudbeds, or connection approval from an OTA is still pending: other companies make those calls, not us.
- What it means
- We connect the channels in your plan, then test them with a real booking before handover.
- For example
- We book one night through your website. That date closes across every channel, we show you it happening, and then the test booking is cancelled.
- How to claim
- WhatsApp or call us. In working hours, Monday to Saturday 09.00-18.00 WITA, a clash is handled ahead of every other request. Outside working hours, a clash report is answered within 2 hours between 07.00 and 22.00 WITA, and reports after 22.00 are answered from 07.00.
- Worth knowing
- A clash from a booking entered manually outside the system, or from a channel you run yourself, is outside this cover.
- What it means
- The website built alongside the booking engine carries a 30-day bug-fix guarantee.
- For example
- A button that does nothing, or a broken page in the first 30 days, and we fix it at no cost.
- How to claim
- Report it on WhatsApp. Anything that makes the site unusable is handled the same working day.
- Worth knowing
- A new feature is not a bug. It is quoted separately, and we name the price before starting.
- What it means
- STAAH, the domain and the payment gateway are registered to your name and your email, not ours.
- For example
- You stop working with us today. Your website and booking engine still run tomorrow.
- How to claim
- Ask for the account list any time. We send it within one working day.
- Worth knowing
- The STAAH subscription and the gateway fees are billed to you by the vendor directly, not through our invoice.
- What it means
- If you take Jalur Cepat, guests can book and pay on your website on working day 12, not day 21.
- For example
- You take Jalur Cepat because high season is close. On working day 12 the first reservation can come in, even though some website pages are still being finished until day 21.
- How to claim
- No claim needed. We count the days ourselves and transfer the fee if we miss.
- Worth knowing
- Only applies when Jalur Cepat is taken. Day one starts when photos, rates and OTA access are complete, and STAAH or Cloudbeds onboarding, OTA approval and payment gateway activation still run on their own schedules.
- What it means
- If you take management, your lowest rate per room type is written into the contract, and every rate change is checked against it before it is sent.
- For example
- Your Deluxe room's floor is IDR 900,000 a night. We mistype it as IDR 90,000, and two reservations land before it is corrected.
- How to claim
- Send us the reservation number on WhatsApp. We work out the difference and put it on the next invoice.
- Worth knowing
- Promotions you approved, and rates your team changes without going through us, are outside this cover.
- What it means
- The website built with your booking engine has to start being found by guests searching on Google, not only through the OTAs and the links you share yourself.
- For example
- On day 60 after the website launches, Google Analytics has not recorded a single WhatsApp click, form or reservation from a Google search visitor. That same month we start the first of up to 6 free SEO rounds.
- How to claim
- No claim needed. On day 60 we check Google Analytics and send you the result on WhatsApp, then a short note on each round we run.
- Worth knowing
- Conditions: the Google Business profile is in your name, the site is not blocked from indexing, and the Google Analytics and Search Console we install stay active. Visits from ads do not count. A guest who searched your hotel's name and then got in touch does count, because Google Analytics does not record the words searched. What we do not guarantee: a position for generic phrases like hotel Seminyak, or how many end up staying.
Working terms for website packages
Materials deadline, the discount if we run late, and the deposit back if you stop, on one page.
Still unclear on something?
Ask about any part of it. We will answer in the same plain language you just read.
See Hotel Booking Engine packages