Yes. Add case studies as a custom post type with vertical, ARR range, channel, and outcome fields. SleekAI reads them as context and surfaces the best-fit case study based on the prospect's situation. A B2B SaaS founder at $8M ARR gets B2B SaaS case studies in the $5-15M range, not an e-commerce case at $30M. The bot can also reference the outcome (traffic, organic-pipeline contribution, ranking gains) in one sentence rather than dumping the full case study.

Each service tier gets its own page: technical audit, content engine, link acquisition, and hybrid retainer. The bot asks two qualifying questions (current organic traffic, biggest perceived gap) and recommends the right starting engagement. JS-rendered sites with flat traffic usually start with technical audits; content-thin sites with rendering already solid start with the content engine; high-DR competitor situations start with link programs. The recommendation is grounded in your service pages, not the model's general SEO opinions.

Yes, when you tell it your retainer floor in the system prompt. If your floor is $7,500/month and a prospect describes a $1,500 budget, the bot says so politely and redirects to a self-serve audit, a recorded webinar, or a partner agency referral. The prospect leaves with a useful next step instead of a wasted hour, and the agency's partner calendar stays focused on engagements that can actually close.

SleekAI logs every conversation in WordPress and most SEO agencies push the transcript and contact details into HubSpot, Pipedrive, or Salesforce via Zapier or webhook on the conversation-saved event. The conversation summary plus the qualifying answers (vertical, ARR, retainer band, organic-traffic baseline) end up as a fully-shaped lead record so the partner sees full context before the discovery call. For analytics, conversation logs include the page URL, which lets you correlate which landing pages produce which inquiry types.

Yes. International SEO has different inputs from domestic SEO: hreflang strategy, ccTLD versus subfolder decisions, regional content strategy, and local link networks. Add a multi-region service page and the bot reads it as context. Prospects with multilingual sites get triaged to a specialist who handles international SEO, and the bot captures target markets, target languages, current hreflang state, and rendering stack as qualifying context for the call.

Programmatic SEO is its own service tier and the bot reads the dedicated page if you have one. The qualifying conversation is different: data inventory (how many entries, what fields, what update frequency), CMS stack (WordPress, headless, Webflow), and template scope (city pages, product alternatives, integration pages). The bot captures those inputs and routes to a programmatic specialist. For agencies that do not offer programmatic SEO at all, the bot can route to a partner agency that does, which preserves the prospect relationship for related work.

Local SEO has very different inputs from technical or content SEO at scale. Service-area businesses care about Google Business Profile optimisation, local citations, review velocity, and geo-targeted content. The bot routes local prospects to a local specialist or to a partner agency if local is not your focus. For agencies that mix national and local engagements, the bot captures the service-area scope, the number of locations, and the current Google Business Profile state as qualifying context.

Yes, and it should. The system prompt encodes the things you do not do (negative SEO, link farms, content farms, AI-generated mass content without editorial oversight) and the bot declines those engagements politely. That discipline is what keeps the agency's portfolio clean and stops the partner team from spending hours scoping engagements that violate Google's guidelines or the agency's own standards. The bot's job is to attract aligned prospects, not to maximise sign-ups.