HR consultancies usually run six or seven distinct service lines: comp design, employee relations investigations, policy and handbook work, M&A integration, leadership development, DEI, and HRIS implementation. Each one needs different qualifying questions and routes to a different lead in the firm. A single contact form treats them all the same. SleekAI runs the right conversation for each on the page itself, so engagements land shaped instead of generic.

The bot reads your service descriptions, your engagement models (project, retainer, advisory), your typical fees, and your case studies from WordPress (post types, ACF fields, taxonomies, the data-source wizard maps each shape). When a Series B founder asks about comp design, the bot describes the typical engagement (job architecture, banding, equity refresh), quotes the fee range, and books a scoping call with the comp lead. When a board asks about an employee relations investigation, the bot routes to the ER partner with the right confidentiality posture from the first message.

BYO API key means OpenAI, Anthropic, Google, or OpenRouter and you pay only your provider. Conversation logs stay in WordPress with model name, token usage, and page URL, so the firm sees which service pages generate which inquiries. The bot is the qualifying conversation a senior associate would run if they had time to staff every page 24/7.

HR consulting is one of those B2B services where the firm's website often does the least specific work because the firm's actual service mix is the broadest. A single firm might do comp design for a Series B SaaS one week and an M&A integration for a Fortune 500 the next, and the contact form has to support both. Most firms compromise by writing a generic services page and a generic contact form and then absorbing the triage work in the partner's inbox.

That works, but it loads cost onto the most expensive resource in the firm. A chatbot that identifies the service line from the first message and runs the right qualifying conversation for each replaces the triage layer entirely. The biggest win is the service-line split.

A comp design inquiry needs different qualifying questions (current banding, equity strategy, sales comp, total team size) from an HRIS implementation (current system, headcount band, timeline, integration scope) from an ER investigation (timing, scope, internal versus external counsel, geography). Treating all three the same with a generic form is what produces the "so tell me about your situation" opening on every scoping call. A bot that already knows which service line is in play opens the call with "you mentioned you're scoping a Series B comp engagement before your next round, what's the current state of the banding?" The conversation starts twenty minutes ahead of where it would otherwise start.

The confidentiality posture for ER work is the second big win. Employee relations conversations have a different tone in person than comp design conversations, and a generic chatbot cannot calibrate. A system prompt that recognises ER inquiries and shifts the posture (no employee names in chat, no specific allegations captured, immediate partner routing with same-day SLA) lets the firm deploy AI even on the most sensitive service line without creating new exposure.

And because the conversation logs sit in WordPress with the model name, token usage, and page URL captured, the firm gets a structured view of which service-line pages generate which kinds of inquiries, which is invaluable for marketing investment and editorial planning.