Yes. SleekAI's data mapper lists every custom post type and ACF field on your site and lets you tick which ones the bot can see. Case study fields like client name, industry, deliverable type, and outcome metric become readable in seconds. You're not writing a schema by hand or maintaining a separate knowledge base, since the bot reads the same posts you edit in the WordPress admin.

Yes. Pick the ACF fields the bot can see and exclude the client name field for NDA work. The bot still references the industry, scope, and outcome, but says something like "a Series B fintech" instead of the real name. You can also gate full samples behind a request-access flow that the bot triggers when a prospect asks for sensitive details.

Rates live in a simple custom post type or options page that you control. The bot reads day rate, minimum engagement, rush surcharge, and retainer terms verbatim and quotes them when asked. Update the values once in WordPress and every page that hosts the bot reflects the change immediately, so you stop having stale rate cards drift across PDFs and Notion docs.

It uses your published voice samples as reference material. If a prospect asks for a playful tone for a kids app, the bot cites a real sample from a similar audience. It will offer to generate a short demo line on request, but the answer is always anchored in work you've actually shipped rather than a sample invented by the model from scratch.

Yes. If your case studies tag deliverables as onboarding, error messages, empty states, marketing emails, or notifications, the bot filters answers to that scope. "Have you written push notifications for a wellness app?" returns only matching case studies, ordered by recency. This is faster than scrolling a portfolio grid and prospects feel like they're getting a curator's answer.

It augments rather than replaces. The bot qualifies the lead by asking about budget, timeline, and scope, then routes to your existing contact form or Calendly link with the conversation summary attached. Prospects who weren't going to fill out a form often will engage in chat, and the conversation log gives you context the contact form alone wouldn't capture.

Logs sit on your own WordPress database and are only readable by users with the role you specify. Since you provide the API key, prompts and replies go directly between your site and your chosen model provider, with no intermediate vendor storing the content. You can also redact logs by IP, email, or content match if a prospect later requests it.

Yes. Display conditions in SleekAI let you scope a bot to a specific post, category, or URL pattern. The home page can have a generalist bot, the fintech case studies cluster can have a tone-tuned variant, and a course landing page can have a third bot focused on enrollment questions. Each bot has its own instructions and data mappings, but they share the same WordPress data and account.