Most of your contacts give you permission inside Finocket: they fill in a form, reply on WhatsApp, tick a box. Finocket records the exact wording, the time and the source, so it can prove the opt-in later. Some contacts don't. They filled in a Facebook lead form, attended your webinar, met you at a trade show, or came from an industry directory. You have permission; we never saw it.
Declaring consent is how you tell Finocket about permission it can't see, so those contacts stop being blocked. It is the only setting in Finocket that turns a blocked message into an allowed one, so it's off until you turn it on, and this page sets out what you're taking on.
Turn it on
Open Campaigns and find Declare consent you hold outside Finocket. Only the workspace owner can switch it on. Choose how long a declaration lasts (365 days by default).
Declare it for the contacts it applies to
Select the contacts, choose Declare consent, and optionally record where the permission came from and a note. Both are optional. Finocket always records who declared it and when, because with no other evidence, that is the minimum worth keeping.
Declare it for people who actually gave you permission. Finocket cannot check the claim; it records that you made it.
What a declaration never overrides
A declaration does not outrank:
- An unsubscribe. If someone opts out, they stay out. Declaring consent afterwards cannot bring them back; only they can, by opting in again themselves.
- A spam complaint or a hard bounce. Both suppress the contact permanently.
- A data-deletion or do-not-sell request. Handled the same way as always.
- Quiet-hours holds, which apply to SMS where the law sets a window.
- WhatsApp's 24-hour rule. Outside the window you still need an approved template, declaration or not.
Declarations expire
A declaration lasts as long as you set, then lapses, and the contact stops receiving marketing until you renew it or they opt in themselves. An unverified claim that nobody re-checks for three years isn't worth much. You can set the window to zero so declarations never expire, but you lose the record that they were ever revisited.
Every message says which basis it used
In the message log, a send that relied on a declaration is recorded as declared, never as a normal opt-in. So if you're ever asked which of your messages went out on a claim rather than on a recorded opt-in, you can answer with a filter.
Changed your mind about a batch
Every declaration you make in one action shares a batch reference. Withdrawing it takes one step and covers the whole batch, however many contacts it held. Nothing is deleted. Finocket appends the withdrawal, so the record shows both that the claim was made and that you took it back. Those contacts return to needing a real opt-in.
You can withdraw a batch even after switching the setting back off.
If you're not sure
Finocket records your declaration; it doesn't rule on whether contacting a particular person is lawful where you operate. If you're unsure whether a source gives you a basis to market to someone, ask someone who advises you on data protection before you declare it. The suppression rules, the expiry and the audit trail keep a record of what you did; they do not give you legal cover.