Host Resources
Guest Communication: What to Send Before Arrival
Give guests the right address, clear entrance directions, and a confirmed handover. Use adaptable message examples to resolve arrival times, requests, and changes before the journey.

Before guests arrive, send the property address, confirmed stay dates, agreed check-in arrangement, entrance directions, and a clear way to report a delay. Ask for the expected arrival time and any unresolved practical questions. Good host–guest communication before arrival gives someone enough information to find the right door and understand the next step without searching through a long conversation.
Build messages around the actual reservation and property. The Host readiness checklist covers preparation before listing. This guide covers the exchange that follows: what to repeat, what to confirm, and how to keep changes understandable. The examples are drafts to adapt, not automatic ShamStay messages or platform policies.
Image note: all three photographs are AI-generated photorealistic editorial images of fictional scenes. They do not show real ShamStay properties, hosts, or access arrangements.
What host–guest communication before arrival should cover
Start with information guests will use on the journey. Keep it in short, labelled lines that remain readable on a phone. A welcoming sentence helps, but the address, arrival arrangement, and requested reply should be easy to find immediately. Check these essentials against the reservation before sending:
- Stay: the correct property or unit, arrival date, departure date, and booked guest count.
- Location: the exact address and matching map pin, plus a useful entrance description.
- Handover: the actual check-in window and agreed method of entering or meeting someone.
- Contact: the person handling arrival, the agreed contact method, and how to report a delay.
- Reply needed: the estimated arrival time and any specific question still awaiting an answer.
Repeat relevant house rules briefly when they affect arrival, such as how to use a shared entrance. Do not turn the message into a second rulebook. Material conditions belong in the information guests consider before booking; an arrival reminder should agree with that offer.
Make the address clear and keep entry details private
On ShamStay, the saved exact property address and map pin are public before booking. Review them from the guest's perspective, then repeat the same location in the arrival message. Guests should not have to reserve a stay to learn its address. Access codes, key-storage instructions, and private entry credentials are separate information for the relevant confirmed guest.

Describe the final approach using observable details: the correct building entrance, the floor, and the route to the booked unit. If you include a photograph, use a current image of the real entrance and check that it does not expose access credentials or unrelated personal information. Avoid vague directions such as the usual door or behind the shop without enough context to identify it.
Check the arrival description against the property listing description. If the entrance involves steps, a shared passage, or another relevant physical feature, describe it accurately. When a guest asks about a particular access need, answer from the actual route rather than offering a broad assurance that everyone will manage.
Send each message when it helps the next decision
A useful sequence has three purposes: acknowledge the confirmed arrangement, prepare the guest for arrival, and resolve changes. Choose timing that suits the booking lead time and the handover. A stay booked shortly before arrival may need one concise exchange; a booking further ahead may need a later reminder. Do not present your preferred schedule as a universal platform requirement.
For a pre-arrival message, the host should focus on what the guest will need next. Keep vacation rental guest messages specific to the unit and reservation, even when a reusable draft saves time. Remove irrelevant lines and check that a previous guest's name, dates, or access details have not survived in the text.
Separate requests from confirmed arrangements
A guest may ask to arrive early, leave bags, bring an additional traveller, or change the handover. Acknowledge the question without implying approval before you have checked. State which part is confirmed and which remains unresolved. For short stay guest communication, this distinction matters because there may be little time to correct an assumption once travel begins.
For example, “I have your request for an earlier arrival; the existing check-in arrangement still applies while I check whether a change is possible” makes the status clear. If you can agree to a change, send the specific revised arrangement and ask the guest to acknowledge it. Do not promise luggage storage, transport, or another service simply to make the message sound welcoming.
If the arrival estimate changes, confirm the new date and time as well as who will handle the handover. A late journey can cross into the next calendar day. Use explicit dates and local property time when ambiguity is possible. For an issue that affects the reservation or cannot be resolved through the available process, contact ShamStay support with the relevant booking context.
Give the arrival contact one current version
When another person handles arrival, pass on the current agreed time, the correct unit, and the tasks they need to complete. Identify who answers the guest if plans change. Avoid leaving two people with different versions of a copied message, or assuming that a colleague has seen a conversation they cannot access.

Match the message to the prepared property using the host amenities checklist. If an agreed feature or arrangement changes, explain the specific issue promptly and use the appropriate process for the affected booking. Editing a reusable message for future guests does not resolve a promise already made to someone arriving today.
Read the final message as a guest on the way
Use this host checklist in Syria for the final read-through. Open the draft on a phone and follow the instructions in order, without relying on your knowledge of the home:
- The guest, unit, dates, address, and map pin match the reservation and listing.
- The arrival time and handover method are confirmed, with unresolved requests clearly labelled.
- Directions identify the correct entrance, and the contact arrangement is usable.
- Every placeholder is replaced, and private entry information goes only to the intended recipient.
- The message asks for a specific reply, and any second language conveys the same details.
If you are preparing to host, use the ShamStay Host guide for onboarding and listing review. Keep this communication checklist with your property preparation notes, then improve unclear instructions when guest questions reveal a gap.
Practical answers
Frequently asked questions
How far before arrival should I send the directions?
Send them early enough for the guest to review the route and resolve questions before travelling. Adjust the timing to the booking lead time and actual handover. If arrangements change, send a clear update rather than relying on an older message.
Should the public address and the private entry code go in the same place?
No. ShamStay's property address and map pin are public before booking. Keep entry credentials and sensitive access instructions in the appropriate private communication for the confirmed guest. Check the recipient and the current access arrangement before sending.
What if the guest has not replied with an arrival time?
Send a short follow-up that explains which detail you need and why it affects the handover. Do not treat silence as agreement to an unconfirmed time. Keep the existing arrangement clear and use support when an unresolved issue affects the booking.
Can one arrival-message template serve several properties?
Reuse the structure, then check every property-specific field. The address, entrance, unit, contact, timing, and access method may differ. Remove irrelevant instructions and review the completed message before sending; a template is a starting point, not evidence that its details are correct.
