A group of eight is deciding where to go on Saturday. One of them is nineteen. Two are wearing trainers. They are travelling in from out of town and they are not willing to gamble the night on a venue that might turn them away.
So they ask, and if nobody answers, they go somewhere that did.
What people ask
People usually ask what the dress code is and whether trainers are allowed, what the minimum age is and whether it changes on different nights, what identification is accepted, whether there is a cover charge and when it applies, what time it gets busy, whether they can reserve a table, whether there is a cloakroom and whether it is card only.
Example conversations
These scripts use information a venue might publish. Your answers should come from your own pages.
Customer: Are trainers allowed on a Saturday? Assistant: The entry page explains the dress code for each night, including which footwear is acceptable and which is not, and notes that entry is always at the discretion of door staff on the night.
Customer: One of our group is nineteen. Is that okay? Assistant: The page states the minimum age for each night and lists the forms of identification accepted. Everyone who looks under the age shown should expect to be asked.
Customer: How late can we arrive without queuing? Assistant: The page explains the usual busy times and when queues typically build, along with how table bookings and guest list entry work.
Never guarantee entry
Door staff decide on the night, and no website should override that. Explaining the policy and adding that entry remains at the door team's discretion is both accurate and protective.
Age and identification
This is the question people are most awkward about asking and most likely to be refused over. Listing accepted identification specifically, rather than saying valid ID, prevents a genuine problem for younger customers with limited documentation.
Dress code in plain words
Smart casual means nothing. Listing what is not permitted, in specific terms, is what customers need, and it is far less likely to cause an argument at the door.
Accessibility
Step-free access, accessible toilets, whether there is seating and how to arrange assistance. These questions are asked quietly and decide whether someone comes at all, in the way described in dress code, kids and dogs, the small questions that decide visits.
Busy nights and waiting times
Groups want to know whether they will spend an hour outside. Publishing when queues usually build, whether there is a faster route for table bookings and how long waits typically run on the busiest nights helps people plan their evening rather than gambling on it.
Offers and guest lists
Discount entry, guest lists and promotions generate their own confusion, handled as described in how to handle discount and coupon questions with a chatbot.
Bookings alongside
Table and booth enquiries follow the pattern in table and booth bookings bars lose to slow replies, and private hire in private party and venue hire questions for bars.
Getting started
Publish dress code specifics, age policy, accepted identification and busy times, then answer at any hour. SpideyChat for bars and restaurants answers from your published pages. Try SpideyChat on your own site, or read about answers on the features page.