Where a flow and its governance nodes are edited together.
Sector templates
Ten flows worked out, not yet built.
Planned · would ship with the flow builder
Ten templates are worked out: the flow, the sector and the compliance overlay nodes in each. None of them is built — the status column below says so per template — and they would ship with the flow builder, which is planned as well. The verticals are the ones where compliance behaviour actually differs: dental, legal, healthcare, financial services and general SMB. The nodes sit inside the template so that the governance travels with the flow instead of being reapplied by hand every time someone copies it.
The templates
What each one does, and which governance nodes it carries.
The nodes in the last column are not documentation. They are the parts of the flow that decide whether a step may run at all: eligibility before an outbound call, scope-of-practice before an answer, vulnerable-person handling before an escalation.
- Sector
- Dental
- Template
- No-show recovery
- What it does
- Outbound to patients who missed an appointment.
- Governance nodes
- Outbound eligibility · scope of practice
- Status
- Planned
- Sector
- Dental
- Template
- Booking and reminder
- What it does
- Inbound booking with an outbound reminder cycle.
- Governance nodes
- Article 50 disclosure · vulnerable-person handling
- Status
- Planned
- Sector
- Legal tech
- Template
- Intake screening
- What it does
- Pre-qualification of legal enquiries before a lawyer triages them.
- Governance nodes
- Scope of practice (no legal advice) · compliance checkpoint
- Status
- Planned
- Sector
- Legal tech
- Template
- Case status updates
- What it does
- Outbound status notification to clients across the region.
- Governance nodes
- Cross-jurisdiction consent
- Status
- Planned
- Sector
- Healthcare
- Template
- Patient triage
- What it does
- A pre-screening conversation that routes on medical urgency.
- Governance nodes
- Scope of practice (no medical advice) · vulnerable-person handling
- Status
- Planned
- Sector
- Healthcare
- Template
- Follow-up after consultation
- What it does
- Outbound recall after an appointment.
- Governance nodes
- Cross-jurisdiction consent · PHI compartmentalisation
- Status
- Planned
- Sector
- Financial services
- Template
- Lead qualification
- What it does
- Inbound and outbound intake for scheduling financial advice.
- Governance nodes
- Commercial transaction validation · scope of practice
- Status
- Planned
- Sector
- Financial services
- Template
- Payment reminder
- What it does
- Outbound dunning with the regulatory dunning rules built in.
- Governance nodes
- Outbound eligibility
- Status
- Planned
- Sector
- General SMB
- Template
- Support deflection
- What it does
- Inbound deflection of tier-one queries away from human agents.
- Governance nodes
- Article 50 disclosure · compliance checkpoint
- Status
- Planned
- Sector
- General SMB
- Template
- Survey and feedback
- What it does
- Outbound feedback collection with consent governance.
- Governance nodes
- Outbound eligibility · vulnerable-person handling
- Status
- Planned
Why templates and not documentation
A rule that travels with the flow is a rule that survives a copy.
The failure mode is not that someone does not know the rule. It is that the rule lives in a document and the flow lives in a builder, and the second one gets duplicated for the next client while the first one does not.
Putting the eligibility check, the scope check and the disclosure step inside the template means the copy carries them too. That is the whole idea, and it is why the templates ship with the flow builder rather than as a PDF pack.
Questions
- Can I use a template as-is?
- It is a starting point, not a finished agent. The wording, the knowledge base and the escalation path are yours; what the template brings is the structure and the governance nodes in the right places.
- My sector is not on the list. Now what?
- We build templates for pilot agencies. Raise it during the scoping call and say which step in your flow is the one that has to be governed — that is usually the fastest route to a template that fits.
- Do templates change the compliance position?
- No. A template makes the same governance easier to apply consistently; it does not create an obligation and it does not remove one. The obligations sit in the regulation, and the article numbers are on the Article 50 page.
The flow builder
The templates ship as part of it. The builder is where a flow and its governance nodes are edited together.
Related
Flow builder Feature list Every capability, with the status of each line.
The platform The governance engine the nodes run on.
Article 50 What the law requires, with the article numbers.