The bot drives intake but does not decide outcomes. Coverage decisions, payouts, and liability still flow through a human claims handler. SleekAI's role is to capture structured data with full audit logging, which most regulators prefer to a paper form or a tired customer-service rep typing into a Word doc. Always run the prompt past your compliance team.

Map your policy CPT and customer table into the prompt. The bot reads policy_number, policy_status, coverage_type, and excess_amount. If the policy is lapsed, the coverage doesn't include the claim type, or the customer doesn't match, the bot says so up front and refers to the renewal or coverage team instead of forcing a doomed intake.

The chatbot widget supports file attachments that flow into the WP Media Library. SleekAI links them to the claim record via claim_attachments postmeta. The bot can request specific photos ('source of leak', 'damaged contents', 'license plate') and confirm each upload before moving on, so handlers don't open a claim missing the key evidence.

Yes. The system prompt branches on cause (water, fire, theft, accidental damage) and asks the questions a human adjuster would. Water needs source, shut-off time, secondary damage. Theft needs police report number, time discovered, list of items. The branching is in the prompt, not in custom code, so adjusting it is a 5-minute edit.

Customers log in to their policy portal before opening the bot, so user ID and email are already known. For phone-channel claims, layer on date of birth and policy number cross-check. The bot can also trigger an SMS one-time code via a Tool Use endpoint if higher assurance is needed before sensitive disclosures.

If your claims platform exposes an API, the bot can post the structured claim via a Tool Use endpoint. If it doesn't, the claim sits in WordPress as a CPT and gets exported nightly via CSV or webhook. Many insurers start with WordPress as the system of record for chat-initiated claims and migrate downstream when integration capacity opens up.

SleekAI is a one-time WordPress plugin license. You bring your own OpenAI, Anthropic, Google, or OpenRouter API key. A typical claim intake conversation costs a few cents in API. Compared with the labour cost of a first-notice-of-loss call (often 15-25 minutes of an agent's time), the ROI is immediate.

The bot captures the standard structured data and explicitly hands off when the claim's value or complexity exceeds a threshold (multi-vehicle accidents, total losses, bodily injury). It collects what it can, flags the case, and routes to a senior handler with full context attached. Don't try to fully automate the cases that benefit most from human judgement.