Guide12 min
Migrating off spreadsheet-driven automation
A phased path from Apps Script and Google Sheets to a centralised pipeline, without a big-bang cutover or a support outage.
ReadResources
How teams actually put this in place
Implementation guides, migration playbooks, and the architectural detail behind the decisions the platform makes on your behalf.
Guides and playbooks
Guide9 min
Building a knowledge base your team trusts
How to write approved answers, internal actions, and do-not-say rules that produce drafts staff actually send.
ReadPlaybook7 min
Shadow mode: measuring before you cut over
Run the pipeline beside your current process, compare every decision, and set the agreement threshold before going live.
ReadPlaybook6 min
Designing a follow-up cadence customers answer
Why three outcomes beat a satisfaction score, and what to do with the second consecutive Not Resolved.
ReadReference14 min
Event contracts and idempotency keys
The dedupe keys behind every channel, and why checkpoint advancement is not a deduplication strategy.
ReadReference8 min
Matching senders across email, phone, and name
The match ladder, what happens on an ambiguous result, and how manual review feeds back into the directory.
ReadSecurity
Multi-tenant from the first line of schema
Isolation added later is isolation that leaks. Admin Shortstop treats the organization boundary as a database-level constraint, not a filter someone might forget to write.
Request the security overviewTenant isolation
Every record carries an organization ID, enforced at the database layer with row-level security rather than in application code alone.
Credential handling
Provider credentials live in a managed secret store and are referenced, never copied into the database, logs, or source control.
Webhook verification
Inbound webhooks are signature-verified with constant-time comparison, and replay is prevented by the same idempotency keys used for deduplication.
Audit trail
Mutations and support access are recorded with actor, correlation ID, and before/after state. Support access is time-boxed and requires an admin grant.
Support
Operations plans include a named contact and a shared escalation channel. Failures reach us before they reach you.
Contact supportSystem status
Ingestion, processing, and each connected provider reported independently, with incident history.
Status page coming with general availability
Changelog
What shipped, what changed in decision behaviour, and what is deprecated — published for every release.
View the product