No. SleekAI is configured to refuse stage-model interpretations and to avoid telling a grieving person what their grief means or what is normal. Those frameworks are clinically dated and not how most contemporary grief counselors work, and even if they were, interpretation from a chat conversation would be inappropriate. The bot answers operational questions and books a consult with a licensed counselor who can have that conversation properly. The boundary is in the system prompt and applies consistently.

Crisis routing is the first rule in the system prompt. Any indication of suicidality, self-harm, or acute distress triggers the bot to share 988 (the Suicide and Crisis Lifeline) and to recommend local emergency services for active danger. The bot does not try to talk a person through a crisis itself, it points to live human help available 24/7. This rule always takes precedence over any other instruction, including continuing a program-detail conversation the visitor was already in.

Yes. Add loss-type specializations to each counselor's profile as custom fields (loss of parent, partner loss, child loss, perinatal loss, complicated grief, traumatic loss, suicide loss), and SleekAI routes accordingly. A perinatal loss inquiry goes to the perinatal-loss specialist, a suicide loss inquiry goes to the suicide-loss specialist. The match is conversational, which lets the visitor share context without filling out a long form before they know who they'll be working with.

Publish your group schedule with cohort dates, population, and capacity. The bot answers the predictable questions (when the next cohort starts, who it's for, whether spots remain) and routes the visitor into enrolment through your booking widget. If a group is full, the bot offers the next cohort or a waitlist signup, and never makes commitments your schedule doesn't support. Group facilitator names and credentials come from the published page.

Yes. The intake script branches on whether the inquiring person is the bereaved adult or a parent seeking help for a child. The child path captures different details (age of the child, time since loss, what the parent has noticed) and routes to the counselor on staff who focuses on child and adolescent bereavement work. The parent always remains part of the conversation about a child's care, and the consult is structured accordingly.

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, and most practices set short retention given the sensitivity of the content. For a practice handling PHI under HIPAA, treat the chatbot as an administrative tool. The intake captures enough to route the consult, not enough to be a clinical record.

The bot doesn't make clinical distinctions, but it captures the time since loss as part of the intake so the counselor has context before the consult. Some practices use this field for routing too, particularly if certain counselors focus on acute bereavement and others on complicated grief that has persisted for longer. The bot reads the routing rules from your therapist profiles rather than from any built-in clinical model.

Yes. Publish a resources page with grief support organizations (the Dougy Center, GriefShare, hospice-affiliated support groups, local community programs), and the bot shares relevant items based on context. This matters because not every visitor is ready to book a consult on the first conversation, and a quiet offer of community resources can be the right help in that moment. The bot never replaces those resources, it just makes them findable.