Stay on topic
Platform messaging exists to coordinate a specific meal—ingredients, access, timing, dietary needs—not to become an open-ended chat or a path around safety tooling. Boundaries protect hosts from scope creep and guests from pressure. They also preserve a record if something goes wrong.
Questions that belong in thread
- Allergies, intolerances, and religious dietary requirements.
- Arrival logistics—parking, stairs, companion animals in the home.
- Menu clarifications—“Is the broth fish-based?” “May I bring a sealed wine?”
Questions that should stay shallow
- Personal contact details before a confirmed booking—generally redirect to the platform.
- Off-platform payment requests—decline and report patterns that feel coercive.
- Romantic or intrusive topics unrelated to the meal—hosts and guests both deserve a clean exit: “Let’s keep this about dinner; thanks for understanding.”
Hosts: model the redirect
If someone asks for your phone number “for convenience,” a calm template helps: “We keep logistics here so nothing gets lost—happy to confirm arrival at 6:45 in this thread.” Consistency trains the room.
Guests: report discomfort early
If messages feel pushy, discriminatory, or unsafe, use reporting tools rather than hoping it resolves at the door. Product teams need signal; you need documentation.
When warmth and boundaries coexist
You can still be friendly—emoji, a joke about dessert—without erasing structure. The best threads read like a good maître d’: warm sentence, clear facts, next step.
Stay in the loop
Read coordination for day-before cadence and trust for how signals from messaging and reviews compound.