It uses your published essays and case studies as voice reference. The bot won't sound exactly like you in invented sentences, so the safer pattern is to have it paraphrase your stated views and link to the original. Most prospects prefer that pattern because it feels like a research assistant rather than a clone, and you stay in control of how your positions are represented.

Only the ACF fields you tick are visible to the bot. For NDA case studies, exclude the client name field and the work-in-progress visuals, and the bot will reference the engagement as "a global beauty brand" or similar, with the sector, scope, and outcome intact. You can also gate sensitive material behind a request-access flow that the bot triggers when a serious prospect asks for full samples.

Yes, if you store retainer details in a small custom post type or options page. The bot quotes minimum commitment, monthly investment range, hours included, and what's excluded. Most CDs find that this turns the awkward "what do you cost" conversation into a quick filter, since prospects whose budget is genuinely below the floor self-select out before a discovery call.

Yes. SleekAI display conditions let a different bot run on different sections. The DTC food cluster on your site can have a bot tuned for that sector with its own greeting, while the speaking page can host a separate bot focused on bookings. Both bots read the same WordPress data, but each is instructed differently and surfaces different presets.

It augments rather than replaces. The bot qualifies a lead by asking about sector, scope, budget, and timeline, then routes to your Calendly or contact form with the conversation summary attached. Many prospects who would never fill out a six-field form will engage in chat, and the summary gives you context before the discovery call rather than a vague brief.

SleekAI logs every conversation with model, tokens used, the origin page, and the visitor's referrer if available. That data sits in WordPress and can be exported to CSV. You can also forward conversation events to GA4 or Segment via the bot's webhook config, so sales-attribution dashboards keep working the same way they do for form submissions.

Yes. The bot follows the language the visitor writes in, since the language model handles translation natively. If your portfolio is bilingual using WPML or Polylang, SleekAI maps to the translated post variants so the bot quotes the right language version of a case study. You can also force a specific language per page using display conditions.

OpenAI, Anthropic, Google Gemini, and OpenRouter are supported out of the box, with their full model lineup. You bring your own API key, so usage costs go directly to that provider rather than being marked up. Most CDs use Claude Sonnet or GPT-4 class models for nuanced portfolio conversations and a cheaper model on speaking pages where answers are more transactional.