1. Book a tour
- Useful context
- Chosen location and a preferred visit time
- Receiving owner
- Location team
- Confirmation check
- Describe whether the time is requested or confirmed, and how the team follows up.
Your notes
Coworking location and enquiry-routing map
Prepared by Derrick Kityo · ReviewedChoose the smallest useful set of questions for each type of request, then keep the location and offer with the handoff. Test what the visitor sees and what the receiving team gets.
Completed fictional workspace example. The locations, routes and roles are planning examples, not DeskLodge or TOSH Space internal processes.
2. Enquire about a meeting room
- Useful context
- Location, room, intended date and group size
- Receiving owner
- Meeting-room team
- Confirmation check
- The same room and date reach the receiving team; the reply route works.
Your notes
3. Ask about venue hire
- Useful context
- Location, type of event and an outline of the request
- Receiving owner
- Venue-hire lead
- Confirmation check
- Set expectations for the next conversation without implying confirmed availability.
Your notes
4. Ask about workspace membership
- Useful context
- Location and the workspace option of interest
- Receiving owner
- Membership team
- Confirmation check
- Preserve the selected offer; avoid asking for unrelated event details.
Your notes
5. Booking service unavailable
- Useful context
- Relevant location and a short description of the issue
- Receiving owner
- Support or location team
- Confirmation check
- Offer another contact route and avoid a false success message.
Your notes
Use this with your team
- Map your actual locations and visitor tasks before selecting form fields or a booking integration.
- Replace the sample owners with real inboxes or system destinations and agree the confirmation wording.
- Submit fictional requests on mobile, follow them into the receiving workflow and record any lost context.
Source notes
W3C WAI: forms tutorial
Use the tutorial when reviewing labels, instructions, validation and success or error messages. Keep requests short and ask only for relevant information.