Skip to content
Prototype · fictional data & simulated workflows · not a live crisis service
Covenant House doveCovCareSeen. Heard. Helped.
Youth home ↗

Roles, responsibilities & connections

How CovCare works.

Every participant has a different path. Each proposed handoff has a decision-maker, a purpose and a privacy boundary.

Entry & authentication

Fictional Connect kiosk; no live fleet is deployed.

Access boundary

Anonymous discovery, language options and accessibility controls.

Unavailable: Previous visitor content, staff records and guaranteed human connection.

Community Kiosk VisitorProposed / fictional storyboard
01

STEP 1 OF 8

Start a clean visit

Confirm the device is at an anonymous starting point.

What the participant sees

Role storyboard: start a clean visit. This is not an operational queue.

What happens next

Continue to choose language after the stated approval.

Decision owner: Visitor / device steward

Information shared

None

Approval required

Approved shared-device configuration

If something goes wrong

If approved shared-device configuration is missing or invalid, stop this step. The responsible visitor / device steward would review an appropriate alternative; the prototype sends no escalation or notification.

Actual current functionality

These controls navigate public documentation only. Operational review, notification, assignment, finance and service fulfillment are not activated. Existing public practice remains separate. This step describes intended design, not a completed operational task.

1/8

Explore the CovCare Vision

Discover how CovCare could connect young people, Covenant House teams, supporters, and community partners through one coordinated network of support.