It quotes starting prices per tier from your service pages - $2,400 day-of, $5,800 partial, $11,000 full. Final pricing varies with scope - guest count, venue logistics, design complexity, vendor count - so the bot routes to your discovery call after capturing the basics. The starting prices are calibrated against your published tiers, so couples arrive with the right expectation.

Yes. If a couple's budget is below your full planning minimum, the bot recommends a different tier or sets expectations on what's possible at their budget. A couple with a $3,000 budget for full planning gets a polite redirect to day-of coordination, not a hopeful 'let's talk about it' that wastes everyone's time.

Yes. The bot uses your travel and destination policy to quote per region or country and identifies which planner handles which destination. If you have a Tuscany specialist and a Hawaii specialist, the bot routes by the destination the couple mentions. Travel logistics, vendor sourcing in the destination country, and timeline expectations all come from your published content.

It hands off to your discovery call link with couple details, event date, venue, guest count, and tier preference pre-filled where the platform supports URL parameters. Aisle Planner, Honeybook, and Dubsado all support URL parameters; Calendly does too. The booking lives in your CRM with the brief attached, so the call starts at decision-stage.

Yes. The bot reads your tier descriptions and explains the difference in plain language - day-of coordination starts at the rehearsal and runs the wedding day; partial planning includes vendor sourcing 3-6 months out; full planning is design, sourcing, and execution from booking. The phrasing matches your tone, so couples feel like they're talking to your studio, not a generic widget.

It uses the tone of your existing service pages. If your site reads warm and conversational, the bot mirrors that. If it's more editorial and elevated, the bot adopts that voice. The bot does not have a fixed personality - it inherits the personality of your published content, which means cohesion across your website and your chatbot is automatic.

If you publish a vendor referral list - photographers, florists, DJs you trust - the bot can mention them in context. Partial planning couples often arrive looking for vendor recommendations, and a chatbot that names a few photographers you actually work with feels more useful than a generic 'we'll help you find vendors.'

If you publish dedicated pages for elopements, multi-day weddings, or cultural ceremonies (Indian, Persian, Jewish, Chinese), the bot reads them and routes accordingly. Multi-day Indian weddings need different logistics than a one-day American ceremony, and the bot recognizes the language and routes to the right tier and planner.