DELETE /contacts/{id} does it. This
page says what that removes, what it deliberately does not, and how recordings
and transcripts are treated for model training.
Erasing a contact
Erasing a contact removes, together and for good:- their conversations and every message in them (the transcripts);
- their calls, queued calls, callbacks and calling-campaign entries;
- their form replies, helpdesk tickets and the follow-ups waiting on them;
- the recordings of their calls, wherever the audio is kept;
- any duplicate of them that was merged into the contact — the record a merge leaves behind still holds a name and an email, so it goes too.
withdrawn instead.
Recordings go with the contact
The audio is deleted first, then the call records, so a recording is never left behind with nothing pointing to it:
If a file cannot be deleted at that moment — a provider is down, say — the
contact is still erased, and the deletion is queued and retried every night
until it succeeds. The response then carries
recordingsPending, the number of
files still queued:
204, no body) every file was already gone when the response came
back.
To know when an erasure is finished, subscribe a webhook to
contact.erased. It is sent once,
with only the contact’s id and when it was erased: straight away after a 204,
or from the nightly retry once the last queued file is gone.
What is not erased
- Do-not-call entries are kept, on purpose. If the person asked never to be called again, forgetting the number would let a campaign ring it again. The list holds the number and where the request came from, not their history.
- Webhook payloads we already sent are kept for retries and then purged automatically after 7 days.
- Copies in your own systems and your vendors’. Anything your CRM, your webhook receiver or your tools stored is yours to delete; erasing a contact here does not reach into them.
Deleting one call’s recording and transcript
To remove what was said on one call without erasing the person, callDELETE /calls/{id}/content
with a full API key.
- Deleted: the recording (ours, the phone provider’s copy, and any copy made for model training), this call’s turns in the conversation, its summary, the details collected from it, and the summary handed on when the call was passed to another agent. Other calls and chats with the same person stay.
- Kept: the call itself — when it was, how long it lasted, what it cost and what it was billed as. Your usage and invoices do not change.
"contentDeleted": true and when it happened
(contentDeletedAt). A recording that cannot be deleted at that moment is
retried every night until it is gone; the answer says how many are still
queued (recordingsPending). Asking again is safe. A call that is still
going on, or one booked that has not rung yet, is refused — this is not how
you cancel a call (DELETE /calls/{id} still does that).
It cannot be undone.
How long calls are kept
Your plan keeps call recordings for 30 days on pay-as-you-go, 49 on Pro, 75 on Scale and 365 on Enterprise. Transcripts are kept until you delete them. To keep less, setcallRetentionDays with
PATCH /workspace — any whole
number of days from 1 up to your plan’s limit (a longer one is refused, naming
the limit). Every night, calls older than that lose their recording and
their transcript exactly as Delete Call Content removes them, and their billing
record stays. It applies to calls you already have, from the next night.
null goes back to your plan’s limit for recordings and keeps transcripts.
GET /workspace shows your setting
(callRetentionDays) and your plan’s limit (planRetentionDays).