Yes, as long as those numbers live somewhere on the site. SleekAI reads program impact figures, appeal totals, and overhead ratios from postmeta, ACF fields, or page content. When you update the page with the latest situation report or annual figure, the next conversation reflects the change. The bot does not invent numbers, and the system prompt instructs it to say "I do not have a current figure for that" when a metric is not in the content. That boundary protects credibility with donors and journalists.

Yes. SleekAI detects the visitor's browser language and replies in kind, using the underlying model's translation quality. If your site uses WPML or Polylang, the bot will prefer the existing translated post over machine-translating the English source, so program descriptions, currency mentions, and country names match your approved copy. Most international NGOs run at least English, French, Spanish, and Arabic; SleekAI handles them all without separate bots.

Custom fields on each donation page can store currency, suggested amounts, and the matching processor URL. The bot reads those fields and quotes the right amount in the visitor's local currency, then links to the appropriate donation page or processor (Stripe, PayPal, Donorbox, or a regional gateway like GoCardless for SEPA). Recurring versus one-time options can be presented based on what the page actually supports.

Yes. When an emergency appeal post is published, the system prompt can be switched to reference that post first, so visitors land on the appeal context regardless of which page they entered from. The guideline filter and presets steer conversations back to relief content if a visitor tries to redirect. During appeal traffic spikes, the bot keeps replies short and routes complex media questions to your named press contact rather than improvising.

Yes. Display conditions can vary the bot's behavior by page or by user role. On the press page the bot can prefer to surface the press officer's email and recent statements; on the partners page it can surface the partnerships director and the partner application form. If a logged-in partner staff member visits, the bot can be scoped to internal resources. Conversation logs are tagged with the originating page, so the team can route follow-ups appropriately.

Yours. SleekAI is BYO API key: bring your own OpenAI, Anthropic, Google, or OpenRouter key, and the model bills you directly. There is no per-message markup. For a typical international aid site with steady traffic and an appeal spike a few times a year, monthly model spend usually lands between $20 and $150. GPT-4o-mini or Claude Haiku handles most program questions; larger models are worth it for nuanced press inquiries or multilingual edge cases.

Conversation logs live in your WordPress database, not in a third-party SaaS. The only external call is to your chosen model provider, and you control which provider that is. If your compliance team requires a specific data-residency posture, choose a provider that meets it (for example, Azure OpenAI in an EU region, or an Anthropic enterprise contract). The bot itself reads only the WordPress content you point it at, plus optional OpenAI Files vector store data if you opt into it.

Yes. Partner organizations stored as a custom post type or as a custom taxonomy attached to country posts are part of the bot's context. Visitors asking "who are your partners in Ethiopia?" get the actual list with links to each partner page, rather than a generic "we work with many partners." This matters for both donor confidence and for journalists doing due diligence, because partner specificity is the credibility signal.