No, and this is the most important guardrail on the entire chatbot. The system prompt instructs SleekAI to share general family-law education, your fees, and your process, never specific legal recommendations about a particular family's situation. When a prospect pushes for a 'should I' answer, the bot explains how cases typically work, frames the actual recommendation as something the attorney makes in the paid consultation, and books that consultation. That separation is what keeps the firm clear of UPL exposure while still letting prospects do the research they came to do.

Yes. Multibot lets you run an uncontested-divorce bot on uncontested pages with flat-fee framing and a contested-divorce bot on contested or high-asset pages with retainer framing. Each bot has its own intake script, its own routing rules, and its own consult fee, so the prospect lands in the right conversation and the attorney handling the matter gets the right structured details. Custody modification, post-judgment enforcement, and prenups can each run as their own scoped bot.

Yes, when those rules live on your site. SleekAI references your published pages rather than baking statutes into a system prompt, so when your state adjusts mandatory waiting periods, parenting class requirements, or financial disclosure forms, you edit one page and every conversation is current. Multi-state firms can configure state-specific bots using display conditions so the Texas pages get Texas framing and the California pages get California framing.

Conversation logs live in your WordPress database under your control. Family law intake involves marital details, children's information, and asset disclosures that are sensitive, so most firms purge full logs on a strict schedule (often weekly) and forward summary emails to the case management system through a webhook. API calls use your own OpenAI, Anthropic, Google, or OpenRouter key, so prompts and responses do not pass through any SleekAI server.

No. Child support amounts depend on state guidelines, income from both parties, parenting-time allocation, healthcare costs, and child-care expenses. The bot points prospects at your state's official guideline calculator and explains the inputs at a high level, but it never produces a number on its own. The attorney runs the actual calculation in the consultation with verified income documents in hand. That boundary is non-negotiable on a family-law site.

Yes. The system prompt detects DV indicators (immediate danger, restraining order language, recent incident keywords) and shifts tone immediately: the bot acknowledges the situation, provides the National Domestic Violence Hotline number (1-800-799-7233) and 911 for immediate danger, then routes the conversation to a same-day callback through your webhook instead of running the standard intake. That callback path is configured per firm and triggers a Slack ping or SMS to whoever is on-call.

Yes. The bot can describe your firm's mediation process, collaborative divorce option, and four-way settlement meetings at a high level using your published service pages. It explains the cost difference between mediation and litigation, the typical timeline, and which cases tend to fit each path. As with every other topic, the actual recommendation about which path is right for a specific family stays in the attorney's office where it belongs.

Yes. Multibot supports separate bots for divorce, custody and visitation, child support modification, prenups and postnups, adoption referrals, and DV protective orders. Each runs on its own URL pattern via display conditions, with its own intake questionnaire, consult fee, and routing rules. That separation matters because a prenup intake asks completely different questions than a contested custody intake, and conflating them produces messy consults.