People should know they are speaking with AI.
The opening and channel profile identify the assistant clearly. The system does not pretend to be a clinician, employee, or specific real person.
// AI trust & safety
A dependable AI system is explicit about what it is, acts only inside approved boundaries, and leaves important decisions with authorised people.
// Design principles
The exact controls depend on the organisation, workflow, country, and information involved. They are agreed before launch.
The opening and channel profile identify the assistant clearly. The system does not pretend to be a clinician, employee, or specific real person.
Allowed information, prohibited advice, escalation triggers, and tool permissions are defined for the workflow instead of left to improvisation.
When a request is sensitive, urgent, unclear, or outside scope, the agent stops, captures context, and follows an approved transfer or callback path.
Access, retention, deletion, exports, and staff visibility are scoped before launch. Sensitive data is not collected merely because the system can ask for it.
If calls are recorded or transcribed, the organisation must approve the purpose, notice, access rules, retention period, and deletion process.
Calls, messages, handoffs, tool actions, failures, and approvals can be logged so staff can review what happened and correct the system.
// Healthcare boundary
A clinic agent can share approved administrative information, manage appointments, and route requests. It should not diagnose symptoms, recommend treatment, or delay urgent human help.
Bring one routine workflow. We will map what the agent may do, what it must never do, and when a person takes over.
Review a workflow