Urgent symptom routing is the first rule in the system prompt. Severe pelvic pain, rapid weight gain, shortness of breath, decreased urine output, or visible swelling after egg retrieval can indicate OHSS and route immediately to the REI on-call line and to 911 in active emergencies. Heavy bleeding or severe pain in early pregnancy after a transfer routes the same way. The bot does not assess severity in chat. It points to the clinical line. This rule applies regardless of what the visitor was originally asking about.

No. Treatment decisions require a full workup (semen analysis, AMH, antral follicle count, HSG, hormone panel, history) and an REI's judgment. The bot describes IVF, IUI, mini-IVF, and donor cycles in general terms using your published copy and routes every case-specific question to a new patient consult. Recommending a protocol from chat is harmful and quickly wrong, and the boundary is in the system prompt for every conversation.

Publish your SART data page with the standard categories (age band, fresh vs frozen, single embryo transfer vs not) and the bot reads from it. The answers reference your published data rather than guessing or quoting national averages. The bot is also clear that individual outcome depends on workup-specific factors and that the new patient consult is the right place to discuss case-specific expectations. This framing matches SART's own guidance about interpreting success rates.

Yes. Publish your fee schedule with each component split out: monitoring, retrieval, anesthesia, embryology base, ICSI, PGT-A, transfer, fresh vs frozen, freezing, and storage tiers. The bot reads from the schedule and quotes the appropriate components based on the program the visitor is asking about. Medication costs are typically separate and reimbursed differently, and the bot is explicit about that distinction. Verification of insurance happens with your financial team, not in chat.

Yes. Donor egg, donor sperm, known-donor, and embryo donation pathways each have different timelines, costs, and eligibility considerations. Publish each as a dedicated page and the bot routes inquiries accordingly. Donor-program inquiries usually route to a separate information call with the program coordinator rather than directly to an REI new patient consult, and the bot reflects whichever flow you've set up.

Yes, and it's a natural fit. Egg freezing intake is more standardized than full IVF intake, with cost being one of the top questions. The bot reads from your fertility preservation page, quotes the cycle and storage fees, explains the medical and elective indications you serve, and books the consult. Some practices add a separate landing for medical fertility preservation (oncology referrals) with expedited scheduling, and the bot routes those distinctly.

Conversations live in your WordPress database. Model calls go to OpenAI, Anthropic, Google, or OpenRouter using your own API key, never through any Sleek-hosted service. Retention is configurable. For a fertility practice under HIPAA, treat the chatbot as an administrative tool. The intake captures enough to route the consult and prepare the REI (age, partner status, workup status, diagnosis if known, insurance) but should not collect detailed clinical specifics.

Via webhook or JS API. SleekAI exposes both, so the chatbot intake can land in eIVF, IDEAS, Babysentry, or any practice management tool that accepts webhook input. Most practices use this to push the intake into a new patient task in the EMR so the front desk can confirm the booking and review the intake before the consult. Smaller practices often have the bot create a WordPress custom post and convert manually.