Works in Your Existing Tools
Keep the systems that hold your business. Add the execution they still require.
How Deptly connects to the software you already run on — and why your systems, not ours, remain the source of truth.
What does this layer do?
Deptly works inside the systems you already run your business on — your scheduling platform, CRM or practice software, email, calendar, and invoicing — connecting through APIs where they exist and browser-based access where they do not. Your systems stay the system of record: Deptly reads from them, writes results back to them, and logs every change, instead of asking your team to adopt something new.
Your systems stay the system of record
You have already paid — in money, migration pain, and habit — for the systems that hold your business. The scheduling platform your team checks every morning. The CRM with ten years of customers. The practice software your compliance depends on. The last thing you need is a new place to look.
Deptly is built around that reality. It does not replace your systems or maintain a competing copy of your business. It reads from your tools, does the execution work they still leave to a human — the follow-up, the update, the chase, the entry — and writes the results back where your team already looks.
The test is simple: your team keeps working in the tools they know, and those tools are simply more up to date than they used to be.
How Deptly connects
Where your systems offer official APIs, Deptly uses them — the most reliable path for reading records and writing updates. Email and calendar connect through standard account access with scopes you approve, which alone covers a large share of real execution work: confirmations, follow-ups, scheduling, document handling.
For the legacy systems that run much of the service world — the dispatch tool from 2011, the practice system with no API — Deptly can work through the same browser screens your team uses, performing the same clicks and entries a trained staff member would. Slower than an API, but it means a system without one does not exclude your business.
Some systems only share data one way, through exports or reports. Deptly works with that too, and is honest during onboarding about which of your tools support full two-way work versus read-mostly access. Systems named on this site are examples, not guaranteed integrations — your actual stack gets mapped in discovery.
Boundaries and the audit trail
Access is scoped during onboarding: you decide which systems Deptly can read, which it can write to, and which it never touches. Credentials are stored under access controls and used only for the purposes you approved. Where a system supports scoped or dedicated accounts, that is the preferred setup — it keeps Deptly's access visible and revocable.
Every read and write is logged: what changed, in which system, when, and as part of which workflow. When a customer record updates or an invoice goes out, you can trace exactly why. And bulk operations above thresholds you set require explicit approval first — no mass changes to your data on the system's own initiative.
When a connection breaks or data disagrees between systems, the affected work stops and a person is flagged. No silent failures, and no silent retries into a mess.
What it works from
- Official APIs, where your systems offer them
- Your business email and calendar accounts, connected with scoped access
- Browser-based access for legacy systems with no API — the same screens your team uses
- Exports, webhooks, and reports for systems that only share data one way
- An audit log recording every read and write across all of it
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.
Status questions answered from the shop system — auto repair
Customer
Any update on my Civic? Hoping it's done today.
11:40 AM
Deptly
Read the repair order in the shop management system: parts arrived 10:15, tech assigned, status in progress, promised time 4 PM. Same system the team already updates — no extra step for anyone in the bay.
11:40 AM
Deptly
Replied to the customer: Civic is in progress, parts are in, on track for 4 PM pickup. The reply was logged to the repair order as a note.
11:41 AM
Deptly
Repair order marked complete in the shop system. Invoice generated there, and the pickup text went out with the balance and today's closing time.
5:05 PM
- Dinbox
Owner brief
Friday
23 status questions answered directly from the shop system this week, each logged on its repair order. No separate inbox. No new dashboard for the team to check.
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
- Access is scoped with you during onboarding — you decide which systems Deptly reads, which it writes to, and which it never touches.
- Every write to your systems is attributed and logged, so you can see exactly what changed, where, and as part of which workflow.
- When a connection fails or data disagrees between systems, the work stops and a person is flagged — nothing is silently retried.
- Deptly executes in your tools but does not approve its own exceptions — anything outside recorded rules routes to you before a system is changed.
Guardrails
- Your existing systems remain the system of record — Deptly writes to them rather than building a parallel copy of your business.
- Credentials are stored under access controls and used only for the scopes you approved during onboarding.
- Browser-based access to legacy tools follows the same rules as API access: scoped, logged, and reviewable.
- Bulk operations above thresholds you set require explicit approval — no mass changes on the system's own initiative.
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
The layers around this one
Questions owners ask
Deptly can work through the browser — the same screens and entries your team uses — with the same scoping and logging as API access. It is slower and set up more carefully, and some legacy systems support only partial workflows that way. Discovery maps what is realistic for your specific tools before anything is promised.
Access is set up deliberately during onboarding, with the least access that does the job. Where a system supports dedicated or scoped accounts, that is the preferred route, because it keeps Deptly's access separately visible and instantly revocable. Where it does not, we walk through exactly how credentials are stored and used before you share anything.
Yes — that is much of the point. Booked jobs, updated records, logged notes, and generated invoices land in your systems so your team sees current truth where they already look. Every write is attributed and logged, write access is scoped to what you approved, and bulk changes above your thresholds require explicit approval first.
The honest answer is that it depends on your stack, which is why systems named on this site are examples rather than guaranteed integrations. Common scheduling, CRM, field service, and invoicing platforms connect by API; email and calendar are near-universal; legacy tools are assessed for browser-based access. Discovery produces a concrete map for your business.
The affected work stops and queues, and a person is flagged — customer-facing commitments do not silently fail. Deptly does not blindly retry writes into a system behaving unexpectedly, because a duplicated invoice is worse than a delayed one. Once the connection is restored and verified, queued work resumes and the brief notes what was delayed.
No. Your team keeps working in the tools they already know, and communication with Deptly happens over channels they already use — text, email, phone. The absence of a new interface is deliberate: adoption fails when software asks a busy team to change where they look.
Yes, at any time, per system — revoke the account or credential and access ends. This is another reason scoped or dedicated accounts are the preferred setup: your access to your own systems is never entangled with Deptly's, and shutting one door does not require rekeying your business.
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.