A shared playbook: property management is never solo work
Accepting or declining bookings is not an individual art project; it is a repeatable process that must hold steady when the point person changes, someone is on leave, or you are already driving to an emergency maintenance call. This playbook is not a substitute for legal house policies or local short-term rental rules; it is an operational page that spells out roles, timing, escalation tools, and what to log in the PMS before clicking approve or decline. The goal is fewer internal collisions and a coherent guest experience even when they speak to different teammates.
Core separation: who reads inbound mail, who decides non-standard exceptions, and who records rationale so the next shift does not guess what was promised. Align housekeeping and maintenance partners on approved exceptions when risk or noise constraints drove a decline on other services.
Minimum roles: intake, analysis, decision
Intake collects inquiries across channels, runs a fast pass with the shared checklist, and tags a request as green or potentially off-pattern. Analysis (often the same person in small shops) cross-checks guests, dates, contacts, history when visible, and message threads. If everything fits, move forward; otherwise draft three bullets summarizing gaps and questions already asked. Decision on sensitive exceptions stays with a supervisor or portfolio PM—publish explicit monetary or reputation thresholds that auto-trigger escalation.
Tiny teams collapse these hats onto one human; the page still prevents skipped steps under cognitive load. Larger teams avoid five parallel interrogations of the same guest with mismatched tone.
Escalation in three beats
- Structured clarification: one outbound message listing missing items with a reasonable reply window.
- Supervisor review: if answers are evasive or new exceptions stack, halt ping-pong and bring in whoever owns owner-facing policy.
- Motivated decision: conditional acceptance (deposit, guest cap), scripted declines when counsel requires, zero emotional improvisation in chat.
Each leg gets a CRM note: timestamp, author, essential content. That trail matters when complaints surface weeks later.
Message models and tone
Four templates cover most cases: missing-data request, deposit proposal, house-rule confirmation, professional decline. Avoid template sprawl—mixed styles confuse guests. Personalize only objective details (dates, amounts, property label). If external tools summarize requests (for example a Risk Radar workflow beside HostGuard), keep that summary in internal notes, not raw exports to guests.
Short rituals and tiny KPIs
A fifteen-minute weekly touch between inbox owners and owner supervisors catches drift early. Track yellow-tag rate, first-reply time inside SLA, and approved exceptions versus the monthly cap agreed with owners. Random oscillation without seasonal reason means the playbook is muddy or someone bypasses steps.
Playbook killers
- Side-channel chats outside the PMS.
- Verbal exceptions without written notes for housekeeping or concierge.
- Dual decisions when the guest messages two platforms and nobody coordinates.
Bridging intake and on-the-ground teams
Acceptance rules matter little if cleaning arrives with a four-person sheet while the inbox approved six guests. Bake a handoff checklist into the playbook: guest count caps, parking limits, pet approvals, arrival window. Field teams should not infer policy from rumors; they should read the same CRM snippet intake used when confirming money. Night auditors or emergency phones need the same page—nothing erodes trust faster than «We never approved a dog» while the guest brandishes an email thread nobody logged.
When you wire lightweight scoring or reminders from tools like HostGuard Risk Radar, route them to both intake and supervisors, not to a siloed dashboard nobody opens on Saturday night. Signals only improve decisions when the right people see them at decision time.
Owner expectations without chaos
Portfolio managers juggle owners who want volume and owners who fear parties. Publish internal guidance on how many yellow-tag bookings you accept per month per asset, how you document post-stay outcomes, and when you will decline despite owner pressure. Owners respond well to transparent dashboards: exceptions granted, complaints received, deposit claims filed. The playbook becomes the contract between revenue goals and risk appetite.
Training rotations help: twice a year, have owners’ representatives shadow inbox reviews for two hours. They stop asking for «special favors without paperwork» when they see how fast ambiguity compounds.
Contingencies when platforms change rules
OTAs tweak verification and payout timing without warning your stand-up agenda. Maintain a changelog section inside the playbook: date, channel, what shifted, updated template ID, who confirmed the legal read. Operators stop improvising contradictory answers when deltas are bite-sized rather than inferred from rumor. If automation from HostGuard or similar flags match the new funnel steps, annotate that dependency so nobody disables a script without noticing downstream deposit timing.
For direct sites, contingency is simpler technologically but politically harder with owners impatient for occupancy. Tie every rule change to a written risk note so revenue conversations stay grounded.
Quality assurance drills
Once a quarter, replay three anonymized threads—green, yellow, red—and score how closely the actual CRM notes matched the playbook. Celebrate near misses corrected by supervisors; fix systemic misses with template updates rather than blaming individuals.
Handoffs between shifts without losing context
Playbooks fail when the outgoing operator summarizes a yellow booking in a hallway whisper instead of a CRM note. Standardize a four-line handoff: guest name, bucket, open questions, next action owner. If a supervisor approved an exception, paste the approval line verbatim so the night team does not renegotiate terms. When multiple time zones touch the portfolio, timestamp notes in UTC or property local time—pick one and stick to it so nobody misreads «tomorrow morning».
Pair handoffs with a quick scan of payment status: deposit received, preauth pending, or none required. Money surprises at 11 p.m. are playbook failures, not guest malice.
Practical follow-up
Publish a single wiki page: roles, SLAs, three templates, escalation ladder. For three days, ask staff to flag where they skipped the doc and why—often complexity, not laziness. Simplify until the page survives peak pressure.