Trust & safety

Admissions automation with clear human boundaries.

Finnor is built to capture missed, overflow, and after-hours admissions moments while keeping decisions, judgment, and escalation ownership with the treatment center.

Operating boundary

Human team owns next steps

Approved script
Urgency route
Unknown stays unknown
Structured handoff

Boundary 01

Human admissions teams stay in control

Finnor prepares context for the admissions team. People remain responsible for rapport, eligibility, clinical judgment, and next steps.

Boundary 02

Finnor does not diagnose or recommend treatment

The workflow is designed for non-clinical intake capture and handoff. It does not make diagnoses, treatment recommendations, or admissions decisions.

Boundary 03

Urgent language routes to human escalation path

Centers define the escalation path for urgent or concerning language. Finnor flags that language and routes it according to the approved process.

Boundary 04

Center-approved scripts and knowledge boundaries

Pilot scripts, intake questions, and knowledge boundaries are approved before use so the system stays within the center's operating model.

Boundary 05

Public-info-only demo builder

The personalized demo builder uses public website information and user-provided inputs. It is not a production deployment or a claim about private systems.

Boundary 06

Unknown fields stay marked unknown

If a caller does not provide a field, the handoff should show that it is unknown rather than inventing or assuming an answer.

Boundary 07

Data minimization during pilots

Pilots should collect only the information needed to test call capture, structured summary, escalation, and follow-up workflow.

Boundary 08

Scoped deployment before production

Finnor is intended to start with a defined routing scope, reviewed scripts, test scenarios, and clear handoff ownership before broader use.

What Finnor does not replace

The center remains the decision-maker.

A licensed clinical team
Admissions judgment
Eligibility or insurance verification
Emergency services
A center's compliance program
Human follow-up with callers and families

Compliance note

Compliance depends on final deployed stack and agreements.

Trust and compliance are not created by copy on a website. They depend on the final routing, data handling, vendor agreements, access controls, retention settings, and the center's own policies. Finnor's pilot process is scoped so those decisions can be reviewed before production.

Conservative operating principle

Capture the call, structure the handoff, escalate urgent language, and leave admissions decisions to the human team.