A channel drops at 2am.You find out Thursday.
The failure is not what costs you. The gap between the failure and finding out is. We shorten that gap with a check every working day, on Beds24, STAAH or Cloudbeds, whoever installed it.
| What breaks | Unwatched | With Jaga |
|---|---|---|
| Sync to one OTA stops running | Days at a time | At the next working-day check |
| Calendar does not close after a booking | Until the second guest arrives | At the next working-day check |
| Settings drift after an OTA rule change | Weeks | When the working-day check shows it |
| Configuration lost to a misclick | Found out when needed | Restored from backup |
The right column is when we know, not when the problem is solved. You are told by the next working day at the latest, and fixes run in business hours WITA.
One double booking is not one lost night. You find the replacement property, you cover the difference, and you still collect one bad review that the next guest reads for months afterwards.
That is why what is sold here is watching rather than repair. Repair arrives after the break; watching arrives before anyone knows.
Three things that break silently
A booking engine never tells you when it stops working. It simply goes quiet, and quiet looks exactly like fine.
The OTA connection drops and nothing makes a sound
A token expires, an OTA changes its API, or a connection fails once and never retries. From your side the dashboard looks normal. Only one thing has changed: the calendar over there stopped following the calendar over here.
The platform changes its rules and your settings fall behind
Cancellation policies, minimum-stay rules and rate plan formats change, often without a notice owners actually see. Settings that were correct last month become settings that refuse bookings this month.
There is no copy of your settings to roll back to
One wrong click on a rate plan or an allotment, and there is no earlier version to restore. What is left is rebuilding from memory, usually on the busiest day.
Four jobs, done as routine
Short routine work: checked every working day, hands-on only when something breaks. That keeps the price low.
Your system is audited once, first
If we did not install it, we write down what is inside: live channels, rate plans, allotment, and the points most likely to drop. Without that we would only be guessing at what to watch.
Sync status checked every working day
The status of every OTA connection is checked every working day (Monday-Saturday). If one stops following, you are told by the next working day at the latest, with what dropped and what we are doing about it.
Configuration backed up monthly
Booking engine and channel manager settings are copied and kept. When something changes or disappears, there is a version to restore rather than a memory to reconstruct.
Settings realigned when an OTA changes its rules
When a platform changes a policy or a format, your settings are brought back into step. Each adjustment counts as one repair from the monthly allowance: 1 for villas, 2 for hotels.
The same system, two states. One is checked every working day; the other is not.
What the subscription contains
All of it in your name. If you stop, the system stays yours and stays running.
- A sync status check every working day on every live channel
- Word by the next working day at the latest when a channel drops
- Monthly configuration backup, restorable
- Settings adjusted when an OTA changes its rules, counted as one repair
- A one-page monthly report: occupancy and booking sources
- WhatsApp us in business hours WITA
- 1 repair a month for villas, 2 for hotels; beyond that IDR 500K an hour with a written estimate
- For hotels: STAAH or Cloudbeds and each of its channels checked too, the PMS not included
Three steps, 5 working days
- Days 1-2
Audit what is inside
We ask for read access to your booking engine and channel manager, then record the channels, rate plans, allotment, and the points that fail most often.
- Days 3-4
Fit the monitoring
A working-day check is set up for every connection, the WhatsApp number for outage notices is recorded, and the first backup is taken.
- Day 5
Break it on purpose
We make one test booking on a date closed to guests, to confirm the working-day check actually catches a fault rather than existing only on paper. We never disconnect a live channel to do this. After that it runs as routine.
What we carry, and what we do not
We cannot promise a system never breaks. What we promise: you are never the last to know.
- If a channel stops syncing and we have not told you by the next working day at the latest, that month's Jaga fee is not charged.
- A double booking caused by a sync error on our side: we find the replacement property and handle the guest. We cover the price difference for one night, for one unit or room per incident, up to one month of your Jaga fee.
- If you take booking engine management, Jaga is already included and never billed again. Stop any time, with no penalty and no minimum term, and service runs to the end of the month already paid.
- We never move an account into our own name; access runs through an invite and is revoked when you stop.
Compare it to one double booking
Two prices, split by property type and by how much there is to watch. Stop any time.
Per month for a villa. Hotels are IDR 2,500,000 a month. If somebody else installed your booking engine there is a one-time takeover audit: IDR 2,500,000 for villas and IDR 3,900,000 for hotels.
The five that come up most
Send your property name and the tool you run
Tell us who installed it and how many channels are live. We reply whether we can watch it.