Approvals, Safety & Human Oversight
You decide what Deptly drafts, what it handles, and what always stays human.
The control model in plain terms: what runs within your rules, what waits for your approval, and what is never the system's to decide.
What does this layer do?
You assign a control level to every class of action: handle within rules, draft for your approval, or always human. Sensitive actions default to approval-first until you deliberately loosen them, industry guardrails are built in, and final legal, clinical, safety, coverage, and fiduciary decisions can never be delegated to the system at any setting. An audit history records what was asked, what was approved, and what was done.
Control levels, not all-or-nothing
The real question about any system doing work on your behalf is not whether it is impressive — it is who is in control. Deptly's answer is control levels, set per class of action rather than as one global switch.
Handled within rules: routine actions you have approved run to completion — appointment confirmations, reminder sequences, standard follow-ups — and report in your weekly brief. Draft for approval: Deptly prepares the work, and it waits for your yes — a quote at the edge of your pricing, a response to an unhappy customer, a refund. Always human: some things reach you untouched, drafted by no one.
You set these levels per action class, and defaults are conservative: new classes of action start at approval-first, and you loosen them deliberately, one at a time, as trust is earned by a visible track record.
Sensitive actions and industry guardrails
Some categories are treated as sensitive regardless of your settings: money above your thresholds, pricing exceptions, anything involving a complaint or dispute, and communications with unusual weight. These default to approval-first, and several have a floor below which the controls cannot be loosened at all.
Industry guardrails sit on top. A med spa gets clinical-communication boundaries — Deptly can confirm appointments and answer logistics, but treatment suitability questions route to the practitioner. A law firm gets legal-advice boundaries: scheduling and document chasing, never a legal position. Restoration companies get coverage-language rules — Deptly can assemble and chase documentation, but never tells a customer what insurance will cover.
One line matters most: the system is built so that final legal, clinical, safety, insurance-coverage, and fiduciary decisions cannot be delegated to it. That is not a setting you might misconfigure. There is no control level at which Deptly makes those calls.
Audit history and how oversight evolves
Every action carries a record: what triggered it, what Deptly did or recommended, what you approved or declined, and what happened in which system. When you want to know why a customer got a message or an invoice went out, the answer is a lookup, not a mystery.
Approval requests are built to be decidable in seconds: what happened, what is recommended, what it costs, what happens if you say no. If you do not respond, the action waits or escalates according to your rules — silence is never treated as a yes.
Oversight is expected to change over time. Most owners start with almost everything at approval-first, watch the brief for a few weeks, and promote the action classes that have proven boring. Tightening is just as easy, and control-level changes only ever happen because you make them — nothing self-escalates its own permissions.
A note on the jargon, for readers who follow AI
If you read about AI, you will meet terms like agentic systems, autonomous agents, and multi-agent architectures — vendor language for software that plans and carries out multi-step tasks. The technology under Deptly belongs to that family: it does plan and execute complete workflows, not just answer questions.
We avoid those words in our own descriptions because they blur the question that actually matters to an owner: who decides what? Deptly's position is boring on purpose — every class of action has an owner-assigned control level, sensitive categories have floors, certain decisions are structurally reserved for humans, and everything is logged. Judge any system in this category by those specifics, whatever vocabulary its marketing uses.
What it works from
- The control levels you set per class of action, during onboarding and any time after
- Industry guardrail defaults matched to your business type
- Your escalation rules: who gets asked, in what order, and how long to wait
- Sensitive-action definitions: money thresholds, disputes, and communications with unusual weight
- The full action log, which powers the audit history and your weekly brief
Everything above comes from your business — your records, your rules, your tools. Nothing is invented, and when information is missing, it becomes a question to you rather than a guess.
What this looks like in practice
Every proof item on this site is labeled for exactly what it is.
A billing question handled at the approval level — dental practice
Patient
I was charged $180 but my treatment plan said $120 — can someone fix this?
2:14 PM
Deptly
Billing disputes are set to draft-for-approval in your controls. Pulled the ledger: the $60 difference is a fluoride treatment added on the day, not on the original plan. Drafted an explanation and a refund option.
2:16 PM
Deptly
Needs your OKRecommend: explain the add-on and offer to remove the charge as a courtesy ($60 refund). Approve the refund with explanation, send the explanation only, or take this one yourself?
2:17 PM
Practice owner
Refund it and send the explanation.
2:29 PM
Deptly
Refund processed in your practice software and the explanation sent in your wording. Audit history logged: what the patient asked, what was recommended, what you approved, what was done.
2:31 PM
Where humans stay in the loop
This layer runs inside boundaries, not on its own. Here is who reviews what — and the limits it never crosses.
Human review
- You set the control level for every class of action: handle within rules, draft for your approval, or always human.
- Sensitive categories — refunds above your threshold, pricing exceptions, anything involving a complaint — default to approval-first until you deliberately loosen them.
- Final legal, clinical, safety, insurance-coverage, and fiduciary decisions are never Deptly's to make at any control level — the system is built so they cannot be delegated.
- If you do not respond to an approval request, the action waits or escalates per your rules — silence is never treated as a yes.
- The audit history is always available: what was asked, what was approved, what was done, and where.
Guardrails
- Defaults are conservative: new action classes start at approval-first, and you loosen them deliberately, one at a time.
- Industry guardrails are pre-set — clinical-communication boundaries for aesthetics and health practices, legal-advice boundaries for firms, coverage-language rules in restoration — with a floor that cannot be turned off.
- Approval requests carry the context needed to actually decide: what happened, what is recommended, what it costs, what happens if you decline.
- Nothing self-escalates its own permissions — control-level changes happen only because you make them.
The full rulebook — control levels, approvals, and audit history — lives on trust and control.
Where this layer shows up
Technology is only interesting when it carries real work. These are the responsibilities this layer powers — and the layers around it.
Responsibilities it powers
- See What Needs Attention—and Handle It
- Get Paid & Finish the Back Office
- See everything Deptly handles
The layers around this one
Questions owners ask
A setting you assign to each class of action, choosing one of three modes: handled within rules (runs to completion and reports in your brief), draft for approval (prepared, but waits for your yes), or always human (reaches you untouched). Appointment reminders might be fully handled while refunds stay approval-first — the levels are yours to set and change.
Final legal, clinical, safety, insurance-coverage, and fiduciary decisions, plus contested situations — disputes, complaints escalating toward conflict, quality disagreements. These are structurally reserved for people: there is no configuration in which Deptly makes them, which means there is also no way to misconfigure your way into it.
For every action: the trigger, what Deptly did or recommended, the approval or decline and who gave it, the resulting change and which system it landed in, and the timing throughout. It exists so "why did this customer get this message?" is a lookup rather than a mystery — and so you can review Deptly's work the way you would review an employee's.
The action waits, or escalates along the path you defined — to your office manager after a set time, for example. What never happens is a timeout that counts as consent. If something time-sensitive expires while waiting, it expires; the brief tells you, and you can decide whether that class of action deserves a different rule.
Yes — that is the expected pattern. Most owners start nearly everything at approval-first, watch the weekly brief, and promote the action classes that have proven consistently boring. Tightening is equally immediate. The one constant is direction of authority: every change is made by you, and nothing expands its own permissions.
They are pre-set boundaries matched to your business type, layered on top of your own settings. Aesthetics and health practices get clinical-communication limits, law firms get legal-advice boundaries, restoration companies get coverage-language rules. You can tighten them further; below a safety floor, they cannot be loosened at all.
Access is limited to the people servicing your account, under access controls, for the purpose of doing your work. We would rather answer this precisely for your setup during onboarding — including how access is granted, logged, and revoked — than gesture at it here. Ask, and you will get the specifics in writing.
Under the hood, then in practice
See what Deptly could take off your plate
Answer a few questions about how your week actually runs and get an honest read on which responsibility this machinery should carry for you first.