Yes, when each booth type is a package post with footprint, power, and capacity fields. A 360 booth needs a 10 by 10 footprint and a 20 amp circuit. A roaming booth is battery powered and works for outdoor cocktail hours. The bot asks about venue size and power when the brief is vague, then recommends the booth that actually fits. The decision is grounded in your equipment, not generic guidance pulled from training data.

Yes. Backdrops and prop sets live as posts or taxonomy terms with photo, theme, and upcharge. The bot answers backdrop and prop questions with the same data your operations team uses for setup. A request for an 80s themed prop set returns the actual contents of that prop box, the upcharge if any, and a link to the photo gallery. The visitor sees what they would actually get rather than a vague yes.

Yes. Your booking calendar in WordPress, or in a third party booking plugin connected through the data source wizard, is part of context. Confirmed bookings block their dates and the bot only offers what is open. Saturday nights in June, September, and October are the typical bottlenecks, and the bot states the constraint clearly when the date is gone, then offers two adjacent Saturdays that are open as a fallback option.

Yes, through your existing payment plugin. SleekAI does not run a checkout itself. It hands the visitor a deep link to WooCommerce checkout or your booking plugin's deposit flow with the package, date, and add ons pre selected. Most photo booth operators keep the deposit at $200 to $500 to take the date off the market. The bot logs the conversation to WordPress so the operations team has the brief when the deposit clears.

Yes. Multibot lets you run a corporate booking bot with branded template upsell, lead capture overlay options, and net 30 invoicing language. The wedding page bot stays focused on package fit, props, and the 4 hour timeline. Display conditions scope each bot to its page so the conversation never mixes up activation language with reception language. Activation planners and brides have very different priorities.

Yes, when the system prompt is configured to mention the upgrade once. The bot is not a hard seller. It quotes the package the visitor asked about, mentions the upgrade with a one line description and the upcharge, and respects the visitor's choice when they say no. Overzealous upsell pressure costs deposits, and the prompt is tuned to mention the upgrade only when the visitor's brief makes it a good fit, such as a tall ceiling venue or a larger guest count.

Conversations are logged to WordPress per visitor session. Cross session memory across days is not the default because most photo booth leads convert within one session or get a follow up email. If a returning visitor identifies themselves by email, the bot can match against the prior conversation and pick up the brief. Most operators leave the bot stateless across sessions and rely on the operations team to follow up by email with the conversation summary attached.

Yes. The data source wizard reads from any post type, postmeta, taxonomy, or custom database table. Whether you use a dedicated wedding booking plugin, WooCommerce Bookings, or a custom build, the calendar and package data are readable. The conversation context is shaped by what is in WordPress, not by an integration. You do not need a connector or webhook to make the catalog visible to the bot, just a mapping that points the bot at your data.