Urgent symptom routing is the first rule in the system prompt. Heavy bleeding, water breaking before 37 weeks, decreased fetal movement, severe headache with vision changes, persistent preterm contractions, or fever all trigger an immediate referral to the client's OB or midwife on-call line, to labor and delivery triage, and to 911 in active emergencies. The bot does not try to assess severity. It is clear that a doula is not a clinician and that those calls belong with the medical provider on the case. This rule is non-negotiable and applies before any package discussion happens.

No. The system prompt explicitly keeps the bot inside doula scope. It does not interpret labor signs, does not coach through contractions, does not give breastfeeding advice that crosses into lactation consultant territory, and does not assess infant feeding in clinical terms. Every clinical question routes to the appropriate provider. This is the only honest scope for a doula chatbot and protects both the practice and the client from advice that should come from a credentialed clinician.

Yes. Publish each package as a page with content, fee, prenatal visit count, postpartum visit count, and any add-ons (sibling care, bereavement support, breastfeeding-focused postpartum, twin support). The bot reads from those pages and quotes the current numbers. Update the page and every conversation reflects the new pricing. The bot will not invent packages you don't offer, because it answers from your published copy rather than a generic doula template.

Yes, if you publish them. Most birth doulas work with a backup or a small partnership, and clients want to know who covers if their primary doula is unavailable. Publish your backup arrangement as a page (named backup doula, partner doulas, agency rotation), and the bot reads from it. The answer is honest and avoids implying a guarantee that isn't real. If you work with a doula collective, the bot can describe the rotation structure too.

Yes. SleekAI is multibot. The birth services pages can run an intake-focused bot with EDD capture and provider name. The postpartum services pages can run a different bot focused on overnights, feeding support within scope, and the first-weeks plan. Sibling and bereavement doulas can have their own pages with appropriate tone and routing. Display conditions ensure each bot only appears on its intended pages without bleeding into the others.

Yes. List each doula on the team with their bio, certification (DONA, CAPPA, ProDoula, BAI), specializations (VBAC support, twins, bereavement, queer-affirming, BIPOC-led), languages spoken, and radius. The bot routes inquiries by specialty and geography, so a queer couple looking for an affirming birth doula and a Spanish-speaking family looking for postpartum support each meet the right person on the first conversation.

Conversations live in your WordPress database. Model calls go to OpenAI, Anthropic, Google, or OpenRouter using your own API key, not through any Sleek-hosted service. Retention is configurable in plugin settings. Intake should capture EDD, birth setting, provider, package interest, and any context that helps the consult be useful, but should not collect clinical detail. For doulas in a HIPAA-adjacent collaboration model with clinical practices, treat the chatbot as an administrative tool.

Yes, in the way doulas always do. The bot captures the client's provider name at intake, and the system prompt reinforces that the doula supports the client and the family, while clinical decisions belong with the OB or midwife. For urgent symptoms the routing always goes to the client's provider on-call line first. This is the only configuration that respects the scope of practice, and it tends to make providers more comfortable with doula referrals because they know the boundary is being enforced even outside the room.