Consent, Import, and Opt-out
A Review Request is sendable only when Consent exists for that Customer on that Channel. Adding a Customer does not create Consent. Import records Consent only for the basis chosen for that batch, and only on the channels that row can use. Without a basis, nothing is imported. A skipped row does not record Consent. Another app can post a completed Job. A fully paid Xero sales invoice can create a Job.
This is how a cold list stays unable to become a blast. It is not legal advice.
Use this before an Import, or when Send says not sendable: no Consent on SMS or not sendable: no Consent on Email.
Express and Inferred
Consent is per Customer, per Channel (SMS or Email). On Add Customer and Correction the controls are Text or email and Why you can contact them.
Text or email is None yet, SMS, or Email.
Why you can contact them is None yet, They asked to hear from you, or This job is why you are contacting them.
They asked to hear from you is recorded as Express — the Customer asked to be contacted.
This job is why you are contacting them is recorded as Inferred — implied by a real Job this Business did for that Customer, for messages about that work. Not available without a Job. A bought or cold list is not consent.
None yet — the Customer is stored; a Review Request is not sendable until Consent exists on the Channel that would be used. The empty Customers list says adding a person does not create Consent, and that they choose why they can contact them before a send.
Import
Import lives on Customers, not as its own destination. At most 5,000 rows.
Choose Why you can contact them for this file before the file is accepted: They asked to hear from you (recorded as Express) or This job is why you are contacting them (recorded as Inferred). One reason for every row. The placeholder is Choose why you can contact them first. No basis, no Import. A bought or cold list is not consent.
The batch is a .csv file with the header name,mobile,email,completedAt. The page shows the file name. Download a sample file on Customers and copy it. A comma inside a name needs quotes. A completion time can be 1/08/2026, 01/08/2026, 1/08/2026 17:30, or 2026-08-01. A date with no clock time is 00:00 on that day in the Business timezone. 1/08/2026 is 1 August. An instant that already has an offset, such as 2026-08-01T10:00:00+10:00, stays that instant.
No file says Choose a .csv file before you Import. A file that is not .csv says Choose a .csv file. The header is name,mobile,email,completedAt. The wrong header says The file needs the header name,mobile,email,completedAt. Semicolons or tabs say Save the file with commas. The header is name,mobile,email,completedAt. A file that cannot be read says That file could not be read. Save it as a .csv with the header name,mobile,email,completedAt.
Inferred still needs a real Job on the row (completedAt) or that row is skipped. On Active and Grace, a row with no completion time still brings the Customer in. The result says how many rows had no job date. Those rows are not Failed, and one missing date does not refuse the file. The imported Job remembers the file name, cut to 80 characters. A Job you add by hand does not. A skipped row does not create a Customer and does not change one that is already there. Invalid rows are reported and skipped. The page says how many were skipped and that a skipped row needs a name and an Australian mobile or an email. An extra column adds This row has too many columns. Each row is name, mobile, email, completedAt. Zero valid rows fails — No Customers were imported. Each row needs a name and an Australian mobile or an email. When every row has an extra column, the page says This row has too many columns. Each row is name, mobile, email, completedAt. A completion time that is not a date, such as 13/13/2026, says A completion time has to be a real date and time. Check completedAt and Import again. No Consent is recorded for nothing. A second row with the same mobile, or the same email when there is no mobile, is the same Customer. A second Import with a new completion time reports the Jobs added and says that no new Customers were. The same completion time does not add another Job and is not counted. When the file adds neither a Customer nor a Job, and nothing was skipped, the page says Nothing new was imported.
You can Import before Google Connection. Sending stays blocked until the Business is sendable.
Opt-out
The Customer withdraws Consent on one Channel. Opt-out is not Customer Deletion.
SMS: reply STOP. RatePulse remembers that Australian mobile for this Business. Deleting the Customer and adding the same mobile again keeps the Opt-out. Send says not sendable: opted out of SMS. The Customers list shows SMS opted out.
SMS stays off until the Customer replies START (also YES or UNSTOP). When that mobile is opted out for more than one Business, START turns SMS back on only for the Business that last sent that mobile an SMS, when that send can be told apart. When RatePulse cannot tell which Business the reply belongs to, START turns SMS back on for every Business that stored that mobile. Recording Express means they asked again. It does not turn SMS back on, and there is no control that forces it. The page says SMS stays off until they reply START.
Email: unsubscribe in the Email. Email stays withdrawn until Express Consent is given again.
That Channel is then not sendable. The other Channel is unchanged unless they Opt-out there too. No Reminder after Opt-out.
If Send says not sendable
no Consent on SMS or no Consent on Email — on Customers, open that person's Actions, then Correction. Choose Text or email and They asked to hear from you or This job is why you are contacting them, then Save Correction. Those are recorded as Express or Inferred. Choosing None yet for the Channel that is showing and None yet for the reason, then Save Correction, removes Consent on that Channel and does not clear an SMS Opt-out. The Customers badge names where it was recorded, for example SMS Express or Email Express. Send uses SMS when SMS Consent exists on an SMS-capable mobile. Otherwise it uses Email when Email Consent exists. When Add Customer or Correction has an Australian mobile filled in and Text or email is Email, the form says The ask goes by email. SMS needs its own Consent. Inferred needs a Job. Inferred while that Channel is opted out is refused. The other Channel stays.
A bad mobile or a bad email on Correction is refused and the saved values stay. Clearing the mobile keeps the email. The Customer is then email only until an Australian mobile is saved again.
Cool-down — 6 months after a send on that Channel, or 3 or 12 months when the Owner saved that. Not a missing Consent.
deleted — Customer Deletion, not Opt-out.
More causes: Why a Review Request did not send.