Urgent symptom routing is the first rule in the system prompt. Heavy bleeding, decreased fetal movement, severe headache with vision changes, persistent preterm contractions, suspected rupture of membranes with concerning signs, fever, or any other red flag triggers an immediate referral to your on-call midwife line, to labor and delivery triage at your transfer hospital, and to 911 in active emergencies. The bot does not try to assess severity itself. This rule applies regardless of what the visitor was originally asking about and is non-negotiable.

Only what you publish. Each credential has a different state-by-state scope and different practice rights. Publish a credentials page that describes the credentials your midwives hold and what they can do at your practice, and the bot reads from it. SleekAI doesn't ship with a built-in regulatory model, so the scope answers reflect your published copy rather than any guess about state-level law. This is honest and avoids the kind of misstatement that a generic bot makes when it tries to summarize midwifery regulation in general terms.

Yes. Publish your fee schedule and payer policy as a page. Most midwifery practices have a global maternity fee with sliding scale options and a defined Medicaid policy (some accept it, some don't, some accept it at certain sites only). The bot quotes from that page and is explicit that final verification happens at intake. This is also where most birth-center vs home-birth fee differences live, and the bot reads them from the same source.

Yes, if you publish the collaboration model. List your OB partner practice, the consulting OB who handles risk-out cases, and the transfer hospital with its labor and delivery line. The bot can share the OB partner's name in contexts that warrant collaborative consultation (VBAC, twins, advanced maternal age), and direct urgent calls to the on-call line and L&D triage. The relationships come from your published page, not from any built-in directory.

Yes. Publish your VBAC policy: which midwives take VBAC clients, what the screening criteria are, whether VBAC is offered at home, birth center, or hospital only, and how collaboration with the OB partner works. The bot answers from that page and books a consult for case-by-case evaluation. The bot never tells an individual visitor whether they are a VBAC candidate, that decision belongs to the midwife after reviewing records.

Yes. SleekAI is multibot. The prenatal pages can run an intake-focused bot with consult booking. The postpartum pages can run a different bot focused on lactation visits, postpartum visits, pelvic floor referral, and PMAD screening. The conversations are not the same and trying to fit both into one prompt produces a worse experience for new clients and established ones alike. Display conditions ensure each bot only appears on its intended pages.

Conversations live in your WordPress database. Model calls route to OpenAI, Anthropic, Google, or OpenRouter using your own API key, never through any Sleek-hosted service. Retention is configurable in plugin settings. For a HIPAA practice, treat the chatbot as an administrative tool and avoid asking for clinical specifics in chat. Intake should capture enough to route the consult or the urgent call, not enough to be a clinical record.

Yes. The same patterns apply with slightly different routing: scope of practice within the hospital, which midwives are on staff, how labor admission works at the hospital, and how the practice integrates with the OB group. Hospital-based practices often emphasize collaboration upfront and the bot can reflect that on the relevant pages, while routing urgent symptoms to the L&D triage line directly rather than to a practice on-call number.