Yes. Any ACF, Meta Box, or native post meta field can be included in the chatbot's context, including client name, results, tools used, timeline, and budget range. Each field is opt-in, so you choose exactly which fields the bot can quote and which stay private. Most studios start by exposing scope, deliverables, and outcomes, and skip internal notes and rate cards.

Only fields you explicitly add to the context are visible. Internal or private custom fields stay out, and the system prompt can also instruct the bot to refuse pricing questions and route them to a discovery call instead. If a rate is not on your site, the bot has no way to invent one because it draws from your published content.

Display conditions let you hide it on the homepage hero, on landing pages with their own conversion goals, or on any specific URL while keeping it active on case studies and service pages. Most studios run it on the about, services, and individual project pages, and turn it off everywhere else.

The system prompt can include direct links to Cal.com, SavvyCal, Calendly, or any hosted form so the bot routes leads to the right place. You can route different inquiry types to different links, for example a discovery call for new prospects and a longer scoping call for warm leads who have read the case studies.

Multibot lets you set a project-specific bot per case study so it behaves like a guide for that single piece of work. The visitor asking 'what tools did you use' on a brand identity case gets answers about that project's stack rather than a generic studio overview.

Even with five or six projects, SleekAI saves visitors from scrolling and helps you understand what people actually want to know. Solo freelancers with a single services page often get more value than agencies because every conversation is data about how to position the next iteration of the site.

Conversations are stateless by default to keep things private, but a returning visitor on the same browser sees their prior thread. If you want longer memory tied to email or a CRM, the system prompt can ask for an email and pass it to your tool of choice via webhook, while the chat itself stays inside WordPress.

It is safer to fail gracefully than to invent. The default behavior is to say it does not know and offer the booking link or contact form, which is exactly what a smart studio assistant would do. The system prompt can also instruct it to recommend specific resources or case studies as fallbacks for common gaps.