Sending rules and consent

​

Set who sends

• Company name: the name people know you by. The unsubscribe page of your emails shows it, and the first text a contact gets starts with it (text messages are coming soon).
• Postal address (required for emails): your street address, a P.O. box or a registered private mailbox. US law (CAN-SPAM) requires a valid postal address in every commercial email, so Kerux adds it on one small line under the opt-out line of every campaign email. Booking confirmation emails show it after your company name, and a new Footer block in your email template starts with your company name and this address (you can edit them in the block).
• Language of the email footer: English, Spanish, German or French.

• the checks before launch block a campaign with an email step, with Who sends is missing: a postal address and a Fix link to this page;
• emails already on their way wait with Waiting for who sends in Settings > Sending rules: add your postal address (emails) or company name (texts) and show in Needs attention with Open Sending rules. They go on by themselves once you save.

​

Text messages (SMS)

• Only to contacts with a recorded consent for their current phone. A contact without one waits at the Send SMS step with Waiting for consent: texts go only to people who agreed. Record it on the contact. Before launch, the checks say how many contacts would wait.
• Only in the contact’s daytime: from 8:00 to 21:00 in their own time; from 8:00 to 20:00, and at most 3 texts a day, in Florida, Oklahoma and Maryland. Kerux reads where they are from their LinkedIn location and their phone’s area code; when the two disagree, or it can’t tell, it only texts at an hour that is fine in every place they could be.
• The first text names you and says how to stop: the first text a contact gets in a campaign gets your company name in front (“Northwind: …”) and “Reply STOP to opt out.” at the end, unless your text already has them.
• STOP is honored at once: STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT, REVOKE, OPT OUT, and plain words like “stop texting me”, “remove me” or “wrong number” (also in Spanish, German and French). That phone is never texted again from this workspace, and its consent no longer counts. Texting START undoes it.
• An owner or admin confirms the rules (consent, STOP, A2P 10DLC registration of your US numbers) by ticking a box in the Twilio panel (Integrations > Connections) the first time Twilio is connected. It is a statement for the whole workspace, so members can’t make it: they see Only an owner or admin can connect Twilio the first time… and can change the keys once an admin has connected it. Until it is confirmed, SMS campaigns can’t launch and texts wait. See Twilio (text messages).

​

WhatsApp

​

Where consent comes from

1. By itself from a form: a lead form question about texts or WhatsApp answered yes (for example a checkbox “I agree to receive text messages”). The question’s words are kept as what they agreed to.
2. By itself when they write first: a text or WhatsApp message from the contact’s phone, or START.
3. When you import: on the last step of an import (3. Import), under Consent to texts or WhatsApp (optional), tick They agreed to get texts (SMS) or They agreed to get WhatsApp messages, then I confirm these people gave us this consent, and I can show how if asked. A column such as sms_consent or whatsapp_consent with yes, imported as a custom field, also counts for that row. Only rows with a phone get a consent. Only do this when every person really agreed.
4. By hand: on the contact page, under Consent and contact, tick Texts (SMS): the contact gave consent or WhatsApp: the contact gave consent. Kerux keeps your name and the time, for the contact’s current phone. Untick it to withdraw it. For many contacts at once, tick them in Contacts > Database and choose They agreed to…. When you add contacts to a campaign, the checklist line about consent has a They agreed button that does the same for the contacts you’re adding. The contact needs a phone with its country code first (type it under Details and click Save). Members, admins and owners can do this; viewers only see it.
5. By API: POST /v1/leads/{id}/consent with channels and attest: true.
6. For the whole workspace: in Settings > Sending rules, under Contacts’ consent, turn on Texts (SMS) and/or WhatsApp, tick I confirm these contacts agreed to get these messages from us. and click Save (owners and admins). Every contact you add from then on counts as agreed on those channels, with no step per contact. Tick Also my current contacts to cover the ones already in the workspace too. The contact page shows Workspace setting as where the consent comes from. A STOP reply, the do-not-contact list and unticking the consent on a contact page still win for that contact. Turn it off the same way. Only use it when everyone you add really agreed (for example, they all signed up on your own form).

​

Email

​

Do not contact

​

Deletion requests (GDPR)

• their details, custom fields, tags, notes, tasks, AI research and enrichment results;
• their campaign history, timeline and queued steps (nothing queued goes out), and their consent records;
• inbox conversations with them on every channel (LinkedIn, email, WhatsApp and text) and every message, voice note and reaction in them;
• comments they wrote on your LinkedIn posts (see Comment automation);
• LinkedIn invitations they sent you, and the notifications about them;
• lead ad form submissions, email opens and clicks, meetings that were only with them and possible meetings about them;
• outgoing webhook events about them and their delivery logs, payloads that reached your listener steps, saved API replays that show them, and their rows in import error reports.

• their email(s), phone and LinkedIn profile become one-way hashes on the do-not-contact list (shown as Deleted person (kept as a hash)). An earlier unsubscribe or STOP becomes a hash too, so emails and texts to them stay blocked; if an import or a form adds them again, no campaign takes them;
• a form submission and what the LinkedIn checks saw keep only a hash of their id, so a resent form or the next check never brings them back.

​

API