Yes. Your serving chart is a structured field on the pricing page, or a taxonomy on each tier configuration. The bot reads it and quotes the right combination of tiers for the guest count. A 130 guest reception with a coffee bar usually needs around 100 servings, and the four tier 6/8/10/12 inch round happens to serve roughly 122 wedding slices. The bot does the math from your chart, not from a generic guess, so the recommendation matches what your bakery actually produces.

Yes. Each flavor and filling carries allergen flags (contains dairy, nuts, eggs, gluten, soy) and a description. The bot surfaces them when relevant and includes the cross contact note when your kitchen shares space with gluten or nut products. Celiac safe versus gluten free are different claims, and the bot says "below celiac safe levels is still possible" when the kitchen is shared. Couples appreciate the honesty more than a confident yes that leads to a hospital visit at the reception.

Yes, when the zone and fee structure is in a settings post. The bot quotes the delivery fee for the venue's zip code or town, the setup time required, and any surcharge for stairs or no service elevator. Summer deliveries to outdoor venues add a buttercream alert because buttercream sags above 80 degrees, and the bot mentions the fondant or stabilised buttercream alternative. The couple leaves with a delivered cost, not just a cake price.

Yes, when those options exist. Some bakeries offer fully vegan or fully gluten free cakes; others only do the affected tier as a substitute. The bot reads what you actually offer from the flavor post type and answers accordingly. Pricing for fully gluten free or fully vegan is different from a single substitute tier, and the bot quotes the right structure. Avoiding the "yes we can do that" answer when you actually cannot is exactly what the bot is for.

Yes. Tasting slots live in your calendar plugin and the bot offers what is actually open. The $35 per couple tasting fee, the credit to a full order, and the Tuesday through Thursday window are all surfaced. Flavor preferences captured in the same chat flow into the booking, so when the couple arrives, the kitchen has prepped the right miniatures rather than serving a generic flight that the couple already knew they did not want.

Yes. Each add on is a post or term with a serving count, flavor list, and price. The bot quotes the groom's cake as a flat fee for typical designs and a per serving fee for novelty sculpted work, depending on how you price it. Sheet cakes for back kitchen service are quoted by sheet size with their own serving count, and the bot adds them to the tier estimate when the guest count exceeds the tiered cake's servings. The math stays clean.

Yes, when your portfolio is tagged with styles (modern, traditional, rustic, geometric, floral, fondant, buttercream, naked). The bot can recommend a style based on a two question intake and link to the portfolio examples. Custom design work that requires a separate sculptor or a topper artist is flagged with the upcharge or longer lead time. Couples come away with a sense of fit before the tasting, which makes the design conversation faster on the day.

Yes. A bot can detect urgency from the language (within four weeks, this Saturday, emergency replacement) and route the conversation to your phone or text channel instead of completing the standard intake. Same week wedding cake requests usually cannot be filled, but the bot can offer to check the schedule, and the conversation log fires an alert to the bakery owner so the call back happens fast. Non urgent inquiries flow through the standard tasting booking path.