General
General enquiries
hello@communitylet.co.uk
Use this for broad platform questions, account help, or anything that does not fit a booking-specific or venue-specific route.
Contact this team
Overview
CommunityLet is set up to support both customer-side booking questions and venue-side operational enquiries. Keeping those routes separate helps us respond faster and with the right context.
Use the contact options below as your starting point. Once your Strapi single type is in place, you can replace all of this copy, the headings, and the contact methods without changing the page structure.
Helpful note
Including the venue name, facility name, requested date, and the type of support you need will speed up routing and reduce back-and-forth.
Contact routes
Start with the option that best matches the outcome you need. Each card can later be edited from a single Strapi entry.
General
hello@communitylet.co.uk
Use this for broad platform questions, account help, or anything that does not fit a booking-specific or venue-specific route.
Contact this teamBookings
bookings@communitylet.co.uk
Use this for booking-request questions, saved card issues, customer-side booking flow problems, or request follow-ups.
Contact this teamVenues
venues@communitylet.co.uk
FAQ
These can later become editable FAQ items in your single type, but the page already supports them now.
Include the venue name, facility name, requested date, and the email used for the booking so the team can locate the request quickly.
Send the venue and facility names together with the specific pricing or content changes you want made so the request can be actioned without back-and-forth.
Share a short overview of the venue, the kinds of spaces you want to list, and whether you already have booking rules or pricing structures defined.
Include the page URL, the action you took, and a screenshot if available. That is usually enough to reproduce and prioritise the problem.
Next step
You can browse live venues, open facility detail pages, and review the booking journey before getting in touch.
Use this for venue setup, facility presentation, pricing structure, permissions, or operator-side workflow questions.