Yes. Practice areas live on your services pages or as a custom post type, and SleekAI pulls them into the system prompt as context. The bot confirms practice-area fit before booking anything, so a hiring client asking about a niche outside the firm's coverage gets a polite "that's outside our focus, here's a peer firm you could reach out to" rather than landing on the calendar as a wasted call.

Candidates get their own track: the bot captures function, sector, location, current role, and comp range cleanly, then either points them to relevant active mandates (where publicly listed) or adds them to the talent database with full context. Most firms run a Zapier or webhook trigger that pushes candidate intake into Invenias, Clockwork, or whichever ATS the firm uses, so the candidate record appears with profile already shaped.

Yes, when the firm wants it to. Retainer scale (one-third structure, fixed-fee, or hybrid) lives in postmeta or on a services page, and the bot quotes the structure plus the typical engagement length for the practice area. Many firms prefer to keep specific dollar figures off the public bot and only quote ranges; the system prompt accepts that constraint and the bot defaults to "we typically run a one-third retainer; specific scale depends on the role" instead of a number.

Confidential mandates stay off the bot entirely. Public retained searches can be surfaced if the firm has them listed on the site (some do, most don't). For confidential searches, the bot is configured to say "we have an active mandate at that level but we can't discuss it publicly; the partner will follow up" rather than pretending no relevant search exists. Conversation logs stay on the firm's WordPress install, not a third-party SaaS.

Yes. Case studies live as a custom post type with sector and function taxonomies. SleekAI filters by taxonomy, so a SaaS CFO inquiry surfaces SaaS CFO placements and a healthcare CEO inquiry surfaces healthcare CEO placements. For long case study libraries, the OpenAI Files vector store handles retrieval, so the bot picks the most relevant two or three rather than listing every search the firm has run.

SleekAI logs every conversation in WordPress, and search firms typically use a Zapier or webhook trigger to push transcripts into Invenias, Clockwork, Bullhorn, or HubSpot. Candidate inquiries route to the ATS as profiles; client search briefs route to the CRM as opportunities. The conversation summary plus the qualifying answers end up as a fully-shaped record so the partner walks into any follow-up with the full picture.

BYO API key means OpenAI, Anthropic, Google, or OpenRouter, your choice. For most search firm sites a mid-tier model handles the qualifying conversation, since the bot mostly retrieves practice-area context and asks shaped questions. If the firm wants more nuanced handling of senior candidate inquiries (where tone matters more than retrieval), a stronger model is worth the spend, and token usage is logged per conversation so the cost picture is clear.

Within limits. The bot can take a basic profile (function, sector, comp range) but is configured not to discuss specific candidates by name, specific compensation negotiations, or any matter that should sit with a partner. Sensitive conversations get routed to a partner with a same-day SLA rather than continued in chat. That discipline is what makes deploying AI on a search firm site safe rather than reputation-damaging.