Key takeaway: Booking.com Pulse Greece hosts and managers should treat Pulse as Booking.com’s free official partner app for phone-side ops — reply to guests, mark no-shows, tweak availability and rates, and switch multi-property portfolios without waiting for a laptop. It does not fully replace the Extranet: advanced setup stays on desktop, attachments are images only (no PDF or QR), and Booking.com may temporarily disable link-sharing if it detects suspicious activity. Confirm every UI path in your live partner account; labels move.
This is a field playbook for Greek short-term rental owners, villa and apartment managers, and multi-property operators who work off-laptop — islands, turnovers, ferry ETA changes, traffic between buildings. It sits next to our guides on Booking.com message templates, cancellations and no-shows, guest phone numbers, and Request to Book. Pulse is the mobile ops layer; those articles still own inbox craft, fee clocks, and phone-access policy.
Who needs Pulse in Greece
Pulse is useful for a single Athens apartment if you want push alerts after midnight. It becomes essential in Greek field ops: a manager covering three hillside villas, a cleaner waiting on a late ferry, a host in traffic when a guest asks for a gate code, or a same-day arrival whose ETA moves after weather or a strike. Booking.com’s Partner Hub positions Pulse so you can monitor reservations, update availability and message guests when you are away from a computer. Multi-property switching in one account helps teams that run several AMA-registered units — each team member still needs their own user and two-step verification, per Booking’s Pulse help.
Install, verify the device, turn on push notifications
Booking.com’s Pulse solutions page frames setup in three steps. Adapt the wording you see in-app, but keep the sequence:
- Download Pulse from the App Store or Google Play (or via the QR path on the Partner Hub Pulse page). Use official stores only.
- Sign in with your Booking.com partner (Extranet) credentials and verify the device when prompted.
- Turn on push notifications for bookings, messages and reviews so alerts reach you in the field.
Device verification is not optional. Booking’s Pulse help: pick a registered mobile number, choose SMS or voice for a code, enter it. If the number is missing, verify via Extranet → My devices, then return to Pulse. Admins can Deny old devices when a phone is lost or a contractor leaves. Supported OS floors on that help page (checked 11 Oct 2026): Android 10.0+ and iOS 16.0+. Pulse is free and available in 44 languages — useful when seasonal staff prefer Greek UI labels while still messaging guests in English via translation.
What Pulse does well vs what stays on the Extranet
Booking.com is explicit: Pulse complements the Extranet; it does not fully replace it. You can handle reservations, availability, guest messaging, analytics, reviews and some property details in the app, but advanced setup still needs the Extranet. Use this as an ops split, not a philosophy debate.
| Task | Pulse (phone) | Extranet (still needed) |
|---|---|---|
| Reply to guests / templates / auto-replies | Yes — Bookings → guest → Messages | Full Messaging Preferences, security URL whitelist, deeper inbox tools |
| Mark a no-show | Yes — Bookings → Mark as a no-show | Same action; finance/invoice follow-up |
| Update rates & availability | Yes — real-time calendar updates | Complex rate plans, LOS rules, bulk strategy work |
| Facilities & services tweaks | Yes — More → Property details → Facilities & Services | Broader property description / layout edits |
| Guest phone number access | Yes (with reservation permissions) | Yes — same permission model |
| Advanced account, payouts, deep policy setup | Limited / not the primary surface | Required — see also our Booking.com payouts Greece coverage for money-side context |
iOS users can add Booking’s Pulse Daily Activity widget for arrivals/departures; widget data stays hidden while the device is locked. Handy on turnover mornings — still open the reservation when something looks wrong.
Messaging on the go: speed, templates, translation — and hard security limits
Pulse messaging path (Partner Hub): open the app → Bookings → select the guest → Messages → write and Send. You can use templates, automatic replies, image sharing and location sharing. Built-in translation covers English, German, French, Spanish, Dutch, Polish, Russian, Arabic and Portuguese — enough for most Greek summer mix, not a claim that every guest language is covered.
Do not re-build your entire template library from this article. Our dedicated message templates Greece playbook already maps Extranet/Pulse Messaging Preferences, schedulers (booking made, week-before, day-of-arrival, and related stages), automatic replies, and Greek ferry/check-in wording. Use Pulse to fire and monitor those tools in the field; use the templates article to design them. Booking’s templates help also reminds connected partners that Connectivity providers no longer receive guest phone numbers — numbers stay in Extranet or Pulse for permitted users, which is why our guest phone numbers Greece guide still matters when a ferry delay needs a call.
Security limits are operational constraints, not footnotes:
- Images only in chat attachments. Booking.com states PDFs and QR codes are not supported in platform messaging. Share directions or check-in maps as text or as an image. If you must send a PDF, Booking points you to the reservation email alias — not the chat attach button.
- Anonymised emails. Guests and partners see aliases (@guest.booking.com / @partner.booking.com style), not private addresses. Keep money talk and document links inside Booking’s channel.
- Link-sharing can be disabled. If Booking detects suspicious activity on the account, it may temporarily block links in messages (including via Pulse) while teams investigate. You can still send text and images. Whitelist trusted URLs in Message Preferences security settings before peak season.
- Phishing caution. Faster replies help guests; they also help attackers if someone hijacks your inbox. Treat unexpected “pay outside Booking” requests as hostile even when they appear in a thread that looks familiar.
| Channel limit | Official rule (Partner Hub) | Greek field implication |
|---|---|---|
| Attachments | Images only; no PDF / QR in chat | Send lock-box map or gate photo as JPG/PNG; do not attach a PDF “welcome pack” |
| Messaging window | From booking until 7 days after checkout or cancellation | Post-stay damage or missing-item chats have a short clock — escalate early |
| Guest-initiated extra window | If the guest messages, you get 14 days to reply | Do not assume the thread stays open forever after departure |
| Message history | After one year post checkout/cancel, messages are no longer readable | Export or screenshot critical threads before you need them for a dispute |
| Links | May be disabled on suspicious activity | Keep a text-only check-in backup (code + steps) ready for island Wi-Fi chaos |
Booking.com’s marketing line on the Pulse page is soft but attributable: their data shows guests who get faster responses tend to cancel less and leave better reviews. That is not a published Greek percentage, and Booking does not publish a public numeric “Reply Score” clock on the current Pulse pages we opened. Do not invent thresholds. Compete on actual response speed and clear templates instead.
Reservations, no-shows, availability and rates on the phone
Pulse gives a real-time overview of upcoming bookings, guest details and special requests. You can view and update rates and availability so last-minute Greek demand swings (a sudden Athens conference weekend, a weather-driven island reshuffle) do not wait until you are back at a laptop.
No-shows are a first-class Pulse action. Booking’s no-show help documents the Pulse path: Bookings → find the reservation → Mark as a no-show → confirm Yes. The reservation is then cancelled and both sides get a cancellation email. The Mark as a no-show control is available from midnight on the planned check-in date until 48 hours after planned check-out. Miss that window and you may face full commission on the original booking under Booking’s General Delivery Terms — details and fee/waive mechanics belong in our cancellations Greece playbook; this article only flags that Pulse can execute the mark when you are standing in an empty villa at 00:30.
Extranet no-show flow still offers the waive-fee vs charge-fee choice with more explicit prompts; Pulse’s published steps emphasise confirm Yes after Mark as a no-show. UI copy can differ by app version — if you need to waive a fee and the phone screen is ambiguous, open the Extranet or contact Partner Support before you lock the outcome. Never invent a “local cash no-show settlement” outside the booking.
Multi-property switching and the timezone quirk
If one Booking.com account is linked to multiple properties, Pulse can manage them without signing out. Booking’s Pulse help notes that Home and Reservation views can show data across properties by default, while Availability, Messages and Property details use a property selector. Train your team to glance at the selector every time before they close dates or send a template — the classic multi-villa mistake is blocking the wrong house after a no-show.
Timezone mismatches are a known FAQ, not a Greek myth. Pulse converts UTC timestamps using the phone’s timezone; the Extranet may reflect the computer’s timezone. If message times disagree, align time and timezone on both devices. For Greece that usually means Europe/Athens (EEST UTC+3 in summer / EET UTC+2 in winter) on every staff phone — especially for contractors who travel with a home-country timezone still enabled.
Greece field checklist: ferries, late arrivals, smart locks, disabled links
Pulse does not rewrite Greek logistics. It shortens the loop when logistics move. Pair it with your existing ops articles on early check-in / late checkout and smart-lock backup plans.
| Field situation | Pulse move | Do not |
|---|---|---|
| Ferry delayed; guest asks for late entry | Message on-thread; share image of map/gate; adjust expectations | Send a PDF guide or off-platform WhatsApp-only deal |
| Same-day ETA change while you are mid-turnover | Push alert → reply from Bookings → Messages | Ignore until laptop; silent gaps drive cancellations |
| Guest no-show after midnight check-in day | Mark as no-show in Pulse within the published window | Leave the booking open for days “just in case” |
| Smart-lock instructions | Text steps + image of lock/map (images allowed) | QR-only entry sheet attached as PDF in chat |
| Links suddenly fail in messages | Fall back to pure text + images; check security settings / support | Invent a personal PayPal link “because Booking blocked URLs” |
| Wrong property selected in multi-villa app | Re-check property selector before closing dates | Bulk-block every house after one incident |
Facilities updates can also happen on the phone when a pool heater fails or a seasonal spa is offline: Pulse → More → Property details → Facilities & Services → save. Guests should not discover a closed amenity from a review if you could have flipped it during the drive between properties.
Seven-day post-checkout messaging: plan the tail of the stay
You can message from booking time until seven days after checkout or cancellation — enough for a missing charger chat, tight for a slow damage case. If changeover looks wrong, photograph, message and open the claims path immediately. If the guest messages first after leaving, Booking’s contacting-guests help gives a 14-day reply window; after one year, history is no longer readable. Pulse does not extend those clocks.
Conclusion: a phone-first ops stack, still Extranet-backed
For Greek Booking.com hosts and managers, Pulse keeps reservations, guest chat, no-shows and calendar edits in your pocket. Install from official stores, verify every device, set Europe/Athens on staff phones, and design templates on the Extranet before you need them on a windy pier. Keep advanced setup — deep rates, payouts, Request to Book policy — on the Extranet and in the Host Daily guides linked above.
Checklist before your next island week:
- Pulse installed on every active ops phone; old devices denied in Extranet → My devices.
- Push notifications on for reservations, messages and reviews.
- Message templates and automatic replies built (see our templates guide); images prepared for check-in maps — no PDF/QR dependence in chat.
- Trusted URLs whitelisted; text-only check-in backup ready if links are disabled.
- Team drilled on Mark as a no-show timing (midnight check-in through 48 hours after planned checkout).
- Property selector habit for multi-villa accounts; phone timezone set to Europe/Athens.
- Extranet still bookmarked for advanced setup — Pulse complements, it does not replace.
Primary references for this playbook are Booking.com’s Partner Hub pages for the Pulse app, using Pulse, templates and notifications, contacting guests, marking no-shows, and updating facilities via Pulse. Re-read those pages when Booking changes a label — Host Daily will not invent a clock Booking has not published.

