Yes. Brew-method tags or notes you write feed the prompt for matched recommendations. A V60 brewer asking for fruity gets the Ethiopia Sidamo because you have flagged it as forgiving, not because the bot pattern-matched on Africa. If you write recipe cards per bean, those get retrieved and quoted in the chat with grind and ratio guidance.

If you store roast date as a custom field, yes. The bot keeps freshness answers honest by quoting the actual roast date and contextualizing it — six to nine days post-roast is peaking for filter, eighteen-plus days is past the recommended window. That stops the awkward answer where a customer receives a bag and finds out it was older than the bot implied.

Yes. Multibot plus display conditions lets a wholesale bot live on /wholesale/ with its own prompt. It can quote minimum orders, lead times, and contract roasting capacity from a wholesale-only knowledge base, while staying out of retail conversations. Each bot has its own scope and tone, so wholesale clients do not hit a retail-tuned voice and vice versa.

Add the subscription page to the knowledge base and the bot will quote your plans accurately. Weekly versus biweekly, single-bag versus tasting-flight, ship-day-after-roast versus next-roast-day — all referenced from one source of truth. Pause and skip rules also get retrieved correctly, which keeps the chat from contradicting your churn-saving policies at the moment they matter.

Yes. The system prompt and your tasting notes set the voice. If your bags read with a dry, technical voice, the bot will too; if your house style is warmer and more poetic, it follows that. The grounding data — your tasting notes and brew guides — is what makes the tone feel native rather than a generic corporate-coffee voice that contradicts the bag the customer is holding.

Yours. SleekAI is bring-your-own-key for OpenAI, so the cost-per-conversation sits in your OpenAI dashboard and conversation data is governed by your account. You can swap to a smaller model for high-volume questions, set monthly spending caps, or pause usage during a slow shoulder season without touching the WordPress install or losing conversation history.

Yes, when decaf process and caffeine status are tagged on each bag. Customers asking for low-caffeine after dinner get steered to your Swiss-water decaf or naturally-low-caffeine origins like a Brazil Decaf, with the process explained accurately. Generic bots conflate decaf processes; a grounded bot quotes whether your decaf is sugarcane, Swiss-water, or CO2 because that affects flavor.

Yes. If you publish your in-shop menu as a page or CPT, the bot can answer which espresso and which filter is on the bar today, and what guest beans are featured. Cafe-specific display conditions put that bot on /cafe/ or your locations page, while online retail stays on /shop/ with its own scope and prompt.