Yes. Most soup kitchens keep the meal schedule on a single visit page or as custom fields on the homepage. SleekAI reads those fields directly through the data-source wizard, so the bot's answers stay in sync with the website. Add a Friday brunch service or shift Thursday from 5:30pm to 6pm, and every conversation reflects the new schedule immediately, with no retraining or redeployment required on the chatbot side.

Yes, and this is one of the most important configurations. Guests should never be asked for ID, asked about their housing situation, or pushed toward a donation pitch. The system prompt enforces a warm, plain-language tone for visit questions and routes any donation or volunteer pitch out of the guest-facing answers. Most soup kitchens add an explicit "no questions asked" line to the system prompt so the bot reproduces it whenever a guest hesitates about whether they qualify.

It cannot process payments directly, but it can answer questions about gift levels, recurring options, and tax deductibility, then link to your existing donation form with the right amount and frequency preselected. The bot stays out of the payment flow, which is what your donation processor handles. Most soup kitchens use SleekAI as the conversational layer in front of GiveWP, Donorbox, or a parish donation system, with the existing checkout doing the heavy lifting.

Yes. Most soup kitchens cannot accept opened, expired, or homemade items, and most cannot accept fresh meat from individuals without a temperature-controlled handoff. Putting the do-not-accept list in the system prompt as a hard rule means the bot warns donors before they drive across town with a bag the kitchen will have to discard. The list is editable through a standard WordPress page so the program director can adjust it seasonally or based on health-department guidance.

Yes. Many soup kitchens host adjacent recovery or housing programs whose pages should not carry a chatbot prompting for donations or volunteer signups. Display conditions let you hide the bot on those pages by URL, post type, taxonomy term, or template. The conditions cover URL, post type, page template, user role, device, and time of day, so you can scope the bot precisely to the pages where it actually helps.

SleekAI is sold as a standalone plugin or as part of the All Access Pass. If you are a registered 501(c)(3) or a parish-run kitchen, email us with proof of status and we will work something out. The API cost is paid directly to OpenAI, Anthropic, Google, or OpenRouter on your own key, so there is no per-message markup from us either way. Most soup kitchens spend $10 to $30 a month in actual API usage.

Inside your WordPress database. Nothing is shared with Sleek or any third party beyond the API calls your key authorizes. You decide retention, you decide who can see logs, and you can purge old conversations on a schedule. Each log records the model name, token usage, and page URL, which is useful for spotting repeating volunteer questions that suggest the volunteer page needs a rewrite, or that a specific shift type needs more onboarding context.

Yes. The system prompt and context adapt per language, and WPML or Polylang content is honored. A guest reading the Spanish version of your meal-schedule page gets Spanish answers drawn from Spanish content. Most urban soup kitchens run English, Spanish, and one or two community-specific languages, and the language-matched answer raises the chance a guest actually walks in to dinner rather than guessing whether they read the schedule correctly.