Concepts and supported capabilities
How Airgent agents are offered, deployed, configured and run, and which of those capabilities you can use today.
Concept
Airgent agents run on a harness. It turns a business event, such as a patient asking for an appointment, into work done inside your systems. The harness has four layers. Each layer has a different owner and changes in a different way.
| Layer | What it is | Who owns it | How it changes |
|---|---|---|---|
| Catalog | What Airgent offers: each job (such as Front Office or Scribe), the workflows it includes, the approvals it enforces and the systems it needs | Airgent | Airgent releases it. It's the same for every customer. |
| Deployment | What you've taken up: which jobs are live, where, and under which approvals | You and Airgent | Agreed when you deploy |
| Configuration | How a deployment is wired for you: your connected systems, data mappings, workflow tuning and agent policy (persona, languages, what it may and may not do, when it hands over to a person) | Set per customer | Changed by Airgent with you, without an Airgent release |
| Execution | What happens for each event: trigger, steps, actions and the outcome | The harness | Follows your current configuration |
Workflow. A workflow is the unit of work. It has a trigger, an optional condition and ordered steps. Each step is one of these:
- an action on a connected system (for example, book)
- an agent step that decides, drafts or converses
- a wait
- a decision
- an approval that a named person must confirm
A workflow ends in an outcome or an escalation to a person.
Action. An action is one system-independent verb, such as check availability, book, reschedule, cancel or check in. A workflow made from existing actions is configuration. A workflow that needs a new action needs an Airgent release.
Approval. Some approvals are mandatory: a doctor signs every scribe note, and no setting removes that. Others are configurable, such as staff confirmation before an agent cancels or reschedules.
Availability
| Capability | Status |
|---|---|
| Front Office agent for healthcare: answer clinic hours, check availability, book and confirm, reschedule, cancel, take a message | Available |
| Front Office agent for healthcare: recognise a returning patient | Available on WhatsApp |
| Front Office agent for healthcare: check in a patient | Not available |
| Scribe for healthcare: produce a draft note for the doctor to review and sign | Available |
| Front Office agent for other business types | Not available |
| Recall, business discovery and patient intelligence jobs | Not available |
| The system your agents act on | Keel only |
| Connections to your own systems (FHIR, REST, MCP, webhooks) | Not available |
| Self-service configuration | Not available Airgent configures your deployment with you. |
| Run history, approval tracking and monitoring through the harness | Not available |
| Public API for the harness | Not available |
Configuration
Not available for self-service. Airgent sets up your deployment's configuration with you during deployment. To change it, contact Airgent.
Errors
Not available. There is no published error reference for the harness yet.
Checked against Airgent's accepted architecture and product source on 2026-10-09, and the configuration and execution rows again on 2026-10-11. Not yet observed in a live deployment.