Yes, at the level your practice has authored on the modality page. SleekAI reads your published copy, so the explanation matches what visitors see elsewhere on the site. The bot describes the 8-phase protocol, the role of bilateral stimulation, and the importance of preparation and stabilisation before any processing begins. It does not invent mechanism claims or extrapolate efficacy figures beyond what the practice has authored. Whether EMDR is the right starting point for a specific person is left for the consultation with the therapist.

No. The system prompt is configured to never ask about target memories, never request trauma history, and never push the conversation toward processing content. EMDR pacing is the therapist's job, and the chatbot stays scoped to fit, pacing, certification level, format options, and booking. The boundary holds across every conversation regardless of how the visitor frames the question. The actual history conversation is reserved for the consultation with a licensed clinician who can pace it appropriately.

988 (the US Suicide and Crisis Lifeline) routing fires before any other flow when distress signals appear. The bot recognises hopelessness, self-harm ideation, dissociation cues, or descriptions of crisis and leads with 988 and the local emergency line. Most EMDR practices add language about the Crisis Text Line (text HOME to 741741) and the nearest emergency department. Booking and practice information are secondary to safety. The system prompt enforces the order on every conversation.

Yes, when each therapist is tagged in custom fields. The bot reads basic-trained, EMDRIA-certified, Consultant in Training, and consultant status into the prompt and quotes the level accurately. Visitors often ask specifically about certified status (which is meaningful because it requires post-training consultation hours and case review beyond the initial basic training), and the bot answers honestly rather than fudging the distinction. Certification level is one of the practical markers visitors use to evaluate fit.

Yes, when intensives are described on your published pages and each therapist's availability is tagged in custom fields. Intensives have a different intake pattern from weekly work: structured preparation sessions before the intensive day(s), the intensive itself (typically half-day or two-day formats), and integration sessions after. The bot quotes pricing and timeline for each component, and explains that the decision between intensive and weekly format comes from the consultation, not at chat time.

Tag each therapist's experience with dissociative disorders and complex developmental trauma in custom fields. The bot routes accordingly because dissociative work requires substantially more preparation and stabilisation than single-incident trauma, and not every EMDR therapist takes complex cases. The bot is configured to be conservative on this point: it routes to the therapists with documented experience and notes that the consultation will determine readiness, rather than booking a complex case with a therapist who specialises in single-incident work.

Yes, in your WordPress database. Retention is set through the plugin, typically 7 to 14 days for EMDR specialty practices given the sensitivity. Conversations stay on your server, OpenAI or Anthropic calls use your own API key directly, and there is no SleekAI proxy. Most practices also forward conversation summaries to their EMR through a webhook and purge raw logs on a strict schedule appropriate for the privileged nature of trauma intake inquiries.

Yes. The 28+ display conditions let you scope the chatbot tightly to booking-intent pages (contact, fees, therapist bios, new clients, intensives) and hide it on the longer EMDR-explainer and blog pages. Visitors reading those are often in research mode, sometimes preparing to reach out to a different practice, and forcing chat onto them can feel intrusive. The scoping respects how visitors actually use specialty trauma sites, where reading is part of the help-seeking process.