Yes. Performance posts, exhibition posts, and special-event posts all load with their date ranges, and the bot prefers "currently open" or "this week" content over older programming when a visitor asks generically. For specific dates, the bot filters by the requested weekend and quotes show times, price bands, and ticket links. When you publish a new show or open a new exhibition, the next conversation reflects it without any retraining or content sync.

Yes. Member preview dates and discount codes are stored on the production or exhibition post, gated to the appropriate membership tier. The bot quotes the preview date and code to visitors who identify as members at the right level, and explains the path to upgrade for visitors who want preview access but aren't yet at the qualifying tier. The conversation stays on the upsell when it's relevant without being pushy when it isn't.

Yes, if subscription packages are stored as a post type or as a tier on the membership system. The bot quotes the package contents (which shows, which seats, what extras), the price, and any flex-ticket rules. Subscribers asking to exchange tickets or check what their package includes get an accurate answer from chat. Complex exchange requests route to the box office contact rather than the bot improvising on policy.

Yes. Class posts typically carry instructor, age range or skill level, schedule, price, materials list, and enrollment deadline. The bot matches a visitor's stated interest ("watercolor for adults, evenings, beginner") to the right offerings and surfaces instructor bios when asked. For youth programs, age requirements are strict, and the bot quotes the age range and prerequisites rather than rounding. Capacity status (open, almost full, waitlist) is also surfaced when stored on the class.

Yes. The system prompt routes patron-circle and major-gift inquiries to the named development director rather than improvising tier benefits or pledge logistics. The bot can quote standard tier benefits up to a defined threshold, then hand off. Naming opportunities, planned giving, and corporate sponsorship inquiries always route to a named human contact with phone and email, because those conversations need relationship-building that a chatbot cannot do.

Yes. Accessibility fields on each performance or exhibition post (ASL-interpreted dates, audio-described dates, sensory-friendly performances, wheelchair-accessible seating, captioned screenings) feed into the system prompt and the bot quotes them precisely. A visitor asking "is there an ASL-interpreted performance of Pippin" gets the date and time directly. This matters for compliance, and it matters for the visitors who need the information to choose a show.

Yours. SleekAI is BYO API key. For a typical arts nonprofit with seasonal programming spikes, monthly model spend usually lands between $20 and $150. GPT-4o-mini handles most calendar, membership, and class questions well. Larger models are worth it for nuanced patron inquiries, multilingual visitor base, or technical questions about historical exhibitions or artist provenance. There is no per-message markup, just direct provider pricing.

Yes, if volunteer roles are stored as a custom post type or as event signups. Ushers, docents, gallery sitters, and education volunteers each have role pages with requirements, training schedules, and signup links. The bot matches a visitor's interest to the role, quotes the next training, and captures intent for the volunteer coordinator. Returning volunteers logged into member accounts get a faster path with their certifications already on file.