No. The chatbot never touches the raw document. When the user is ready to upload, SleekAI hands the session over to your KYC provider's hosted capture flow (Onfido, Persona, Sumsub, Jumio, or your own) and waits for the result via webhook. The bot is the conversational layer on top of an existing identity stack, not a replacement for it.

Map your verification state to a user meta field (for example kyc_status) and SleekAI reads it at the start of each turn. If the value is id_uploaded the next prompt is the selfie. If it is address_pending the bot asks for a utility bill. Branching is configured in the chatbot's system prompt and display conditions, not hard-coded.

Yes. Use multibot to run a UK KYC bot, an EU KYC bot, and a US KYC bot, each with its own system prompt covering the local document types, address proof rules, and enhanced due diligence triggers. Display conditions on the page or the user's country attribute decide which bot loads.

Every conversation is logged with user ID, timestamp, model, token count, and origin page. For five-year retention or audit-trail requirements, the logs live in your WordPress database where the rest of your customer records sit, not on a third-party SaaS. Export to CSV or push to your data warehouse from there.

Compliance copy belongs in the system prompt, not in the model's general knowledge. Spell out exactly what documents are accepted, what timeframes are valid, and what to refuse, then instruct the model to defer to a human when a user asks a question outside that scope. The conversation logs let you tighten the prompt as edge cases surface.

SleekAI is a one-time WordPress plugin license. You bring your own OpenAI, Anthropic, Google, or OpenRouter API key and pay the provider directly at standard rates. There is no per-verification fee, no resolved-conversation pricing, and no monthly seat cap. KYC vendor costs are separate and unchanged.

Yes. Configure a tool or webhook that creates a ticket in your support system (Zendesk, Help Scout, Freshdesk, or a custom queue) when a user fails liveness twice, asks for a manual review, or has a high-risk flag. The bot tells the user what to expect and the case lands in front of a compliance officer with the full transcript attached.

The same model applies. The bot reads which entity type the user picked at signup, then follows the corporate branch: incorporation document, ultimate beneficial owner list, proof of address for the entity, and signatory verification. Multibot lets you run a separate KYB bot if the prompts diverge too much from the retail flow.