Your instruction defines the success bands. Mid-market RevOps, mid-market IT, and SMB ops typically convert well. Enterprise infosec works but with lower meeting counts. Fortune 100 CIOs, certain regulated healthcare administrators, and niche academic decision-makers rarely work via cold outbound. The bot flags the bad-fit ICPs and refers to partners rather than booking pilots that will fail.

Targets are stated as a range per dedicated SDR per month, tied to the ICP. The bot quotes the band from your services postmeta. SLA structures vary, your instruction can specify whether you offer a meeting-floor guarantee, a refund on missed targets, or a pure best-effort model. Honesty here matters because the industry is full of overpromising agencies.

Yes, ramp is typically 4-6 weeks for a new ICP and a new stack. The bot says so. It also explains what gets done in ramp (sequence build, data enrichment, ICP refinement, sequence testing) so the prospect understands they're not paying for nothing in month one. Setting this expectation upfront saves the third-month churn conversation.

Tell the bot your default stack (Outreach, Salesloft, Apollo, ZoomInfo, Lusha) and what you can flex to if the prospect already has tooling. Some agencies require their stack, others can integrate with the prospect's existing one. The bot answers stack questions accurately based on what you tell it in the instruction.

Yes, shared seats are cheaper but the SDR splits focus across multiple clients, which means lower meeting counts and less product-specific knowledge. The bot explains the trade-off and recommends dedicated for prospects whose ICP requires deep technical conversations, and shared for prospects with simpler outbound motions.

Prospects weighing in-house hire versus outsourced SDR ask this. The bot lays out the math honestly: fully loaded cost of an in-house SDR (salary, OTE, benefits, tools, management overhead) versus the outsourced seat. It doesn't push one way unless the prospect's situation clearly favors one (small team, new motion, or first outbound effort tend to favor outsourcing during pilot).

No, the bot avoids committing to specific named accounts because that requires research the bot can't do in chat. It says so and offers to capture the target account list for a partner to review. This avoids the failure pattern where a prospect joins thinking the agency can hit named-account Fortune 500 logos in week 4.

Conversations are stored in your WordPress database in the SleekAI logs schema. On conversation end, a webhook pushes the transcript, ICP classification, and seat-scope to HubSpot or Salesforce. Partners see qualified pilots arrive with the prospect's ICP and seat expectations already captured, and walk into discovery calls focused on closing.