Contacts & Consent Management

Free includes 100 contacts, Standard 500, and Pro and Enterprise are unlimited. Contacts can have first/last name, email, phone, company, address, tags, pipeline stages, and unlimited custom fields. You can group contacts with tags or move them through pipeline stages (Lead → Qualified → Customer, etc.) for automation triggers.

Respectly captures consent through five methods, each producing timestamped evidence stored on the contact record:

• Hosted forms — public web forms that collect a typed name + checkbox + IP address as proof of consent.
• Consent management screen — a dedicated branded page where a contact reviews and updates their channel and purpose preferences.
• Double opt-in — the contact submits a form, then confirms via a link in a follow-up email or SMS.
• AI voice consent calls — the AI reads the required disclosures over the phone and records the verbal "yes," producing audio plus transcript.
• Manual upload — for existing consent records (CSV import or contact-by-contact upload of evidence).

Six levels, applied per channel (SMS, email, voice) and per purpose (marketing or informational):

• Unknown — no record on file.
• None — confirmed absence of any opt-in (you know they haven't consented).
• Opt-out — recipient revoked permission; a hard stop for that channel/purpose.
• Implicit opt-in — consent inferred from a qualifying business relationship (e.g., a recent purchase). Has a decay window.
• Express opt-in — recipient affirmatively opted in.
• Written express opt-in — recipient opted in with electronic written agreement evidence, suitable for the most stringent requirements (US TCPA written-consent rules).

Under Canada's CASL rules, purchase, lease, or rental creates implied consent for 24 months from the transaction date, and an inquiry or application creates implied consent for 6 months. Conspicuous publication for B2B purposes has no expiry. The compliance engine enforces these decay windows automatically — once a window closes, the contact reverts to "Unknown" unless an express opt-in was captured.

The contact's SMS consent is immediately set to opt-out, all queued and scheduled SMS to that contact are canceled, and a confirmation message is sent (where required by jurisdiction). The opt-out is persistent across channels and any future workflows or broadcasts will skip the contact for SMS automatically. Opt-out is logged with timestamp and source for audit.

For email, the same applies to unsubscribe clicks and List-Unsubscribe header actions. For voice, a verbal "do not call" captured by the AI agent triggers the same opt-out flow.

Use Contacts → Export to download a CSV of contacts plus consent status, tags, pipeline stage, and custom fields. Exports respect role-based permissions — only users with the `contacts:export` permission can export. Bulk and scheduled exports are available on Pro and Enterprise.

Yes — each contact has a preference center URL that you can include in any message. It shows the contact their current channel/purpose preferences and lets them update or revoke them. Changes are reflected immediately and logged as consent evidence.