It works with what you have.
Keep the CRM, the website form and the Zapier you already run. CustomerLedger is the memory and the consent record underneath them, and it talks to them through a keyed API and signed webhooks. This page is still short on purpose: everything on it exists today, and the things that do not are named as such further down.
Connected today
A keyed REST API
Your website form, your CRM's workflow, or Zapier and Make write people, interactions
and consent into your ledger and read them back. One key per front end, so any one of
them can be switched off without touching the others. Base URL
https://api.customerledger.ai/v1; the key is the tenant, so there is
nothing else to configure. Full reference on the Connect page once you sign in.
Signed webhooks
When a person is created or updated, an interaction lands, or consent changes, we
POST a JSON event to the HTTPS URL you registered, signed with a secret only you hold
(X-CustomerLedger-Signature, the same t/v1 HMAC shape Stripe uses), and
retry with backoff if you are down. Payloads never carry consent wording or transcripts;
those are read back with a key.
Exports you already have
HubSpot, Jobber, Housecall Pro, ServiceTitan and QuickBooks exports are recognised by their headers and mapped without asking; any spreadsheet, PDF or photo of a list goes through the same wizard. The original file is never kept.
The telephony rail
Inbound calls reach a live agent, and the call record, the caller and the summary land on the ledger. This is the surface that produced most of what is in the store, and it is described in detail on the calls page.
Outbound SMS, behind the gate
Text messages go out through a carrier rail, and every one of them is checked against the consent record first by a single decision the sender cannot skip. How that gate works.
Capture forms
Claim and enquiry forms on the businesses that feed this record write the person, the endpoint and the permission with its wording, in one write.
Not built, and worth saying plainly
There is no marketplace listing and no one-click connector that logs into another CRM for you: connecting means a key and a webhook URL, which takes a few minutes and is described on the Connect page after sign-in. Calendar and mail providers still connect to the After Hours AI and AI Executive products rather than to CustomerLedger directly. Nothing in the API can send a message; sending stays behind the consent gate on our side, which is the point of it.