Yes. Each catering package stores per-person rate, headcount minimum, included courses, staffing ratio, and equipment rentals. The bot picks the tier matching the headcount and event type, then quotes the per-person band with included items. Upgrade options (premium proteins, raw bar, passed cocktail hour) live as add-on fields the bot can layer in on request. The quote in chat matches the coordinator's quote.

Yes. Vegetarian, vegan, gluten-free, nut-free, kosher, halal, dairy-free, and any custom dietary classification per package live as structured fields. The bot quotes which alternatives are included at the standard per-person rate, which carry upcharges, and which require advance notice (typically kosher and halal need 7 days). Multi-dietary events (half-vegetarian, several allergies) get a structured response rather than a generic "we accommodate dietary restrictions."

Yes. Calendar availability lives in a booking plugin or Google Calendar sync the bot reads. The bot quotes whether the requested date is open and surfaces 2 or 3 alternative dates if it's booked. Weekend prime dates (Saturdays May-October) usually surface availability for the following weekend rather than the same weekend's Sunday. The same calendar drives the coordinator's scheduling so there's one source of truth.

Yes. Plated dinners typically need 1 server per 12 guests, hot-buffet 1 per 30, drop-off requires no staff. Service ratios per package are stored as fields the bot quotes. Bartender ratios for events with bar service (1 bartender per 50 guests as a default) and chef-attended station ratios (1 chef per 75 guests) layer in. The labor add-on per guest is quoted accurately rather than left as a surprise on the final bill.

Yes, if you store them. Linens, china, glassware, chairs, tables, and bar setups per package live as rental fields. Some packages include rentals (typical for higher-tier plated dinners), others quote them separately at per-event or per-guest rates. The bot quotes the right inclusion based on the package, so the event planner knows whether linens are extra or built in.

Yes. Wedding weekends (rehearsal dinner Friday, ceremony Saturday, brunch Sunday) and corporate retreats (multi-day with different menus per day) capture each day's headcount, menu type, and timing as a structured brief. The bot can quote each day separately and note any package discounts for multi-day bookings if you've configured them. The coordinator gets the full brief rather than three separate inquiries.

Yes. Custom menus, unusual cuisines, and chef-specific requests usually need the chef's input rather than a bot quote. The bot identifies them by intent ("can we do an entirely Korean menu", "my husband only eats raw food") and routes to the chef or coordinator with the brief captured. Standard packages still quote in chat for everything that fits the menu library.

Yours. SleekAI is BYO API key, so you bring an OpenAI, Anthropic, Google, or OpenRouter key and the model bills you directly. There's no per-message markup. A catering company usually spends $15 to $50 a month in API usage. The quote conversations benefit from a stronger model for tone (these are high-trust sales conversations), so some operators step up to GPT-4o or Claude Sonnet on the catering bot specifically.