Tradesly · Guide
Do-not-call, opt-outs and consent in plain language
See how consent, do-not-call, opt-outs, and quiet hours stay attached to customer activity.
Calling and texting permissions are business records, not assumptions. Tradesly keeps the visible consent and restriction records your team saves, and its AI teammates check those records before outbound contact.
Your business remains responsible for collecting the required permission, keeping the source evidence, honoring requests expressed in ordinary language, and checking every system that can contact the person.
1 Treat calling and texting separately
A Do not call result blocks AI outbound calls to that lead. The restriction stays with the lead across Call Lists, so uploading a new list that contains the same person does not make them callable again. Do not create a duplicate lead or change a number to work around the status.
An SMS opt-out blocks AI text messages. Calling and texting remain separate statuses, so read both when a customer has used more than one channel.
When a person asks not to be contacted, record and honor the request according to its words and your policy. If the request is broad—“do not contact me again”—do not narrow it to one channel merely because the product shows separate controls.
2 The steps
Read the Compliance card.
On the Sales Caller’s Setup tab, read all five statements before selecting them and pressing Confirm all five. Use Re-confirm after a material change. The confirmation is your attestation, not a legal audit.
Set a conservative calling window.
Under Time to call, choose Days, From, and Until. Consider the recipient’s location and any stricter state or local rule rather than relying only on the company timezone.
Review every imported audience.
Select the permission attestation only when your business holds the underlying records for the intended contact. Leave uncertain rows out and keep the source evidence.
Record verbal consent on the ticket.
Choose the consent disposition your business uses and add a note when the scope needs explanation. The disposition remains in the Ticket List.
Check the lead before contacting them.
Read the SMS and calling statuses, recent conversation, and dispositions. A Do not call lead will not be called by the AI, including from a newly uploaded list.
3 STOP and later requests to resume
Tradesly recognizes STOP and other supported SMS opt-out keywords. Treat any clear message such as “please stop texting me” as an opt-out even when it does not use the expected keyword. Staff should not try another thread, number, or channel to bypass the request.
A later START may allow AI messaging to resume. The earlier STOP event remains in the history, so your team can see the sequence. Confirm the intended messages are permitted before resuming.
4 Record verbal consent on the ticket
When a customer gives verbal consent during a call, save the appropriate disposition on that ticket. The disposition is kept permanently in the Ticket List as the visible record of what was captured on the conversation. Use a disposition your business has defined for that purpose, and add a note when the scope or wording needs context.
The permanent record does not mean permission can never change. If the customer later withdraws consent or asks not to be called, record the new outcome and honor the current restriction. The history shows both events.
5 Attestations support the record
The import and Call List confirmations record what an admin attested. They do not inspect your source file, create permission, or prove that a past customer agreed to receive the specific call or text you plan to send. Keep the original permission record with its date, wording, business, channel, purpose, and any other information your policy or law requires.
For verbal consent, the saved ticket disposition is the durable product record. Keep any additional evidence your business requires for the channel, purpose, and law that apply to the outreach.
6 AI quiet hours and human judgment
Every call or message initiated by an AI teammate observes the quiet or calling hours configured for that workflow. When the window is closed, the AI waits.
A human teammate can still manually call or send a message outside those hours. The product does not prevent that manual override, so train staff on your business policy and the recipient-local rules that apply before they contact someone themselves.
When statuses disagree or a restricted message appears to have been sent, stop further outreach and contact support with the lead or ticket identifier. Avoid sending full customer records through ordinary email.