Yes. Each missionary's profile carries a giving-page slug and a designated-gift code (which most mission agencies use to make sure gifts hit the right account). The bot reads these and links the supporter to the correct giving page with the correct code already attached. This eliminates the common problem of gifts landing in the general fund when the donor intended to support a specific missionary, which then requires manual re-allocation by the finance team and creates frustration for the donor when they don't see the gift on their missionary's prayer letter.

Yes, when each missionary's profile carries a current-support-percentage ACF field that the development team updates monthly. The bot can sort by gap and surface missionaries closer to their support goal vs further from it. This helps prospective senders who want to support but haven't picked a missionary yet. The bot does not push specific missionaries — it presents the information and lets the supporter choose. Many mission agencies prefer the bot to surface a balanced view (region, ministry focus, family composition) rather than only the gap, and that's configurable in the system prompt.

The bot reads the trip calendar (trips as a custom post type with dates, cost, deadlines, leader contact, prerequisites). When a visitor expresses interest, it captures name, age, prior short-term trip experience, references, passport status and expiration, and any health considerations. The structured intake routes to the trip leader for screening, and the leader handles application and reference checks from there. The bot does not approve participants on its own — that requires actual leader review and reference calls.

Yes. The bot can add a supporter to a specific missionary's prayer-letter list, to a regional list, or to the agency's general prayer list. It reads which lists exist (from your ESP or from a custom-fields setup) and confirms the visitor's email before adding. For agencies using MailChimp, ConvertKit, ActiveCampaign, or FluentCRM, the bot can route through the appropriate list ID. The bot also quotes recent prayer-letter highlights from the published archive when a visitor wants a preview before subscribing.

It answers factual questions from your published candidate resources page (typical support-raising timeline, training expectations, sending-church requirements, theology of support-raising, common Q&A). For prospective candidates ready to start a conversation with the candidate department, the bot captures contact info and routes the conversation to a real candidate counselor. The boundary matters because candidate evaluation is a discernment process that requires real human relationship, not a chatbot. The bot is a front door for information, not a replacement for the candidate counselor's work.

Yes. SleekAI is multibot. Most mission agencies run at least three: a sender-facing bot on missionary directory and giving pages (warm donor-relations tone, focus on impact and field updates), a goer-facing bot on candidate and trip pages (practical, focused on training, support-raising, deployment), and a prayer-partner bot on the prayer-letter and field-update pages (quieter, focused on prayer subscription and recent field news). Display conditions route each visitor to the right bot based on URL pattern or page taxonomy.

Only at the level you publish. For sensitive fields (closed countries, restricted-access regions) the bot uses the same language your website uses — typically aliased field names, no specific missionary identification, no specific city. The bot's system prompt mirrors whatever security model the agency has chosen on the public site. For supporter conversations that need more detail, the bot routes to a real donor-relations conversation with a development officer, who can share details under whatever security agreement the supporter has signed.

Yours. SleekAI is bring-your-own-key for OpenAI, Anthropic, Google, or OpenRouter, and the model bills you directly with no per-message markup from SleekAI. For a mid-sized mission agency with a few hundred missionaries the monthly model cost is usually $15 to $50 in actual API usage. GPT-4o-mini handles missionary directory and trip Q&A well at low cost. GPT-4o or Claude Sonnet for higher quality on donor-relations conversations where the support gift on the line might be $500/month for ten years.