# Taking requests > Let customers ask for a date and time for a party, event or whole-venue hire, then approve it, without making a new session for every one-off booking. Who can do this: admins only. A **By request** session lets customers ask for a date instead of booking one. They pick up to 3 dates, a time of day and a length, and you approve one. No more making a new session for every party or event. Taking requests is in a pilot with a few venues. If you'd like to try it, email wil@bookasession.org. Until then, use the [custom time, length or price](/docs/private-sessions#book-a-private-hire-for-a-customer-and-send-them-a-payment-link) steps. ## Set up a By request session On the [Sessions page](/go/admin/sessions), select **Add session**, then **By request**. In **Details**, add a name, description and photo. **Holds up to** is the most guests a request can ask for. Set it to at least 2, so customers can say how many are coming. If you have more than one site, pick the **Location** - approving a date hides the sessions that clash with it there. In **Lengths and prices**, add one **Whole session** price. Add each length customers can choose, up to 6 lengths of up to 12 hours, and set the price at each one. For a whole day, choose **All day** under **Add length**. In **When to take requests**, choose the days, the earliest start and latest finish, and how far ahead customers can ask. Save. The session is **Featured** on your booking page by default. In **Visibility** you can make it **Direct link only** instead, and share its link yourself. A By request session has no schedule, and you can't add a time to it from the calendar. Its dates are added when you approve a request. The end of **When to take requests** shows how many are booked and how many are waiting for payment, with a link to **Requests**. It also has no memberships, bundles or category, because the price is agreed per request. It can sell [add-ons](#add-ons). ### Prices or quotes To quote each request, turn off **Show prices** under your prices in **Lengths and prices**. Customers see "We'll send a price" instead of an amount. A price you set is never shown, and fills in when you approve. Leave a length blank to set its price when you approve. If you add a booking yourself on that date, type what they pay. With **Show prices** on, every length needs a price. ### Add-ons Under **Add-ons** in **Lengths and prices**, add extras like a cold plunge. Customers can pick up to 4 with their request and see a **Total**, or just the names with **Show prices** off. You can change them when you approve. They show on the booking like any other [add-on](/docs/add-ons). ### How far ahead **At least** and **Up to** set which dates customers can ask for, never sooner than your [minimum booking notice](/docs/booking-window). To pause new requests, choose **Not taking requests** in **Visibility**. The link then says you're not taking requests, and the ones you have stay open. Choose **Featured** or **Direct link only** again to reopen. If you make a session by hand for one booking - **Direct link only**, one date, a whole session price - the editor suggests taking requests instead. **Not now** stops the suggestion for everyone at your venue. ## Where customers find it A Featured By request session shows at the top of your booking page with the days you take requests for (for example "Fri and Sat in December") and **Request a date**. Selecting it opens the form. It only shows while you're taking requests. **Session types** on the [Sessions page](/go/admin/sessions) lists them in a **By request** group, with their days, hours and new requests. One that isn't taking requests shows **Paused**. ## What your customers see The session page shows a request form instead of a list of times, ending in **Send request**. Customers: - pick up to 3 dates, their favourite first, from the days you allow - your [closed dates](/docs/closed-dates) can't be picked, - choose one of your lengths and when it starts: morning, afternoon, evening or any time, or an exact time inside your hours. You agree the start when you approve. Anything else goes in **Add a note**, - say how many of them there are, up to the session's **Holds up to**, - add any of your add-ons, - leave their name, email, a phone number if they want to, and a note. Turn on **Ask for an address** for a mobile sauna, or anything held at the customer's place. The form then asks where to bring it and about access and parking. Once they're booked, the address and access notes show on the booking, at the top of the session's check-in list and in your new-booking email. If something is missing, the form says what under that field. The form never says a time is free: it offers only what you allow. ## After a customer sends a request The customer gets an email with a link to their request page, where they can see what they asked for, withdraw it, or request another date. Nothing is booked or charged. You and your staff get a **New request** alert by email and in the bell, under the **New bookings** alerts on [My account](/docs/team-notifications). ## Answer and approve requests Requests arrive in **Requests** on [Bookings](/go/admin/home). How to decline, approve, take payment and hold a date for online payment is in [Approving requests](/docs/approving-requests). ## Emails The request emails are sent for you, with set wording: **Request received**, **Request approved**, **Request declined** and **Held date released**, listed in the session's **Messages**. ## Common questions 1. **Does a request hold the date?** No. Nothing is held or booked until you approve it. 2. **Can a customer ask for a time outside my hours?** No. **Other time** must still start after your earliest start and finish by your latest finish. 3. **What stops spam?** A hidden spam trap, a limit on requests from one connection, 3 requests per email address a day and 50 per venue a day. 4. **Where do I reply to a customer?** Reply to the request email - it goes to the customer - or select **Reply** on the request in **Requests**.