Separate reading from resolving
A colleague opening a message does not establish that the guest received an answer. Keep a simple record of the outstanding question, responsible person and next action. Use the supported tools in your selected platform, but do not assume that every inbox provides the same assignment or status features. Demonstrate the handoff before relying on it during a busy arrival period.
Preserve the booking context
Identify the property and reservation alongside the question. Similar guest names or nearby dates can make a conversation easy to misread. Include only information needed for the handoff and keep sensitive material inside appropriate private systems. Do not copy an entire guest history into an unprotected team chat merely because it is a convenient way to transfer responsibility.
Handle absence explicitly
Decide what happens when the first responder becomes unavailable. Name the backup and make urgent arrival issues distinguishable from ordinary future-stay questions. These are operating decisions, not features we claim Lodgify automatically supplies. A shared inbox can help present information, but people still need to agree who acts and how an unanswered item is noticed.
Close with evidence
Record what was communicated and any follow-up still required. A completed message is not proof that a cleaner, payment provider or channel calendar also changed. Link those separate tasks through their actual references. Review a small sample of handoffs periodically and improve the wording that repeatedly causes confusion instead of introducing more automation before the basic responsibility is clear.
A concise handoff example
Use an original note such as: fictional reservation R-12, correct unit confirmed, guest asks about later arrival, no promise made, host to answer today. The note identifies responsibility without copying unnecessary personal details. When the answer is sent, record that action and any remaining property task. This example is a writing pattern, not a claim about automatic assignments inside a particular inbox.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Lodgify unified inbox — Merchant documentation · lodgify.com · Merchant-controlled · checked 2026-09-19