ThinkReservations

ThinkReservations connects from inside MAYA and receives prices, so a ThinkReservations property gets the full path: the history import, starter rules, the calendar, going live and sending. This page covers how to connect, what MAYA reads, which rate type it writes to, and what works differently from Cloudbeds, including how you connect, how rooms are counted, how a send is checked, and how a disconnect or a reconnect shows up.

Connecting

There is one way in. You create your MAYA account, pay, and then connect. ThinkReservations has no marketplace listing for MAYA, so there is no free trial without a code, and a code may be needed at checkout. Read codes and the free trial.

1. 1

   Create your account and pay. At checkout, choose Think Reservations as your system. If the code field is required, enter the code we gave you.

2. 2

   On the screen titled Connect your property system, click Connect → beside Think Reservations. The card says Sign in with your Think Reservations account. There is nothing to copy and nothing to set up on the ThinkReservations side.

3. 3

   Sign in on ThinkReservations' website and approve. If you are already signed in to ThinkReservations in this browser, it uses that login and goes straight to approving, so check it is the login for this hotel. MAYA asks ThinkReservations for permission to read your bookings, rooms, rates and availability, to write rates, and to stay connected without asking you to sign in again. It does not ask for guest details. Finish within 15 minutes. If it takes longer, you land on a MAYA page that says "That sign-in link ran out after 15 minutes. Start again from MAYA." Nothing is wrong and nothing was set up: press Back to setup and start again. If you click Deny, the page says "MAYA wasn't given access, so nothing was changed. Start again and allow access." If ThinkReservations doesn't finish the sign-in, it says "Think Reservations didn't finish connecting" with "Try again in a moment".

4. 4

   You are brought back to MAYA. MAYA names the property from ThinkReservations, reads its time zone and currency, and starts the history import. A property whose currency MAYA doesn't price in yet stops here instead, with "Your property's system uses KRW. MAYA doesn't price in KRW yet, so nothing was set up or imported. Email us and we'll tell you when it does." (with its code), and nothing is set up. So does a property that is already in MAYA under someone else, with "This Think Reservations property is already in MAYA, so nothing new was added. Ask its General Manager to invite you, or email us." Which currencies MAYA works in has the list. If a property with that name already exists on MAYA, a "(2)" is added. You can rename it in the questions step. Read the history import.

Every property starts in simulation. Nothing is sent to ThinkReservations until you go live. Read simulation mode.

Sending to ThinkReservations also has its own switch on MAYA's side, apart from Cloudbeds', and it is on. If it is ever off, Go live waits until it is back on, and a live property is priced as usual but nothing is sent. Read going live.

Messages you can meet on the way in

• "Think Reservations needs an access code", with "You paid without a code, and Think Reservations needs one to connect." You paid without a code, because the system you chose at checkout did not need one, and ThinkReservations does. Any code used at checkout counts, whichever system you chose there. A code can only be entered at checkout, so email us and we sort you out.
• "Payment comes first", with "Set up payment, then connect your property system." The subscription has not gone through yet. Press Back to setup and finish it.
• "Already connected", with "Your property system is connected, so nothing was changed." A second connect was started after your property was connected, from another tab or a page left open. Nothing was added. Press the button to carry on.
• A page headed "We hit a snag connecting your property" with the reason and a Try again button. Most reasons end in "Try again in a moment." and mean exactly that. Where trying again would fail the same way, the button reads Back to setup instead. Read messages you might see, explained.

One property per login

If your ThinkReservations login can reach several hotels, the connect step stops with "This Think Reservations login covers 3 properties. MAYA signs one property up at a time right now" (with your own number) and no Try again link. MAYA cannot tell which of them you paid for, and picking one could price the wrong hotel. Reply to your receipt or email us and we set the properties up by hand, each as its own property in MAYA. There is no group flow for ThinkReservations yet.

What MAYA reads from ThinkReservations

On every cycle, about every five minutes, MAYA reads from ThinkReservations:

• Bookings made or changed since the last read. A booking that holds several rooms arrives with one entry per room. MAYA keeps each room's room type, its nights, and its nightly room charge. A booking that names only its room, as when you sell rooms by name, is counted under that room's room type from your list of rooms. A booking on a room your list marks as not a room or not included in occupancy is left out of occupancy, booking speed and pickup, as that room is left out of the room count. If the list of rooms can't be read on a cycle, a booking MAYA already has keeps the room type it had.
• Room types, by name, and your list of rooms, which MAYA counts room type by room type (see below). A room type ThinkReservations no longer lists is switched off in MAYA, and back on if it is listed again. The change log says so under "Changed in Think Reservations".

About once an hour, MAYA reads your rate types (their names, whether each is standard or follows another, and which room types each covers) and your own nightly rates for the next 396 nights from the rate type it sends to, and from each other standard rate type it moves. Once a day it re-reads the whole booking window, so a booking missed in between is picked up within the day.

At connect, MAYA reads the property's name, time zone and currency once. They are not refreshed afterwards. If you change your time zone or currency in ThinkReservations later, email us and we change it in MAYA.

The nightly rate MAYA stores is the room charge on the booking, after any discount, placed on the night it was billed for. Pet fees, packages and other items are never read as a room rate. If a booking's room charges are not dated night by night, the room total is split evenly across its nights.

The booking date is the moment ThinkReservations recorded the booking, read on your property's own calendar. A booking made at 11 pm at a property in California is dated that day, not the next. MAYA keeps that moment too, to the minute, so separate bookings made together can count as one (What is counted).

ThinkReservations sends guest details with every booking even though MAYA does not ask for them. MAYA drops them before anything is stored: names, emails, phone numbers, addresses, dietary notes, arrival times and special requests never reach MAYA's database. Read what MAYA reads and writes.

A booking in a group, or with a room from a group block, arrives with the group's or the block's id, and the group's name. MAYA never keeps either: it turns the id into a scrambled key that can't be turned back, keeps only the key, and counts the group's bookings as one booking for booking speed. The name is never read. Pickup and occupancy count every room. Groups count once from when MAYA has read your booking history with the keys, so similar past nights count their groups the same way: the first import does that, and for a property connected earlier, Get suggestions from my data reads it again. Until then each reservation counts as its own booking. Read What is counted.

Which bookings count

MAYA keeps a booking when ThinkReservations lists it as scheduled, checked in or checked out. A booking marked cancelled or no show is removed on the next read, and its nights come off the count, every room it held included. Cancelling changes the booking, so the cancellation arrives in the same five-minute read as everything else. A room taken off a booking that holds several comes off on the next read too, and the booking's other rooms stay. A booking deleted in ThinkReservations is no longer in anything it returns, so it comes off at the daily re-read: MAYA asks again for just that booking's nights, and once the answer comes back without it, its nights from today on come off the count. Every change, and when MAYA picks it up has the details.

Nights run from check-in up to, but not including, check-out. A same-day booking is one night. Each room in a booking is one booked room on each of its nights.

For occupancy, each room counts. For booking speed, a booking counts once however many rooms it holds. A 4-room booking for one night is 4 booked rooms and 1 booking. Read booking speed.

How many rooms each room type has

On every cycle MAYA reads ThinkReservations' list of rooms and counts the rooms in each room type, so each room type has its own count. The Room types block on the PMS tab shows it as units beside each one. A room is left out when ThinkReservations marks it as inactive, as not a room, or as not included in occupancy. A room you do not sell online still counts, because it can still be sold at the desk. A room type with no rooms in the list counts as 0.

If a count looks wrong, check those three settings on the rooms in ThinkReservations. MAYA reads the change on the next cycle. If ThinkReservations cannot send the list of rooms on a cycle, MAYA keeps the counts it already has and measures nothing for your bill on that cycle. While any room type ticked as a room still shows 100 rooms, the number it has until the list is first read, nothing is measured for your bill.

Sellable occupancy divides by these counts, and so does the room count on your bill, over the room types ticked as rooms. Read your room count and what you pay.

Room groups

When you sell rooms by name, each room is its own room type in ThinkReservations, and its Room Group column puts them together. MAYA reads each room's Room Group with the list of rooms on every cycle, and shows your room types under their groups.

A room type's group is the one its rooms share. Its inactive rooms decide only when every room of it is inactive. If its rooms are in different Room Groups, or some are in one and some in none, it shows under Other, with the room types in no group.

If the list of rooms can't be read on a cycle, or ThinkReservations sends it with no Room Group field on any room, MAYA keeps the groups it has. A room moved to another Room Group shows under the new one on the next cycle. A room with an empty Room Group is in no group: take a room type's rooms out of their Room Group and it shows under Other from the next cycle. Take every room out of its Room Group and every screen reads as for a property with no Room Groups.

Nothing about groups is sent to ThinkReservations: each room type still gets its own price, from its own rate. A group never decides which room types count as rooms.

Groups show in five places: the group buttons in the rule builder, the Room Types column of the rule cards on the Rules tab, the day detail on the calendar, the room count strip and the floors and ceilings on the review, and the Room types block on the PMS tab. A property with no Room Groups sees every screen as before.

Which rate type MAYA sends prices to

ThinkReservations marks each rate type as standard or as following another rate type (derived). MAYA sends its prices to your Best Available rate type: the standard rate type whose name contains "Best Available". A rate type marked inactive in ThinkReservations is never used, whatever its name. A rate type called "Best Available Non-Refundable" has those words too. One named exactly "Best Available" or "Best Available Rate" comes first for every room type it covers, so a longer name is written to only for a room type the exact one leaves out. To be sure, give exactly one standard rate type a name with "Best Available" in it, or pick the rate type yourself (below).

If no active rate type is called Best Available, MAYA uses the one active standard rate type that covers the most room types. That could be a non-refundable or a package rate type, because ThinkReservations marks those standard too. If two standard rate types tie for that, neither is used, and nothing is priced or sent until you pick one or name one Best Available. A room type the chosen rate type does not cover is not priced or sent. MAYA never hands a room type's price to a non-refundable or package rate type instead.

Derived rate types reprice themselves from their parent by ThinkReservations' own rules. A non-refundable rate that follows Best Available at 10% off moves when MAYA moves Best Available. MAYA never writes to a derived rate type and never creates a rate type. A non-refundable or package rate type marked standard, with rates of its own, is one of your other standard rate types: it gets the same change as Best Available on its own rate, unless you leave it out. Name your main rate type Best Available so it is the one chosen above.

Seeing and picking the rate type

The PMS tab, the review screen and the go-live confirm say which rate type MAYA reads your rates from and sends its prices to: "MAYA reads and writes: Best Available Rate", with your own rate type's name. When different room types use different rate types, each is named with its room types. The line shows once MAYA has read your rate types, a few minutes after you connect. Below it, MAYA says what needs you:

• A room type with no rate type: "No rate type for Deluxe, so it isn't priced."
• A tie: "Rack Rate and AAA could each be the base, so MAYA reads and writes none of them. Pick one."
• Two Best Available rate types: "Best Available Rate and Best Available are both named Best Available. MAYA uses Best Available Rate, the first Think Reservations lists. Pick one to be sure."
• When different room types use different rate types, such a pair is named with its room types: "Best Available Rooms and Best Available Rooms 2 are both named Best Available for Standard and Deluxe. MAYA uses Best Available Rooms for them, the first Think Reservations lists." A pick covers only its own room types, so there is nothing to pick here. To end it, rename one in ThinkReservations.

A General Manager or Hotel Admin can pick the rate type from the Rate type list on the PMS tab or the review screen, and so can MAYA support in God Mode. Everyone else sees the line without the list, and their warnings end "A General Manager or Hotel Admin can pick one on the PMS tab." The list offers Automatic, the choice above, and every active standard rate type. MAYA reads and sends to the one you pick for every room type it covers, from the next cycle, and the automatic choice never replaces it. A room type it doesn't cover is not priced or sent. Pick Automatic to go back.

On a live property the list asks before it saves: "From the next cycle, MAYA reads and sends to Rack Rate. Best Available Rate keeps the prices MAYA last sent it, and rate types that follow it stop moving with MAYA." Press Switch to save, or Cancel. MAYA never puts the old rate type's own rates back: it becomes one of your other standard rate types, held out and marked New on a live property, until you tick it. Ticked, it moves only on nights MAYA never sent prices to while it was your main rate: MAYA doesn't know its own rate there, so those nights keep MAYA's last price, and the list says how many, such as "Not moved on 120 nights MAYA priced it as your main rate". On the next cycle each night MAYA already sent is priced from the new rate type's own rate and sent to it. When the new rate type is one MAYA was moving as another standard rate type, a night it moved is priced from that rate type's own rate as MAYA read it before its first move, not from MAYA's price there. If that cycle's read of your rates fails, those nights wait for one that works, as a first send does. A night MAYA sent to under that rate type before, when you switch back, keeps the starting rate it had.

If the rate type you picked is removed, switched off, or set to follow another rate type in ThinkReservations, MAYA never swaps in another. Nothing is read or sent, and the line says "Rack 2025 is switched off in Think Reservations, so nothing is read or sent. Pick another." (or "isn't in Think Reservations any more", or "follows another rate type now"). The change log says so too (below). Pick another rate type, or Automatic.

When a room type has no base rate

If no rate type MAYA can read covers a room type, that room type is not priced or sent. MAYA's next read of your rate types, about once an hour, puts it in the change log, whether you are live or in simulation: "MAYA can't find a base rate for Deluxe in Think Reservations, so its rates can't be changed", with the action "Add a base rate for this room type in Think Reservations." Add the room type to your Best Available rate type in ThinkReservations, or pick a rate type that covers it. A tie reads "Think Reservations has more than one rate type MAYA could price Deluxe from, so it isn't priced", with "Pick the rate type MAYA reads and writes on the PMS tab." A rate type you picked that is gone reads "The rate type picked for MAYA is gone or switched off in Think Reservations, so Deluxe isn't priced", with "Pick another rate type on the PMS tab."

Live, the entry is headed "Prices not reaching Think Reservations". In simulation it is headed "No rate to price from in Think Reservations". It covers every night ahead of that room type and ends on the first read that finds a rate type for it. Read when your property system does not accept a price.

Your other standard rates

Besides the rate type MAYA reads and writes, your property can have other active standard rate types with rates of their own, such as a wedding block, a group rate or an event rate. MAYA moves the ones ticked on the PMS tab. When you set up, every one starts ticked; one MAYA first finds once you are live starts held out until you tick it (below). Rate types that follow another (derived) are not among them: they already move with their parent in ThinkReservations.

Each one gets the same change MAYA makes to the rate type it reads and writes, applied to its own rate, so its usual gap to your main rate stays. When a rule raises Best Available by 15%, a wedding rate of $300 that night goes to $345. A rule that adds $40 adds $40 to it. Several rules on one night apply in the same order as on your main rate. A rate type that covers only some room types moves only for those.

Your floors and ceilings are for your main rate only, so a wedding rate can go below or above them. A price you type in MAYA is for your main rate only too: while it is on a night, the rule changes it replaced come off your other standard rates, and a rule that fires after it moves them again. A rate you change on your main rate type in ThinkReservations that MAYA keeps as your price does the same: changing Best Available by hand on a night takes that night's rule changes off your wedding and group rates too (rates changed in your system). A night a rate type has at 0 in ThinkReservations (closed, or not loaded) is never moved, and a change that would take a rate to 0 or below is not sent. A night held back on your main rate waits on your other rates too.

Once you are live, MAYA reads each ticked one's own nightly rates about once an hour, as it reads your main rate. A rate you change by hand in ThinkReservations on a night MAYA moved, once MAYA's price there has been read back, is kept as that rate type's own rate for the night, and a rule that fires after it moves it from there. A change of one percentage to nearly every night is the exception, as on your main rate: it is not kept (raising every night by the same percentage). With MAYA's price wins, MAYA sends its own price again instead. Neither shows a warning or goes in an email. Sends are checked the same way as on your main rate (below). If one keeps being refused, or never saved, the change log names the rate type once it has gone on for a few hours: "Think Reservations isn't taking MAYA's prices for Harbour Wedding on Deluxe", with "Check Harbour Wedding in Think Reservations.", or "Think Reservations took MAYA's prices for Harbour Wedding on Deluxe but never saved them". When ThinkReservations refuses MAYA altogether, such as its permission to update rates, the change log has the one item about your main rate for it.

The list is under "MAYA reads and writes:" on the PMS tab and the review screen, headed Also moves with MAYA, with a tick beside each rate type MAYA moves. One that covers only some room types says which, such as "Standard and Deluxe only". The ? beside the heading says the same in short. A General Manager or Hotel Admin can tick or untick each one, and so can MAYA support in God Mode. Everyone else sees the list with "A General Manager or Hotel Admin can change this on the PMS tab." The list does not show while no rate type is in use (pick one first).

• In simulation every one starts ticked, and a tick or untick saves at once.
• Live, ticking asks "From the next cycle, MAYA moves Harbour Wedding too, with the same change it makes to your main rate." with Move it and Cancel. MAYA reads that rate type's own rates before it sends anything to it. Unticking asks "MAYA puts back Harbour Wedding's own rates and stops moving it." with Leave it out and Cancel: on the next cycle MAYA sends the rate type's own rate back on every night it moved, once, and leaves it alone after that.
• Held out, a rate type is yours. A rate you change on it in ThinkReservations is kept, whatever MAYA's price wins says.
• Ticked again, whatever the rate type has in ThinkReservations then is its own rate, and it gets the whole change on top. A wedding rate you set to $320 while it was held out goes to $368 under a 15% raise.
• MAYA moves up to 25 rate types. Ticking one more says "MAYA moves up to 25 rates. Leave another out first." A rate type you ticked that comes back past 25, switched back on in ThinkReservations or no longer your main rate, is held out and marked New.

A rate type that first appears after you go live starts held out, with New beside it and a Leave out button. Tick it to have MAYA move it, or press Leave out to keep it held out without the New. If your property was already live when MAYA started moving other standard rate types, every one started held out and New, so nothing MAYA already sent changed until you looked at the list.

The go-live confirm names them: "MAYA also moves: Harbour Wedding and Garden Party Weekend." and "Held out: Lantern Group Block." What it names as moving is what moves once you are live.

How a send is checked

ThinkReservations does not apply a price the instant it receives it. It answers "accepted" and applies the price shortly after, and there is no job for MAYA to ask about afterwards, as there is with Cloudbeds. So MAYA checks by reading. About once an hour it reads your rates from ThinkReservations, and a send counts as landed when that read finds MAYA's price there.

Once a send has been read back and is at least 60 minutes old, a rate you change in ThinkReservations on that night is kept as your price at the next read, exactly as on Cloudbeds. A change you make before MAYA has read its price back is judged 3 hours after the send. A rate that is neither MAYA's price nor the one the night had before the send is your change, and is kept as your price (with MAYA's price wins, MAYA sends its own price again instead). A rate set back to exactly what the night had before the send can't be told from ThinkReservations dropping the send, so MAYA sends its price again, as below. Read rates you change in your property system.

Until a read finds the price, the change log and the line under the price box say "Accepted by Think Reservations, checking." Once it does, they say "Sent to Think Reservations."

If ThinkReservations accepts a price and then never applies it, MAYA's reads still find the rate from before the send. 3 hours after the send, or at the first read after that, MAYA counts it as not applied and sends the night again, up to 10 tries at that price, then once a day. The night stays one open problem until a read finds MAYA's price there. Once it has gone 6 hours like that, the change log shows "Think Reservations took Standard rates but never confirmed it saved them" under "Prices not reaching Think Reservations", and our team is told.

ThinkReservations may keep prices in whole units, so a whole-number rate less than one unit from MAYA's price (less than $1 in dollars) counts as MAYA's price. A price that moved by less than one unit can therefore count as landed when it never was. If a night in ThinkReservations still shows the old rate hours after MAYA's calendar changed, email us the night and room type and we check it.

Permission problems

If ThinkReservations lets MAYA read but refuses the write, the change log shows "Think Reservations won't let MAYA change Standard rates because MAYA doesn't have permission to update rates", with the action "Give MAYA permission to update rates in Think Reservations, then reconnect on the PMS tab." Reads, pricing and the calendar carry on. The held prices go out on the cycle after you reconnect.

A refused write never disconnects a ThinkReservations property. The connection stays up, and only the sending waits.

Disconnecting and reconnecting

ThinkReservations does not tell MAYA when access has been removed. MAYA reads the refusal when its next call fails, renews its access and asks once more. A failed read is tried again 10 minutes later, then about every 15 minutes, and nothing is priced or sent while reads fail. After three refused reads in a row (about half an hour), after about an hour of reads failing for any other reason, or when ThinkReservations refuses to renew MAYA's access, the Connection card on the PMS tab reads Error and the banner "MAYA has lost its connection to Think Reservations" appears for a General Manager or Hotel Admin, with a Reconnect Think Reservations button. Our team is alerted too, at the latest when the card reads Error. If it still reads Error an hour later, every General Manager and Hotel Admin gets one email saying so. Read emails MAYA sends. Until the status changes, the tab can still read Connected while calls are failing. If prices have stopped and the tab still reads Connected, a General Manager or Hotel Admin can click the quiet Reconnect Think Reservations link on the PMS tab anyway. Which ThinkReservations login you sign in with matters, so read the next paragraph first.

To reconnect, click Reconnect Think Reservations on the banner or on the PMS tab, sign in on ThinkReservations' site with a login that reaches this hotel, and you are back on the dashboard's PMS tab with the note "Reconnected." Your rules, history and settings are untouched. Finish signing in within 15 minutes. If it takes longer, you see "That sign-in link ran out after 15 minutes. Start again from MAYA." Nothing has changed: press Back to the PMS tab and start again. Any reconnect that stops, a Deny included, ends on a page like that, headed "Think Reservations wasn't reconnected" or "Think Reservations didn't finish connecting", with the same button. Syncing resumes within about five minutes, or about 15 minutes if reads had been failing. Read reconnecting and disconnecting.

If ThinkReservations doesn't answer that question, you see "Think Reservations didn't answer. Try connecting again in a moment." and nothing changed. A property with no ThinkReservations hotel on record yet is bound to the hotel the login reaches when it reaches exactly one, and is refused when that one is already another MAYA property's, with "This Think Reservations login is for a property that is already connected to another property in MAYA, so nothing was changed." A login that reaches several hotels is taken without binding any, even when another of them is already in MAYA, and we set the hotel by hand. Reconnecting and disconnecting has every case.

MAYA has no disconnect button of its own. To remove MAYA's access in ThinkReservations, cancel your subscription first, then email us and we walk you through it.

MAYA never sees your ThinkReservations password. ThinkReservations gives MAYA its own access to work with. If prices stop updating after you change your password, a General Manager or Hotel Admin can click Reconnect Think Reservations on the PMS tab, even while the tab still reads Connected.

The PMS tab for a ThinkReservations property

Below the cards, "MAYA reads and writes:" names the rate type MAYA uses, with the Rate type list for a General Manager or Hotel Admin (read Seeing and picking the rate type), and under it Also moves with MAYA with your other standard rate types.

The Connection card and Last sync are right for ThinkReservations. The Recent requests to Think Reservations list and the Health (last 24 hours) card both read "Not tracked for this system", because MAYA keeps a log of its requests to Cloudbeds only. It does not mean syncing has stopped. Last sync is the number to look at. Read the PMS tab.