You set the tone in the system prompt — warm, classic, romantic, contemporary — and SleekAI follows it. No emoji-heavy bot replies unless you specifically ask for them. The single most useful trick is to paste two or three of your coordinator's actual reply emails into the prompt as style references; the model picks up cadence rather than just rules and the difference in warmth is immediate.

Yes. Display conditions can hide the bot for logged-in couples — who already have access to your direct planning portal — and show a different one to public visitors browsing for the first time. You can also hide it on the gallery pages where couples want to scroll uninterrupted, and show it on the package and FAQ pages where questions actually land.

Either publish the brochure as page content — which is better for SEO anyway, since Google can't read your PDF either — or upload the PDF to OpenAI Files for vector retrieval. Both work. Most venues find that publishing the brochure as proper pages also improves their organic ranking on 'Cotswolds wedding venue' style queries, so the chatbot work pays a bonus.

SleekAI hands off via webhook to Tripleseat, HoneyBook, Aisle Planner, Iris Works, or any platform that accepts JSON. The payload includes wedding date, daytime and evening guest counts, ceremony type, accommodation needs, and the full transcript so your coordinator opens the lead with everything she'd otherwise spend the first ten minutes of a discovery call asking.

A one-time WordPress plugin licence and your own OpenAI key. A typical wedding venue with 30-40 chats a week spends a few pounds a month at OpenAI's gpt-4o-mini rates. Switch to a heavier model only if you find the conversations need more nuance, but for the warm-but-factual register most wedding bots aim for, mini is more than capable.

If you publish elopement and full-wedding pages separately with different package details, SleekAI matches the question to the right page and quotes accordingly. A couple asking about a 12-person midweek elopement in November gets the elopement package; a couple asking about 130 evening guests gets the exclusive-use Saturday package. The bot will not muddle the two.

Yes — if your supplier list and ceremony pages cover them. A couple asking about a Hindu mandap, a kosher caterer, or an Anglican blessing in addition to the civil ceremony will get answers based on what your site actually says you support. The bot will not invent a halal kitchen or a sikh granthi if you don't have one accredited; instead it will offer to flag the question for your coordinator to advise.

Not unless you explicitly write that into the system prompt — and we wouldn't recommend it. A pressure-selling wedding bot is the fastest way to scare a couple off your shortlist. SleekAI is configured by default to capture the viewing request, soft-hold the date, and let your coordinator handle the deposit conversation in person at the visit, which is where most venues convert anyway.