Every message you send through Finocket — campaign, sequence step or reminder — passes through one server-side checkpoint that verifies consent, the suppression list, template class and quiet hours before it can leave. If a message can't legally go, it's logged as blocked with the reason — never silently dropped.
How do I launch a campaign?
- On Campaigns, acknowledge the compliance banner first — it names the law that applies to your country (DPDP for India, the Spam Act for Australia, CAN-SPAM/TCPA for the US) and you re-acknowledge when the rules are updated.
- Create a template: subject, body, channel and class (transactional or marketing). A live linter blocks marketing phrases (“offer”, “discount”, “sale”) in templates marked transactional — a template that fails lint cannot send.
- Create the campaign, pick your audience — everyone, leads only, or clients only — and see the live count before you confirm.
- Launch. Today, only email campaigns can be launched — SMS and WhatsApp templates can be authored and are used for one-off and transactional messages, but campaign launch is email-only for now.
- Sends go out in batches and are resume-safe: if a run stops midway, Finish sending picks up exactly where it left off without messaging anyone twice.
- The message log shows every recipient's status — queued, sent, blocked, bounced or complained — with the block reason spelled out.
What does the send checkpoint actually check?
In order, on the server, for every message: the template lint gate; the contact's consent state and the suppression list; SMS quiet hours (enforced against the recipient's local time, with stricter state windows in the US); and the channel rules — transactional messages go unless the contact is suppressed, marketing needs a live opt-in. Whatever the outcome, a message row is always written, so your log is the complete truth.
How does unsubscribe work?
Every marketing email carries a one-click unsubscribe (RFC 8058 plus List-Unsubscribe headers). It takes effect immediately, with no login and no “are you sure” maze — the contact lands on a confirmation page. Consent is an append-only ledger: an unsubscribe is a new row, and a later express opt-in (for example, through one of your forms) can lift it. Complaints and hard bounces never auto-lift.
Who can send?
Owners and assistants launch campaigns; accountants are read-only. The module is enforced server-side — if it's disabled for the workspace, the campaign APIs refuse even direct calls.
Related: Email sequences, Sending & deliverability, Bring your own outreach keys.