Concept
Embed & host
Put care flow activities in front of patients and clinicians, using pages Awell hosts or a custom interface built with Navi.
This section covers where patients and clinicians do what a care flow asks of them: fill in a form, read a message, confirm an appointment.
Placement decides which option fits
| Option | Effort | Controls | Best when |
|---|---|---|---|
| Hosted Pages | Lowest | Branding and settings | Going live fast matters, and Awell's UI is good enough |
| Navi | Medium | Placement, theming, events | Activities belong inside an existing product |
| Your own UI | Highest | Everything | Neither of the above allows what's needed |
Hosted Pages and Navi are both prebuilt UI for care flows, so the difference between them is placement: Hosted Pages is a page a stakeholder is sent to, or an iframe, while Navi is a component rendered inside an existing app. Use Navi where patients already use the host product, and Hosted Pages where they are sent a link.
Hosted Pages
- What Hosted Pages is
- Built-in and customizable features
- Sessions and links: how to get a URL for a stakeholder
- Embed or redirect
- Hosted Pages settings
- Set a custom domain
- Care flow design with Hosted Pages
- Link to an activity from email or SMS
- Tracking and attribution
Navi
- What is Navi?
- Quickstart: get something rendering
- Activity model and lifecycle
- Sessions and JWTs
- Branding and theming
Authors choose the surface; engineers embed it
Picking an option and branding the result is a care flow author's call; embedding it is an engineer's.