No. Outcome prediction is the single most dangerous failure mode for a chatbot on a custody site. The system prompt explicitly forbids the bot from estimating which parent will get primary, whether a relocation will be approved, whether a child's preference will control, or what a specific judge is likely to do. Those questions depend on the full file, the local court, and the attorney's judgement, and they belong in the paid consultation, not in a chat reply. The bot frames every relevant answer as general information about the legal framework instead.

Yes. Relocation cases are time-sensitive and high-complexity, and the bot recognises the signals - phrases like 'move out of state', 'job offer in another state', or specific relocation order language. When those signals appear, the conversation shifts: the bot captures the current order, the proposed move, the timeline, and the affected children, then triggers a priority consult booking through your webhook. That routing keeps the cases that need fast action out of the standard calendar.

Yes, when your relocation page lives on your site. State relocation standards vary dramatically - some require a showing of substantial benefit, others apply best-interest factors only, others require the moving parent to overcome a presumption. SleekAI references your published framework rather than baking statutes into a system prompt, so when case law shifts or you refine your firm's positioning, you edit one page and every conversation is current.

Yes. Modification petitions require a substantial change in circumstances under most state laws, and the bot captures the alleged change conversationally: relocation, remarriage, work-schedule change, child's needs change, parent's substance or domestic-violence issue, or order non-compliance. Cases that clearly involve a substantial change route to the consult. Cases that read as venting about a difficult co-parent without a real change get pointed at mediation or parenting coordinator resources instead, which protects the consult calendar.

If a user describes an immediate-danger situation involving a child (active abuse, abduction risk, parent in active crisis), the bot acknowledges the situation, shares 911 and the Childhelp National Child Abuse Hotline (1-800-422-4453), and triggers a same-day callback through your webhook with the urgency flagged. The bot does not attempt to coach the parent through the emergency itself. That routing is configured per firm and pages whoever is on-call for emergency intake.

Conversation logs live in your WordPress database under your control. Custody intake involves children's names, schedules, school information, and sometimes allegations against a co-parent, all of which is sensitive. Most family-law firms purge full logs on a strict schedule (often weekly) and forward summaries to the case management system. API calls use your own OpenAI, Anthropic, Google, or OpenRouter key, so the conversation does not pass through any SleekAI server.

Yes. The bot can describe your firm's parenting plan templates at a high level: holiday rotations, summer schedules, transportation responsibility, decision-making authority for education and healthcare, communication rules between parents, and tie-breaker provisions. It explains why specific provisions matter (the school-enrolment authority question is usually under-thought; the right-of-first-refusal is usually over-thought) without prescribing what a specific family's plan should look like. That prescription is the attorney's job.

Yes. Initial custody cases involve a complete plan being built from scratch and need full intake on parenting capability, schedules, and shared assets. Modification cases need the existing order, the alleged change, and the requested adjustment. The two intakes are different enough that splitting them via Multibot produces cleaner consults. Display conditions route the initial-case bot to your initial-case pages and the modification bot to your modification pages.