Telerva

Contacts and consent

Contacts and consent

Recording permission to call, and proving it afterwards.

A phone number in your contact list is not permission to call it. Telerva keeps consent as a record in its own right — captured, timestamped, with its source and its evidence — so that if anyone ever asks why a particular number was called on a particular day, there is an answer.

What a consent record holds

  • The number it applies to
  • When it was given
  • How it was given — a web form, a signed contract, a recorded call, an import from a previous system
  • The evidence you hold for it

Recording consent

Consent can be captured one contact at a time, or imported in bulk alongside a contact list. If you are migrating from another system, import the consent evidence with the contacts rather than after — a list without consent is a list that cannot be called.

Enforcement is a setting, and it defaults to off

This is worth reading carefully. Consent enforcement is available and works, and it ships switched off.

With it on, a call to a contact with no consent record is refused before it dials, and the refusal is written to the audit log. With it off, the platform records consent but does not block on it.

It defaults to off because switching it on with an empty consent database would block every call — which is correct behaviour, and not something to discover by surprise. Record consent first, review what would be blocked, then turn it on.

Withdrawal

Consent can be withdrawn, and withdrawal is honoured immediately and permanently across your whole account. See Do not call.

Contacts and consent — Telerva | Telerva