Date: Thu, 28 Mar 2024 01:46:54 -0700 (PDT) Message-ID: <1342713962.287.1711615614419@[209.237.231.73]> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_286_2060317635.1711615614415" ------=_Part_286_2060317635.1711615614415 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The BookingCenter Kiosk solution enables ea= ch Kiosk to offer a Booking Engine that is specific to the specific Kiosk n= eeds. For example, each Kiosk can use it's own Booking Engine template; each Ki= osk use the System Date to allow bookings up to an hour in the early = am and then cut-off additional bookings automatically for that 'business da= y'; each Kiosk can use its own payment gateway, thus supporting either<= /em> 'EM= V MyCa= rd' or<= /em> 'Tr= aditional MyCard'= or no payment gateway; and from the booking can seamlessly check-= in their booking, as they standing at the Kiosk.
Each Kiosk Agent selects a unique Booking = Engine template when offering 'Book Now' capabilit= ies at the specific Kiosk(s), in order to facilitate the best experience fo= r a Kiosk Guest. Learn more about the different Booking Engine templa= tes here. &= nbsp;
For example, if your Site= ID is MYPMSDO and you use two Kiosks: K1 and K2, the Booking E= ngine =E2=80=98agent allocation' for K1 (set to use Booking Engine template= : 01) would link as: https://book.bookingcenter.com/01/?site=3DMYPMSDO&agent=3DMYPMSDOK1.
The other K2 'Kiosk agent' might be set t= o use Booking Engine template: 02 and it would then link to:https://book.bookingcenter.com/02/?site= =3DMYPMSDO&agent=3DMYPMSDOK2.
By default, the Kiosk uses the 'System Date' of the PMS as the 'arrival date' to offe= r the Guest the ability to 'Book Now' and upon successful completion of the= ir <optional> eSign and payment policy compliance, 'check in' to thei= r unit. By using System Date, the property can accept arrivals for 't= oday' as late in the evening as desired.
Most properties manually manage N= ight Audit to set their System Date, and then increment the date manually when they wish. But some properties use Auto Night Audit t= o do this, and this can allow any setting between midnight and 6:30 am in h= alf hour segments. For example, if you are willing to accept bookings= via your Kiosk for 'today' up till 4 am, but then want to stop any more ch= eckins for the day, your options are:
Each Kiosk can have its own EMV payment terminal, so that a Kiosk in one=
location can offer different EMV terminal(s) than other Kiosk(s). If=
using an EMV terminal, it is required that the Kiosk and the EMV device be=
on the same subnet of your IP network, and the EMV device secured and powe=
red-up to work. Getting a user to identify and use a 'tap/dip/swipe' =
EMV device can be a challenge, thus BookingCenter allows you a 'Note' field=
to explain to the Guest where the EMV device is located and how to use it.=
Note that you can use either an EMV device=
(what we call 'EMV M=
yCard') or have the guest enter their credit =
card manually (what we call 'Traditional MyCard') when paying via Self Check-in. Either way =
is secure and offers PCI compliance. In fact, you can offer a
If you are a property that participates in 'Suppressed Rate Bookings' (f= or example Expedia pre-paid bookings) and you require that an incidental cr= edit cards be saved prior to allowing check-in, then this is supported, as = well.
Upon completing the booking, the Guest is requested to click a 'Check in= now' button (or 'Pay and Check-in Now' if using payments) and then they perform thei= r Self Check-in without having= to authenticate themselves (as they just completed their booking, we 'know= ' who they are).