Skip to content
Explore the preview
Browse workflow ideas

Offer a supportive moment with clear limits and a real path to help.

Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.

For an adult who knowingly chooses to use a wellbeing support conversation, provide brief reflective prompts and general coping ideas. Explain that the service is not a clinician, therapist, diagnostic tool, or crisis service; collect as little personal information as possible; and do not promise confidentiality beyond the actual service. If someone may be in immediate danger or describes a crisis, encourage them to contact local emergency services or a trusted crisis resource and connect them with qualified human support.

Explore the simulation Explore the idea

Actual availability depends on published steps, supported connections, permissions, and provider approval.

Illustrative workflow and outcome
A person chooses to request general wellbeing supportA private, clearly explained conversation with optional human support
“Respond with empathy without diagnosing, replacing care, or leaving someone alone in a crisis.”
Work through the request.

Clear tasks, with review where it matters.

  1. Explain the service and privacy limits
  2. Offer listening and general reflection
  3. Avoid requesting sensitive personal details
See all 5 tasks
A bounded supportive response with privacy information and an appropriate human or crisis-support route.

What this workflow could do

Responds to selected wellbeing prompts with general empathetic support and reflective suggestions.

Review points proposed in this idea

Automated conversation is not mental healthcare and may misunderstand distress or miss a crisis. Explain privacy and limitations before use, avoid diagnoses and treatment instructions, do not retain unnecessary sensitive details, and provide clear immediate routes to local emergency and qualified human support.

How the idea could work

Select an illustrative task to explore its proposed role. No workflow runs here.

Explore the sequenceStep 1 of 5

  1. Make clear what is stored, who can access it, and that the conversation is not clinical care.

Step 1 of 5

Explain the service and privacy limits

Make clear what is stored, who can access it, and that the conversation is not clinical care.

Proposed setup considerations

These are planning notes for the concept, not instructions for a currently available template.

  1. 01

    State the non-clinical purpose and limits

    Do not market the service as therapy, diagnosis, treatment, or emergency response.

  2. 02

    Set informed consent and privacy controls

    Explain processing and retention clearly and restrict access to sensitive conversations.

  3. 03

    Provide localized crisis and human-support routes

    Keep emergency guidance current for the person’s location and make human help easy to find.

  4. 04

    Test distress and unsafe-response scenarios

    Have qualified reviewers check that the service responds cautiously and escalates appropriately.

Read the prelaunch status

Published templates and verified customer availability remain pending.

A little help with the whole task

A little less busywork.
A little more room for you.

Explore the sample experience while launch details are being finalized.

View pricing status Explore the simulation