Account

Consent attestation

Your company's signed statement that the contacts you bring to RCSync agreed to receive your text messages. RCS and SMS messages send only while a current attestation is on file.

Why it's needed

RCSync records opt-ins it sees directly — a keyword like JOIN, or an opt-in sent through a webhook. Most of the numbers you text, though, come from somewhere RCSync can't see: a list you import, your point-of-sale system, a form on your website. The attestation is your company's statement, made by someone authorized to make it, that those people agreed to hear from you — and it covers exactly the sources and dates you name, no more.

It applies to text messages (RCS and SMS) only. Email campaigns don't need one; they rely on unsubscribe handling instead.

Recording one

Open Consent → Consent attestation. The page shows whether you have a current attestation, and the form to record one:

  • Name, title and email — of the person making the statement. They must be authorized to act for your company, and tick a box saying so.
  • Where your contacts come from — tick every source the statement covers: file imports and uploaded lists, contacts added by hand, POS or CRM sync, webhook sign-ups, the API, keyword opt-ins.
  • How consent was collected — one method per line, for example “checkbox on our website sign-up form”.
  • The disclosure people saw — the exact wording shown when they agreed.
  • Date range — when the consents it covers were collected. Leave the end blank if you're still collecting consent this way.

The full statement you're making is shown, with your answers filled in, before you accept it. Accepting asks for a fresh verification code, texted to your phone. A copy of the accepted statement is emailed to the person named and to everyone on your team, so anyone who didn't expect it can raise it.

Who it covers

A text message goes to someone only when your brand has a current attestation and one of these is true:

The recipient…Covered when
Opted in themselves (a keyword or a webhook sign-up)Always — their own opt-in is on record.
Is a contact on your listTheir source is one your attestation lists, and they were added within its date range.
Is on a list uploaded to a campaignYour attestation covers file imports and uploaded lists (or POS or CRM sync, for POS lists).
Arrives through an open-campaign or Aura Offers webhookYour attestation covers webhook sign-ups.

Opt-outs always win: someone who replied STOP to any of your senders is never texted, whatever your attestation says. See Consent.

Without a current attestation

Once the check is switched on for your account:

  • Text messages to recipients with no consent basis are skipped, the same way opt-outs and frequency-capped contacts are. The API reports the reason for each one.
  • With no current attestation at all, no text campaign activates and nothing sends.
  • Contact imports and audience list uploads are refused until your attestation covers file imports.
  • A webhook sign-up is refused with a 409 if your attestation doesn't cover webhook sign-ups.

Until then, everything still sends, and a banner on your dashboard, Campaigns and Consent pages reminds you to record your attestation.

Expiry, renewal and changes

Expiry

An attestation lasts 12 months. Everyone on your team, and the person who made it, gets an email 60, 30 and 7 days before it expires, and one more when it has. From 30 days out a banner in the app asks you to renew too. Renewing is recording a new one. There's no grace period — text messages stop the moment it expires.

When something changes

Record a new attestation before you start bringing contacts from a source it doesn't cover, or change how you collect consent. The newest attestation is the one that counts.

Updated statement

Whisp occasionally updates the statement itself. When an update needs everyone to agree to the new words, your current attestation stops counting and the banner asks you to accept the new version.

Revoking

If a statement in your attestation stops being true, revoke it from its row in the history, with a reason. Text messages stop straight away and stay stopped until a new attestation is recorded. Revoking the newest attestation doesn't bring back an older one.

Every attestation is kept — current, expired, superseded and revoked — with the exact statement that was accepted. They can't be edited or deleted.