Publish your booked-dates list or per-DJ availability on a hidden WordPress page - SleekAI checks it before quoting any date. The list updates as bookings come in, and the bot picks up the changes on the next conversation. Couples never get told a DJ is available who actually has another wedding that day; the calendar check happens before the quote.

Yes. If you have separate weekday or off-season pricing published, the bot uses the right rate for the date. Tuesday corporate events price differently than Saturday weddings, and a January Saturday in slow season might get an off-season discount if you publish one. The bot reads the date, applies the right rate, and quotes accurately.

If your packages itemize ceremony sound as included or as an add-on, the bot quotes it accordingly. Some companies include ceremony sound in the 6-hour package; others charge $200-$400 extra depending on the venue layout (long walks, outdoor ceremony, microphones for officiant and readings). The bot reads your package contents and quotes the line.

Yes. It routes corporate inquiries to your corporate package pricing - usually different from wedding pricing - and captures agenda, AV needs, and venue separately. Corporate events often have specific cue requirements (entrance music for the keynote, awards ceremony walk-on tracks, dance party ending) and the bot prompts for them so the planning call starts at the right level.

It hands off to your contract and retainer link with event date, package, and add-ons pre-filled where the platform supports URL parameters. 30% retainer link goes inline so couples lock the date the same conversation. The contract still happens in your CRM, so signed contracts and retainers route through the right accounting flow.

Most teams capture must-play and do-not-play lists in a separate planning form 60 days out, not at booking time. The bot links to that form after booking instead of trying to capture music preferences in the inquiry chat. Music vibe is a longer conversation than a chatbot is built for - the planning call handles it better.

If a couple asks for Marcus and Marcus is booked on their date, the bot apologizes and offers Sasha as an alternative with a quick bio. If both are booked, the bot acknowledges and offers to route to a referral list if you publish one. Couples who insist on a specific DJ on a booked date are routed to your contact form - sometimes flexibility on dates exists, but the bot does not promise it.

Yes - if your package pages explain the logic (ceremony adds an hour to the call time, requires a separate sound system at most venues, increases cartage), the bot mirrors that explanation. Couples often want the cheapest package without realizing ceremony coverage is what they actually need; the bot calibrates expectations so the right package gets booked the first time.