Search Results

Overview Event: DIA (Dental Integrators Association) Annual Conference Dates: April 16-18, 2026 Venue: Margaritaville Hotel, Nashville, TN Room: Seagrass Room (main sessions) / Fins Up - Poolside (reception) / Porch of Indecision (meals) Timezone: Central (Ame...

DTC Client Onboarding SOP On-Site & Remote Tech Field Guide 1. Purpose & Scope This SOP defines the standard onboarding process for new DTC clients. The goal is a focused, efficient onboarding completed in 2–4 hours that gets the core infrastructure in place a...

Every invoice, quote, deposit, and ticket in the portal shows a status badge. These badges tell you where things stand at a glance — and which ones, if any, need your attention. Invoice statuses Invoices appear in the Billing section under the Invoices tab. ...

Any third-party system DTC integrates with will eventually rate-limit us, drop a webhook, return a 500, or return 404 on an entity it created ten minutes ago. This is not a bug in the upstream — it is the default behavior of every MSP-tier API we depend on (Ha...

User-facing requests never block on outbound writes. Every write to a third-party system is queued and executed in the background; every read is served from a local cache. The HTTP handler does the minimum amount of work needed to acknowledge the user and retu...

Every record in a DTC-built system answers three questions: when was I written? when did I last change upstream? when should I give up? If any of those answers is "I don't know," the system can't reason about freshness, can't detect drift, and can't escalate s...

Freshness comes from webhooks. The reconciler is what catches the webhooks that get dropped. Full-table polling is not an option. The rule: webhooks are the primary freshness mechanism. A periodic, change-based reconciler handles the gap between "usually deliv...

NULL is not 0. NULL is not "". NULL is not false. NULL is not "no change." Treating any of those as equivalent in DTC-built code is a production bug waiting to happen. The rule: every comparison, every filter, every conditional that can encounter NULL handles ...

Company name, logos, support contacts, color palette, email footer copy, physical address — all the things that identify a deployment as DTC's — live in environment variables. Not hard-coded strings in the source. The rule: the same compiled binary ships to an...

Every deployment is traceable back to a specific commit by a specific author. Version numbers are durable; commits are signed; Docker image tags match git refs. If production misbehaves, the first question ("what's running?") always has an answer that's specif...

A closed ticket, a paid invoice, a rejected quote — these are terminal states. They rarely change. When they do change (reopened, refunded, reconsidered), a webhook tells us. Until then, we read them from the local cache without touching the upstream, even if ...

When something breaks in production, the first question is always: "what happened?" The answer has to be available in under five minutes, without deploying code, without adding logging, without guessing. The rule: every DTC-built system has structured logs wit...

Users close tabs. Networks drop connections. Browsers reconnect SSE streams. Servers deploy. Workers miss events. Emails arrive hours after the user forgot what they were doing. All of those paths need to converge on the same outcome: the user comes back, and ...

Day-of Onboarding Checklist Client: ____________________    Date: ____________    Start Time: ____________ On-Site Tech: ____________________    Remote Tech: ____________________   Phase 1 — Arrival & Quick Network Audit (0:00 – 0:30) ✓RoleTask☐On-SiteCheck in...