top of page

Support Ticket

Fill in the form below to let us know how we can help - we'll get back to you as soon as possible.

What can we help you with?

Support Desk & Safety Operations

How help, accountability, and protection work across the Powell-Rad Path™

The Support Desk exists to ensure that truth-seeking, learning, and repair can happen safely, reliably, and without fear—regardless of role, location, or level of authority.

 

Support is not a punishment system.
It is a stabilization and resolution system designed to protect people, learning environments,

and institutional integrity.

​

A) Support Ticket Types

Choosing the right path ensures faster, safer resolution

 

When submitting a support request, users select the category that best matches their need.

This allows the system to route the request to the correct team immediately.

​

  • Billing & Access
    Payments, invoices, account access issues

  • License, Seats & Roles
    User permissions, facilitator roles, seat assignments

  • Portal & Technical Support
    Login issues, page errors, feature malfunction

  • Data & GDDI Reporting
    Dashboards, metrics, reporting questions, data accuracy

  • Facilitator Guidance
    Cohort flow, curriculum use, ethical facilitation questions

  • Safety Concern (Non-Emergency)
    Retaliation fears, psychological safety concerns, boundary issues

  • Urgent Escalation
    Situations requiring immediate review due to risk or harm

 

B) Standard Support Flow

What happens every time a ticket is submitted

​

  1. Ticket Submission
    A user submits a support request through the official form.

  2. Automatic Queue Assignment
    The system routes the ticket based on its type and urgency.

  3. Acknowledgment
    The user receives confirmation that the request was received.

  4. Triage
    Support reviews:

    • Severity

    • Scope of impact

    • Safety considerations

  5. Resolution & Documentation
    Steps are taken to resolve the issue, with clear documentation.

  6. Closure with Prevention Note
    The ticket is closed with guidance on how to avoid recurrence when possible.

 

This process ensures consistency, transparency, and learning—not blame.

 

C) Severity Levels

 

How urgency is assessed

Support requests are categorized by impact, not by status or role.

​

​

  • S1 – Urgent
    Credible safety risk, harassment, or mention of self-harm

  • S2 – High
    System outages, blocked access, cohorts unable to proceed

  • S3 – Normal
    How-to questions, data clarification, minor bugs

  • S4 – Low

       Feature requests, enhancements, non-urgent suggestions

 

Severity determines response priority, not user importance.

 

D) Safety Escalation Protocol

Non-clinical, responsible, and privacy-first

The Powell-Rad Path™ includes safety protocols because truth work can surface distress. These protocols exist to protect life and dignity—not to diagnose or treat.

​

If a user indicates risk of self-harm:

  • Immediate crisis resources are shown:

    • United States: Call or text 988

    • Emergency: Call 911

  • The user is advised to contact local emergency services

  • Emergency contact(s) on file may be notified (if previously authorized)

  • InstitutionAdmin may be notified only if permitted by policy

  • The event is logged as S1 (Urgent) with minimal necessary detail

  • Privacy and dignity are prioritized at every step

 

Important:

This platform provides safety routing, not medical or mental health treatment.

 

Why This Matters​

  • Everyone knows where to go for help

  • Safety concerns are handled seriously and calmly

  • Power or role does not determine response quality

  • Truth-telling is supported without creating new harm

  • Institutions can operate with confidence, compliance, and care

 

This is how the Powell-Rad Path™ ensures that no one is left alone, unheard,

or unsafe while engaging in truth, learning, or repair.

bottom of page