Yes. Add your per-state surcharge as a line on the pricing page and SleekAI reads it as context. The bot quotes the base plan, the per-employee fee, and the per-state filing fee separately, so a 14-employee 3-state quote ends up at the actual all-in number rather than 'starting at $40'. State unemployment registration fees, local-tax filings (NYC, Philadelphia, Detroit), and reciprocity rules can also live as separate pages the bot cites when the prospect mentions a specific jurisdiction.

The bot captures the prior provider, the YTD export format, prior-period 941 and state filings, target first pay date, and any active garnishments. That conversation maps to the bureau's published conversion timeline, which usually runs 7-10 business days for clean exports and 14-21 days for messier situations. If the prospect's target pay date is too tight, the bot says so directly and proposes a parallel run with the prior provider rather than promising a timeline the conversion team cannot hit.

SleekAI does not ship native QBO, Xero, or Sage Intacct connectors. It quotes the accounting integration your service already provides and confirms the GL mapping path. Most bureaus already have a built-in QBO or Xero sync at the platform layer (Patriot, OnPay, Justworks, Square Payroll, etc), and the bot's role is to confirm the prospect's accounting stack is supported and to capture the GL mapping requirements for the implementation call.

No, and it is told not to. The system prompt instructs Stub to describe the service, quote the fee, capture the prospect's situation, and book a call, but never to opine on whether a specific employee is W-2 or 1099, whether a state has nexus, or whether the business owes a specific filing. Those questions get routed to a licensed CPA partner or the bureau's payroll specialist. That discipline keeps the bot useful without crossing into work the firm is not licensed to do.

Yes, when your service includes benefits administration. The bot explains the tier, the carriers you partner with, the open-enrollment workflow, and the COBRA handling. For complex benefits questions (ERISA compliance, ACA reporting, 1095 forms), it captures the prospect's situation and routes to a benefits specialist. A bureau without an in-house benefits arm can also configure the bot to refer the prospect to a partner broker rather than pretending to handle it directly.

Add a vertical-specific page (restaurant tip-credit handling, certified payroll for prevailing-wage construction, agricultural H-2A workers) and the bot reads it as context. Tip credit handling, FLSA compliance, certified payroll filings (WH-347), union pension and welfare reports, and prevailing-wage rate sheets each have their own conversation paths the bot follows when the prospect mentions the vertical. Generic chatbots get this wrong because the rules live nowhere in their training data.

Yes, via display conditions or Multibot. Self-service prospects (small businesses, single state, simple W-2 only) can be triaged to a self-serve signup flow, while full-service prospects (multi-state, contractors, benefits) get the longer scoping conversation and a call booking. The bureau can route by employee count, by state count, or by service complexity captured in the early questions, all without writing custom code.

Conversations stay in wp_posts on your install. The system prompt tells Stub to capture metadata (employee count, states, pay frequency, accounting software) rather than SSNs, EINs, or bank details, and the guideline filter rejects attempts to paste sensitive identifiers into chat. Anything that truly requires PII goes through the bureau's existing secure portal after the call is booked, never the chatbot window.