Yes. The system prompt can encode rules like "Series A SaaS retainers go to alex@, ecommerce projects go to mara@, audits go to the audit form" and link the appropriate intake URL. Routing also handles budget thresholds, so inquiries below a minimum can be sent to a self-service audit form while inquiries above route to a partner intake call. Updates happen in the prompt, not in code, so the agency can iterate as the team and book of business shift.

Hand-off is via form or hosted intake link, so any CRM with a hosted form is supported. The bot does not write directly to the CRM. It captures the brief in conversation, summarizes it, and routes the prospect to the right intake URL, which then writes to the CRM with the correct pipeline and stage. This keeps the data architecture clean and avoids a middleware layer for legal to evaluate.

Only what's already public on the site. Internal-only fields stay invisible because they're not part of the data source. The system prompt can also instruct the bot to refuse pricing questions and route them to a discovery call, which is how most agencies handle this today. Visitors never see retainer minimums you haven't chosen to publish, and the bot won't invent a number.

SleekAI is licensed per site. Many growth agencies install it for their clients on retainer; talk to us about an All Access Pass arrangement that covers multiple client sites under a single account. The widget is brandable per install with colors, logo, avatar, and tone, so a client's chatbot reads as part of the client's brand rather than carrying agency or Sleek branding.

Engagements flagged confidential in the ACF panel can be referenced in abstract terms ("a Series B fintech client") the same way they appear in a sales deck under NDA. The bot will not invent client names or details, and the system prompt can explicitly forbid disclosure of unpublished engagements. Verifiable, published case studies are quoted with the client name; gated ones are described categorically.

On the agency's WordPress install, stored alongside model name, token usage, and page URL. Retention and export are controlled at the WordPress level, and a webhook can pipe high-intent conversations to a partner-only Slack channel for real-time inbound. For agencies with strict client confidentiality commitments, the fact that conversations never touch a third-party SaaS is often the deciding factor.

It can summarize what a prospect described and email it to the partner who owns the segment, which gives them a head start on the proposal. It will not generate full scopes of work autonomously, because pricing and scope decisions belong with the partner, not the chatbot. The bot's job is to capture the brief and route it to the right human, fast, not to commit the agency to a number.

Yes. SleekAI follows the language of the page and visitor input and works alongside WPML and Polylang. An agency with English and German service pages can run a single chatbot that replies in either language, drawing from each language's content tree. Tone can be set per language in the prompt, for example more formal in German, warmer in Spanish.