Yes. Add your VAs as a custom post type with fields for specialty, timezone, tools, and years of experience. The bot reads those as context and recommends the best-fit candidate when the prospect describes the work. The agency stays in control of the final match (the matchmaker can override), but the bot does the first-pass filtering that usually eats coordinator time. If a VA is currently at capacity, mark them as such in postmeta and the bot stops recommending them automatically.

Yes. Add the trial policy as its own page and the bot reads it. Whether the agency runs a free 5-hour trial, a paid 2-week trial, or a re-match guarantee, the bot explains exactly that policy and applies the right pricing. When the policy changes you edit the page once and every future conversation reflects it on the next message. The bot will not invent a trial structure that differs from what is published, which prevents over-promising during intake.

Both. A solo VA running 5-7 retainer clients can install SleekAI on her own portfolio site, point it at her services and testimonials, and let it triage prospects by timezone, tool stack, and task mix. The cost is a one-time plugin purchase plus pennies per conversation in API spend, which is well under the value of a single recovered hour of intake calls per month. The same bot can also surface the solo VA's specialities and case studies, doubling as a portfolio guide.

Not when the system prompt is configured properly. The bot is told to triage out work that is not within scope (full-charge bookkeeping, financial coaching, paid social management) and to point the prospect to a partner or to refuse the engagement politely. That discipline is what keeps the agency's intake clean and stops the trial coordinator from spending hours scoping engagements that were never going to fit.

Timezones are a postmeta field on each VA bio, and the bot reads them when matching. A US-Pacific founder gets US-Pacific or US-Mountain matches; a London founder gets UK or Europe-based matches; an Australian founder gets APAC matches. For overlap requirements ('I need 4 hours of overlap with Pacific'), the bot captures that and filters the roster accordingly. The agency can also include a 'flexible' tag for VAs willing to shift hours, which expands the available roster for hard-to-match requests.

Hand-off is via form, calendar booking, or webhook, so any PM tool with a hosted form works. The bot does not write directly to ClickUp, Asana, Notion, or Trello, it routes the prospect to a hosted intake (or just an email) and your PM tool captures the lead via the existing integration. That separation keeps the data architecture clean and avoids a Sleek-hosted middleware your ops team would have to maintain.

Because the VAs live as a custom post type in WordPress, the bot reads them in real time. When a VA leaves the team, you unpublish her bio and the bot stops recommending her on the next conversation. When a new VA joins, you publish her bio with specialty and timezone tags and the bot starts including her immediately. There is no retraining step or vector-index rebuild; the data is whatever the WordPress query returns.

Conversations live on the agency's WordPress install, never on a hosted SaaS. The system prompt instructs Sidekick to capture metadata (hours, tools, timezone, task examples) rather than confidential project details, and the guideline filter rejects attempts to paste sensitive documents. For agencies serving lawyers, doctors, or fintech founders where NDA-grade handling matters, that on-server architecture is usually the deciding factor over hosted alternatives.