Yes, if the drafts list is stored as a custom post type or a structured list on a drafts page. Each tap stores beer name, brewery, style, ABV, and price. When the keg blows and the bartender updates the page, the bot reflects it the same day. Cans, bottles, and signature cocktails live the same way. The bot can answer "any IPAs under 7%" by filtering the list, not by guessing.

Yes. Happy-hour windows (Mon-Fri 4-7pm, Sun all day) and specials ($2 off drafts, $5 well, $1 off wings) live as time-bracketed fields. The bot quotes the right window and the right exclusions (no happy hour on game days, holidays included or excluded). When the schedule shifts for a special event, you update the field and the bot is current.

Yes. Game-day broadcasts on the events calendar (or a custom game post type) carry team, time, network, and broadcast notes (sound on, which TVs). The bot answers "is the game on" with the kickoff time, the TVs, and any game-day specials. For bars that show local college games or regional rivalries, the bot can prioritize those over generic national broadcasts.

Yes. Amenities (number of pool tables, dart boards, shuffleboard, jukebox type, pinball machines) live as fields the bot references. "Do you have pool tables" gets a real count and the per-game price. Reservation policies (most dive bars don't reserve, some do for parties) come from the same field. The jukebox brand and whether it's free or pay reads the same way.

Yes. If the kitchen has hours and a menu, both live in fields the bot quotes. Most dive bars have a short bar-food menu (wings, nachos, pizza, burgers) with kitchen hours that close earlier than the bar. The bot quotes both: kitchen till midnight, bar till 2am, and what's still available after the kitchen closes (popcorn, peanuts, pretzels). Delivery and pickup info reads the same way if you offer them.

Yes. Birthday parties, work happy hours, and rehearsal-dinner reservations route to whoever handles them (sometimes the owner, sometimes a dedicated email). The bot captures party size, date, time, and any space requirements (back room, patio, full buyout), then forwards the brief. The first reply from the owner is already informed about the request.

Yes. Live music or DJ events live as event posts with band name, set times, cover, and age limit. The bot quotes those on the right night, so "who's playing Saturday" pulls from the calendar with set times and cover. Booking inquiries ("can my band play here") route to the booker with the genre, sound needs, and proposed date captured in chat.

Yours. SleekAI is BYO API key, so you bring an OpenAI, Anthropic, Google, or OpenRouter key and the model bills you directly. There's no per-message markup. A neighborhood dive bar usually spends $3 to $15 a month in API usage. GPT-4o-mini is plenty for this niche, where the questions are short and the answers should be short too.