Part 1
Lead reactivation
How your list is checked, ranked and worked — what leaves your side, what never does, and the rules your industry adds.
What we take, where it goes, and who sees it.
For owners, office managers and counsel
Lead reactivation works the leads your business has already paid for — people who asked for an estimate, a bid or a design consultation, were followed up once or twice, and then were not. We rank them by likelihood to book and work the list from the top, so your estimators spend their time on the people most likely to sign.
No federal financial-privacy law covers a contractor’s lead list. What does apply is strict enough: telemarketing law, which puts a price on every unwanted text, and state licensing rules that treat a message offering your services as advertising. This document sets out, control by control, how the engagement keeps your business inside those rules — and which decisions stay with you. The privacy controls go further than the law asks of a contractor. We apply them anyway.
Sections 02 to 06 are the plain-English part. They show the whole system in pictures, explain the four things the ranking looks at, and follow one example lead from your CRM to your estimator’s desk. The sections after them are the detail your counsel will check.
01
Commitments
Ten commitments, before the detail
- 01 · Direct identifiers never reach an AI provider — Names, phone numbers, emails and job addresses stay in a secure environment. The AI provider sees a random ID and a few short facts, nothing more.
- 02 · Nothing goes out without your approval — You approve every template and every batch before use. Our review sits on top of yours, never in place of it.
- 03 · Every message carries your name and license — Each template shows your business name and the license or registration number the job’s state requires. Messages go out as you, from your channels.
- 04 · No evidenced consent, no text message — Consent, opt-outs, Do Not Call status and quiet hours are checked at the moment of sending. Opt-outs are permanent.
- 05 · Your data serves your engagement only — No model training, no reuse across clients, no sale, no outside enrichment without your written instruction.
- 06 · Breach notice within 72 hours — As soon as possible and no later than 72 hours — well inside the time state breach laws give your business to notify customers.
- 07 · Return and destruction, certified — At the end of the engagement your data, including the identity key, is returned or destroyed, and we confirm it in writing.
- 08 · We schedule; your team sells — Messages invite a conversation or a visit with your estimator. We never quote, negotiate scope or price, or sign anyone up.
- 09 · A fee structure your counsel chooses — A flat fee or a results-based fee, with how each is treated under contractor rules set out in section 14.
- 10 · Evidence on request — Every control here has something you can inspect. We complete any vendor questionnaire you, or your own customers, send.
02
The whole picture
The system on one page
The system works in three zones. Names and contact details stay on your side. Our scoring works only with a random ID and a few short facts. The results come back to your side, where you approve and send.
Outcomes (booked, estimated, signed) come back by random ID and improve your ranking only. G1 — the agreement and intake review — clears before any data moves. G7 covers retention and destruction.
Dashed gold-edged boxes, marked G1 to G7, are compliance gates. Nothing passes a gate until it clears. Section 03 lists what each one checks.
03
Step by step
From our first conversation to the first message
Seventeen steps in five phases. The gate marks show where a compliance check has to clear before the work moves on.
Onboard (before any data)
- 01 First conversation — How your business works its leads today
- 02 Agreement — Roles, purpose, subprocessors, 72-hour notice
G1 - 03 Intake review — Lead sources, consent wording, licenses by state
G1 - 04 Secure environment — In your environment, or our workstation
Prepare (on your side)
- 05 Map your stages — Your CRM statuses to eight shared stages
- 06 Check the list — Opt-outs, Do Not Call, open bids, disputes
G2 - 07 Swap names for IDs — A random ID; the key stays with you
- 08 Notes into facts — Fixed-list answers; budgets become tiers
G3
Rank (Tez scoring)
- 09 Score — Intent, Opening, Reachability, Fit
- 10 Tier and reasons — A to D, with the top reasons
- 11 Short summary — Why call, and an opening line, checked
G4 - 12 Next step — Channel by consent, and timing
Act (on your side)
- 13 Match back — The ranked list appears in your CRM
- 14 Your approval — Owner or manager approves the wording
G5 - 15 Send — Re-checked at sending; license number in
G6
Learn (ongoing)
- 16 Record outcomes — Booked, estimated, signed; a held-back group
- 17 Improve and report — Your ranking only; results you can check
G7
| Gate | When | What has to be true to pass | Who decides |
|---|---|---|---|
| G1 | Before any data | Signed agreement; your lead sources, consent wording and opt-out records reviewed; the states you work in, your license or registration numbers and your fee model confirmed | Your business and Tez |
| G2 | As the list arrives | Opt-outs, Do Not Call, current jobs, disputes, public bids still open and anyone hostile are set aside and never ranked | Software, on your rules |
| G3 | Before anything leaves your side | Only approved facts cross: no names, contact details, addresses, notes, exact figures or exact dates | Software, checked by Tez |
| G4 | After a summary is drafted | No personal data, no prices or financing terms, no testimonials, nothing the facts do not support | Software, then your team |
| G5 | Before any outreach | You approve the wording and the batch | Your business |
| G6 | At the moment of sending | Consent for that channel, Do Not Call, quiet hours in the lead’s time zone, opt-outs, the right license number for the job’s state | Software, on your channels |
| G7 | Throughout, and at the end | Outcomes kept by random ID, used for your business only, returned or destroyed at termination | Tez, certified to you |
04
The ranking
How the list is put in order
Every lead is checked first, then looked at through four factors. The factors combine into one score, and the list is sorted by it. The sorting is plain arithmetic, not an AI model, so every score can be explained in a sentence.
| Factor | The question it answers | What it looks at, for a construction business |
|---|---|---|
| Intent | How serious were they, and how long ago? | How far they got: inquiry, site visit, estimate or bid delivered, design or plans started. Time since the last real conversation. Whether they replied before. How many follow-ups have already been tried. |
| Opening | Is there a real reason to get back in touch? | The reason they paused: budget, timing, financing, a permit or HOA approval, another bid. A condition they named, such as “after we close on the house” or “next spring.” Whether that moment has now passed. |
| Reachability | Can we reach them, and are we allowed to? | A working email or phone. Consent on file for each channel. Do Not Call status, and whether the three-month inquiry window has passed. |
| Fit | Can you still take the job? | A job inside your service area and a state you are licensed in. Whether it meets your minimum job size, as a yes or no only. Whether it is work your crews still do. |
How the ranking gets better
- 01It starts from your team’s experience — Your estimators tell us how often each kind of stalled lead comes back. Those estimates set the first odds. Until your results come in, the scores are educated estimates, and we say so.
- 02It corrects itself from your results — As visits are booked, estimates delivered and jobs signed or lost, the odds for each reason move toward what actually happened at your business.
- 03It becomes a model of your business alone — After about 300 recorded outcomes, the ranking is fitted to your business’s results. It is never trained on, or pooled with, another business’s data.
- 04A held-back group keeps us honest — With your agreement, about one lead in ten is held back and not contacted for a set period. Comparing the two groups shows what the outreach actually changed, rather than what would have happened anyway.
05
A worked example
One lead, from your CRM to your estimator
Daniel Ortiz is fictional, and so is his address. His record is shaped like a real one: a kitchen remodel in California, estimate delivered, then nothing. Follow it through the four cards, left to right and top to bottom.
1 · Your CRM record (stays with you)
| Field | Value | Note |
|---|---|---|
| name | Daniel Ortiz | key table |
| phone | (916) 555-0172 | key table |
| d.ortiz@example.com | key table | |
| job address | 1180 Alder Way, Sacramento, CA | key table |
| status | Estimate sent – no decision | becomes a stage |
| note | Loved the layout; wants to wait until they refinance in the spring | becomes facts |
| estimate | $68,500 | becomes a tier |
| last contact | February 20, 2026 | becomes days |
2 · What we receive (leaves your side)
| Field | Value | Note |
|---|---|---|
| ID | s_4Hn8tR1c | random |
| stage | Estimate delivered | Intent |
| days since | 228 | Intent |
| reason | Financing or timing | Opening |
| condition | Yes, waiting on an event | Opening |
| reach | Email yes · text no consent | Reachability |
| fit | Service area yes · licensed state yes · minimum yes | Fit |
| value tier | 2 of 3, only if you opt in | optional |
Never leaves your side: his name, phone, email, address, the note itself, the estimate amount, exact dates.
3 · What comes back (back to you)
| Field | Value | Note |
|---|---|---|
| ID | s_4Hn8tR1c | |
| score | 68 · tier A | |
| reasons | + named a condition · + estimate delivered · − 228 days since contact | |
| reason line | Estimate delivered; paused for an event that should have passed. | fixed wording |
| summary | He paused until something he was waiting on in the spring. That has likely passed. A good opener is to ask whether the timing works now. | AI, checked |
| next step | Email, Tuesday morning his time |
4 · In your CRM (stays with you)
| Field | Value | Note |
|---|---|---|
| record | Daniel Ortiz · tier A · 68 | matched back |
| fields | Reason line, summary and next step added to his record | |
| draft | “Hi {first_name}, …” signed with your business name and California license number; his name filled in only at sending | placeholder |
| flags | Text blocked, no consent · Do Not Call check required | G6 |
No text consent on file, so the next step is email. His inquiry is over three months old and he never signed, so a Do Not Call check comes before any call. Your estimator sees his name here, in your own CRM, for the first time.
- 01His note became a few facts — “Refinance in the spring” left only as “waiting on an event.” If you approve a short list of event types, the summary can be more specific without the note ever leaving. The draft never mentions loans or rates; that conversation is yours.
06
The suggestion
How the “why call” note is written and checked
Each lead comes back with a reason line in fixed wording and a short summary drafted by an AI model, both written only from the facts in card 2 of section 05. The AI writes; it does not decide. The order comes from arithmetic, and you approve anything sent.
The four checks at gate G4
- No personal data — The draft may not contain a name, number, email or address. Names appear only as a placeholder, filled in on your side at sending.
- No prices, no promises — No quotes, price ranges, discounts, payment or financing terms, deadlines or guarantees. The draft invites a conversation with your estimator, nothing more.
- Nothing made up — Every statement must trace back to a fact it was given. No reviews, ratings or testimonials unless you supply them with their source.
- Your never-say list — Phrases and topics your business rules out are blocked, on top of the general rules above.
07
Roles
Your business owns the relationship
No financial-privacy regulator assigns roles here, so we take the one state privacy laws give a vendor: your business decides what the data is for, and Tez I Solutions acts only on your written instructions, as your service provider. We never use, sell or share it for anything else. Under telemarketing law the sender of a message can be liable for it directly, so we carry our share of that ourselves rather than leaving it to the contract. This is how responsibility divides.
| Obligation | Your business | Tez I Solutions |
|---|---|---|
| Licensing and advertising rules | Owns your license or registration, and the number each state requires | Puts your business name and the right number on every template |
| Approval of communications | Approves before use | Submits templates; never alters approved wording; keeps the draft, approved version and approver |
| Selling the work | Your team quotes, negotiates and signs | Schedules conversations only; never quotes or negotiates |
| How leads were obtained | Warrants it in the agreement | Records the consent source and enforces it at send time |
| In-home sales and cancellation rights | Owns your contracts and cancellation notices | Never presses a lead to sign quickly or discourages a cancellation |
| Security of data we hold | Oversees | Operates the controls in sections 10 and 11 |
| Breach notice to customers | Owns, within your state’s deadline | Notifies you within 72 hours and supports the investigation |
| Vendor questionnaires | Sends one if you, or your own customers, require it | Completes it and supplies evidence |
| Access and deletion requests | Receives and instructs | Executes within your deadline and confirms |
| Return or destruction | Instructs | Executes and certifies in writing |
08
Data
What we take, and what we never take
The least data that lets the list be ranked and worked. Where a figure carries signal, we keep a tier and drop the figure.
| Data | How it is handled | Reaches the AI model |
|---|---|---|
| Name, phone, email, job and mailing address | Held only in the encrypted key table on your side; used to address a message when it is sent. The job’s location crosses only as yes or no. | No |
| Social Security, driver’s license, bank and card numbers; credit applications | Excluded from the export. If one appears in a note, the record is quarantined and the value removed. | No |
| Estimate and budget amounts, home value, income | Only if you agree: the estimate becomes a three-level tier on your side. Your minimum job size becomes a yes or no. The figure never leaves. | No |
| Inquiry, estimate and contact dates | Converted to intervals — “14 months since last contact.” | Interval only |
| Lead source, project type, stage, status, estimator | Kept as categories; estimator names replaced with codes. | As categories |
| Call, site-visit and estimate notes | Read on your side and turned into fixed-list answers (section 09). The note itself never leaves. | Fixed-list answers only |
| Consent records and opt-outs | Kept as an append-only history and enforced at send time. | No |
| Photos, plans, permit files; age, gender, ethnicity, health, family status | Not requested, not used to rank, not sent. | No |
09
The privacy layer
Where AI sits, and what it sees
| Station | What happens | Holds or sees |
|---|---|---|
| 01 · Your business — Your CRM | Full records stay here. Only the agreed fields are read. | Holds: everything, as today |
| 02 · Secure env. — Separation, and notes into facts | A local model with no outside connection answers fixed questions about each note. The key lives only here. | Holds: identifiers, key table, notes |
| 03 · Tez scoring — Ranking, then a short summary | Ranking is arithmetic in our own code. Anthropic’s Claude words a summary from the facts. | Sees: random ID, fixed-list facts |
| 04 · Your channels — Approved, then sent | Names and your license number filled in on your side; consent checked; sent from your channels. | Holds: the message, in your records |
Notes are the most sensitive part of a record and the most useful. So they are read where they already are, and only short answers leave. Five layers make sure of it.
| Layer | What it does |
|---|---|
| 1 · Field allow-list | Only approved columns are read. Structured identifiers are separated by rule, not by a model’s judgement. |
| 2 · Identifiers stripped first | Phone numbers, emails, street addresses, account and card numbers, Social Security and driver’s license numbers, dollar amounts and dates are removed from a note before the local model reads it. |
| 3 · Fixed questions, fixed answers | The local model answers set questions — why they paused, whether they named a condition, which kind of event — by choosing from a list you have seen. It cannot write free text. |
| 4 · Unsure means a person decides | An answer the model is not confident about is not guessed. The record is held for a person to review. The process fails closed. |
| 5 · Final scan | Every record is scanned again before it leaves. A record carrying anything outside the approved fields is held back, not sent. |
10
Where it runs
Two ways to run the secure environment
The secure environment is where identifiable data lives during the engagement, and your business chooses where it sits. In both options the key table never leaves it, and the AI provider receives only a random ID and fixed-list facts.
| Inside your environment | On a Tez-operated workstation | |
|---|---|---|
| Where raw data sits | Your infrastructure; it never leaves your perimeter | An encrypted workstation operated by Tez, in a separate encrypted volume per client |
| Access | You control it. We use a named, least-privilege account you can revoke at any time | One named individual, with multi-factor authentication |
| Network | Your controls | Outbound limited to the AI provider and your sending channels |
| Logging | Your logging stack | Access log kept for the engagement, provided on request |
| Suits | Businesses with an IT team or managed IT provider | Businesses without capacity to host it — most contractors |
Workstation standard, when Tez operates it
- Encrypted at rest — Full-disk encryption, as Massachusetts 201 CMR 17.00 requires for laptops, plus a separate encrypted volume for each client’s data.
- Dedicated and locked down — An OS account used only for client data, multi-factor sign-in, screen lock, current patches, endpoint protection.
- No cloud sync — Client data is never stored in a synced folder or consumer cloud backup, and is excluded from sync by configuration.
- Wiped at the end — Your volume is destroyed at termination and the destruction certified in writing.
11
Security and incidents
The controls, and what happens if one fails
| Control | Evidence you can ask for |
|---|---|
| Written information security program, modelled on Massachusetts 201 CMR 17.00 — the most specific state standard, applied in every state | The program document |
| Encryption in transit and at rest | Configuration record |
| Multi-factor authentication on every account that touches your data | Account inventory |
| Access limited to named individuals, reviewed quarterly | Access list and review log |
| Access to your data logged | Log extract |
| Background check for anyone with access, on your request | Written confirmation |
| Raw data held only for the life of the engagement | Retention schedule |
| Return or destruction within 30 days of termination | Signed certificate |
| Cyber liability insurance, where your contract requires it | Certificate of insurance |
| Written incident response plan, reviewed each year | The plan and its last review |
If something goes wrong
- 01 · Contain — Stop sending, revoke the affected credential, isolate the system.
- 02 · Notify you within 72 hours at the latest — As soon as possible — Texas law says immediately — with which records and fields, what window, what we have done. Updates follow.
- 03 · Preserve evidence — Logs, send records and the consent history are kept intact for your investigation.
- 04 · Support your notice, never pre-empt it — Customer notice is your decision, within your state’s deadline — 30 days in Florida, 60 in Texas. We never contact your customers about it.
12
Licensing and advertising
Every message is your advertisement
To a licensing board, a text or email offering your services is advertising. California counts any electronic transmission; Florida means any medium; New Jersey includes correspondence with consumers. Your advertising rules apply to every message we draft.
- 01Your license number on every message — Your business name and the number the job’s state requires — California CSLB, Florida DBPR, Maryland MHIC, Massachusetts HIC, New Jersey “HIC reg. #”. A template with no number for the lead’s state does not send.
- 02We schedule; your team sells — California exempts someone who only schedules appointments for a registered salesperson; Maryland licenses anyone who seeks to get a home-improvement contract. So we invite a visit, nothing more; replies go to your estimator.
- 03No made-up praise — The FTC’s rule on reviews (16 CFR 465) bans fake, bought and undisclosed insider reviews and testimonials. Drafts carry none unless you supply the source, and never offer anything for a review.
- 04Financing claims only with the disclosures — “Financing available” is fine. A monthly payment, down payment, number of payments or finance charge triggers Regulation Z: the message must then give the down payment, repayment terms and APR, or it is blocked.
- 05We book the visit; we never rush the signature — A job sold in the customer’s home carries a cancellation right, usually three business days, under the FTC Cooling-Off Rule and state laws. That is your contract’s duty; we never press anyone to sign.
- 06Open public bids are left alone — Many public owners forbid contact during an open solicitation; under Miami-Dade County’s “Cone of Silence” a breach can make the award voidable. Such leads are set aside at gate G2 until you confirm it has closed.
13
Consent
No evidenced consent, no text message
Under the Telephone Consumer Protection Act the party that sends a message can be liable for it directly. Courts have narrowed the autodialer definition and no longer defer to the FCC, so we rely on neither: consent is enforced in software at the moment of sending. Commercial leads are no exception — a mobile number is covered whoever pays the bill.
- 01 · A consent history, not a checkbox — Each lead’s consent is an append-only record of source, wording, channel and date. Contactability is derived from it, never overwritten.
- 02 · Checked when the message sends — Consent, suppression, Do Not Call and quiet hours are rechecked at sending, not at list-building. Yesterday’s opt-out holds today.
- 03 · Aged leads without evidenced consent — Email, or your team calling directly — not text. An estimate request over three months old, with no job sold, is no established business relationship for Do Not Call.
- 04 · Do Not Call and reassigned numbers — Checked against the National Do Not Call Registry and the FCC Reassigned Numbers Database. Results dated and stored.
- 05 · Quiet hours and state law — 8am to 9pm local time; 8am to 8pm where Florida, Maryland or Washington law sets it.
- 06 · Opt-out everywhere, permanently — STOP, a request in any words, or one made to your office is honoured on every channel and survives any re-import. Email unsubscribes within 10 business days.
14
How we are paid
Two fee models, and how each is treated
We offer two models. Fees are set in conversation and are not in this document. We found no rule that bars a contractor from paying a marketing vendor either way. What matters is what the vendor does and whether its pay is tied to work sold — so here is how each model reads under the rules in section 12, for your counsel to weigh.
Model A: Flat monthly fee
A fixed fee for operating the service. It does not depend on visits booked, jobs sold or contract value.
- Home improvement. Pay not tied to contracts sold supports the reading that we run your outreach rather than sell your work — alongside the fact that we never quote or negotiate.
- New homes. The fee is not tied to any home sale, so no real-estate commission question arises.
- The simplest model to approve and document.
Model B: Results-based fee
A share of revenue from reactivated jobs, measured from your CRM’s own records.
- Home improvement. Where selling requires a salesperson registration or license, as in California and Maryland, pay tied to contracts sold makes the paid party look more like a salesperson. Tez I Solutions holds neither.
- New homes sold with land. A share of a sale paid to whoever procured the buyer can require a real-estate license in some states, Texas among them.
- Commercial work. Home-improvement salesperson rules generally do not reach it, so the question is narrower — but it is still asked state by state.
- Offered only where your counsel confirms, for each state you work in, that it needs no registration or license on our side.
15
Subprocessors and contract
Who else touches the data, and what we sign
| Subprocessor | What it holds | When |
|---|---|---|
| Anthropic (Claude API) | A random ID and fixed-list facts only. No names, contact details, notes or exact figures. Not used for training by default under Anthropic’s commercial terms; zero data retention requested where offered; can run through your own cloud provider instead | Every engagement |
| Your CRM, email and texting providers | Messages, as they do today | Every engagement, under your contracts |
| Messaging provider operated by Tez | Phone numbers and message content | Only if you do not send through your own texting channel, with every message and reply copied into your CRM |
| Operator console hosting | Named in your agreement, with what it holds | Where your team uses our console |
The full list is an exhibit to your agreement. We give 30 days’ notice before adding or changing a subprocessor.
What the agreement contains
- Roles and purpose — Your business decides; Tez acts on written instructions as your service provider. Use limited to this engagement.
- No secondary use — No training, no sale, no reuse across clients, no enrichment without written instruction.
- Security exhibit and 72-hour notice — The controls in sections 09 to 11, as binding terms.
- Consent and license warranty — Your representation of how the leads were obtained, and of the licenses and registrations you hold.
- Privacy requests — Access, correction and deletion within your deadlines, under any state privacy law that applies to your business.
- Audit, return and destruction — Reasonable audit and questionnaire rights; return or certified destruction at termination.
16
Regulatory map
Each rule, and where it is addressed
| Rule | What it requires here | Section |
|---|---|---|
| State contractor licensing and advertising laws (CA, FL, MD, MA, NJ) | License or registration number in advertising and correspondence | 01 05 12 |
| California HIS registration; Maryland salesperson license | Who may solicit or sell home improvement, and how they are paid | 12 14 |
| FTC Act section 5; 16 CFR Part 465 | Truthful claims; no fake or bought reviews or testimonials | 06 12 |
| Regulation Z, 12 CFR 1026.24 | Financing trigger terms and the disclosures they require | 06 12 |
| FTC Cooling-Off Rule, 16 CFR Part 429 | Cancellation right for in-home sales | 07 12 |
| Public procurement contact rules | No contact during open solicitations | 03 12 |
| TCPA and the Do Not Call rules | Consent, revocation, Do Not Call, quiet hours | 13 |
| Telemarketing Sales Rule | Established business relationship windows | 13 |
| State telemarketing laws | State consent and calling-hours rules | 13 |
| CAN-SPAM | Unsubscribe, address, accurate headers, B2B included | 13 |
| Massachusetts 201 CMR 17.00 | Written security program, encryption | 10 11 |
| State breach notification laws | Vendor notice to you; your notice to customers | 01 11 |
| State comprehensive privacy laws | Service-provider terms; access, deletion, no sale | 07 15 |
| State real-estate licensing laws | Pay tied to selling a new home with its land | 14 |
| NIST IR 8053, SP 800-188 | De-identification practice | 08 09 |
17
References
Every requirement, traced to its source
Each commitment in this document rests on a primary source: a statute, a regulation, a regulator’s own guidance, or a court decision. They are listed here so your counsel can check our reading against the text. Links were current in October 2026.
| Contractor licensing and sales | Relied on for | Sections |
|---|---|---|
| California CSLB, License and Contracting Requirements for Online Home Improvement Marketplace Companies (Fast Facts): B&P Code 7026, 7027.1, 7030.5, 7152, 7154; 16 CCR 861 (cslb.ca.gov/Resources/IndustryBulletins/Online_Marketplace_Fast_Facts.pdf) | License number in all advertising, electronic transmission included; referral services may not solicit or negotiate contracts | 05 12 |
| California CSLB, Home Improvement Salesperson registration requirements (cslb.ca.gov/Contractors/Applicants/Home_Improvement_Registration/Before_Applying_For_HIS.aspx) | Who must register; the exemption for scheduling appointments only | 12 14 |
| Florida Statutes 489.119(5) (flsenate.gov/Laws/Statutes/2025/489.119) | Number on each offer of services, bid or advertisement, regardless of medium | 12 |
| Maryland Code, Business Regulation 8-101, 8-301, 8-601 (mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gbr§ion=8-301) | Salesperson license to sell, including seeking to get a contract; telephone-only exemption | 12 14 |
| Massachusetts General Laws c. 142A, sections 13 and 17 (malegislature.gov/Laws/GeneralLaws/PartI/TitleXX/Chapter142A/Section13) | Registration number on every advertisement | 12 |
| Massachusetts 201 CMR 18.00, Home Improvement Contractor Program (mass.gov/doc/201-cmr-18-registration-and-enforcement-of-home-improvement-contractor-program/download) | “Advertisement” includes electronic media | 12 |
| New Jersey Contractors’ Registration Act, N.J.S.A. 56:8-136 et seq., incl. 56:8-144; Division of Consumer Affairs FAQ (njconsumeraffairs.gov/hic/Pages/FAQ.aspx) | Registration number on advertisements and correspondence with consumers | 12 |
| Texas Occupations Code ch. 1101, Real Estate License Act, incl. 1101.002 and 1101.005 (statutes.capitol.texas.gov/Docs/OC/htm/OC.1101.htm) | Procuring a buyer for compensation as a licensed act; the owner’s-employee exemption | 14 |
| Consumer protection and procurement | Relied on for | Sections |
|---|---|---|
| FTC Act section 5, 15 U.S.C. 45 (law.cornell.edu/uscode/text/15/45) | Claims in a message must be truthful and substantiated | 06 12 |
| FTC, Trade Regulation Rule on the Use of Consumer Reviews and Testimonials, 16 CFR Part 465 (2024) (ecfr.gov/current/title-16/chapter-I/subchapter-D/part-465) | No fake, bought or undisclosed insider reviews or testimonials | 06 12 |
| Regulation Z, 12 CFR 1026.24, Advertising (ecfr.gov/current/title-12/chapter-X/part-1026/subpart-C/section-1026.24) | Financing trigger terms and the disclosures they require | 06 12 |
| FTC Cooling-Off Rule, 16 CFR Part 429 (ecfr.gov/current/title-16/chapter-I/subchapter-D/part-429) | Three-day cancellation right for sales made in the buyer’s home, including after an invitation | 07 12 |
| Miami-Dade County Code 2-11.1(t), Cone of Silence (miamidade.gov/global/strategic-procurement/procedures-cone-of-silence.page) | An example of a no-contact rule during open public solicitations | 03 12 |
| Telemarketing and email | Relied on for | Sections |
|---|---|---|
| Telephone Consumer Protection Act, 47 U.S.C. 227 (law.cornell.edu/uscode/text/47/227) | Consent for marketing texts and calls; statutory damages; sender liability | 13 |
| FCC rules, 47 CFR 64.1200 (ecfr.gov/current/title-47/chapter-I/subchapter-B/part-64/subpart-L/section-64.1200) | Prior express written consent, Do Not Call, quiet hours, revocation of consent | 13 18 |
| Telemarketing Sales Rule, 16 CFR Part 310 (ecfr.gov/current/title-16/chapter-I/subchapter-C/part-310) | Established business relationship: 18 months after a transaction, 3 months after an inquiry | 13 |
| National Do Not Call Registry; FCC Reassigned Numbers Database (donotcall.gov · reassigned.us) | The two checks run before any number is contacted | 13 |
| Facebook, Inc. v. Duguid, 592 U.S. 395 (2021); McLaughlin Chiropractic Associates v. McKesson Corp. (U.S. Supreme Court, June 2025) | Autodialer scope narrowed; courts not bound by FCC readings of the TCPA | 13 |
| Florida Telephone Solicitation Act, Fla. Stat. 501.059; Texas SB 140 (2025), Tex. Bus. & Com. Code ch. 302 | State rules that treat texts as solicitation | 13 |
| CAN-SPAM Act, 15 U.S.C. 7701 et seq.; FTC compliance guide (ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business) | Unsubscribe within 10 business days, physical address, accurate headers; no B2B exception | 13 |
| Privacy, security and AI | Relied on for | Sections |
|---|---|---|
| Massachusetts 201 CMR 17.00 (mass.gov/regulations/201-CMR-1700-standards-for-the-protection-of-personal-information-of-ma-residents) | Written security program, encryption on laptops and in transit, service-provider contracts | 10 11 |
| Florida Statutes 501.171, Security of confidential personal information (flsenate.gov/Laws/Statutes/2025/501.171) | Customer notice within 30 days; a vendor tells the business within 10 days | 01 11 |
| Texas Business and Commerce Code 521.053 (statutes.capitol.texas.gov/Docs/BC/htm/BC.521.htm) | A vendor tells the data owner immediately; customer notice within 60 days | 01 11 |
| California Consumer Privacy Act, Cal. Civ. Code 1798.100 et seq.; CPPA threshold adjustment (cppa.ca.gov/regulations/cpi_adjustment.html) | Which businesses are covered; service-provider contract terms | 07 15 |
| Texas Data Privacy and Security Act, Tex. Bus. & Com. Code ch. 541, incl. 541.002 and 541.107 | Small-business exclusion; no sale of sensitive data without consent | 07 15 |
| NIST IR 8053, De-Identification of Personal Information, 2015 (nvlpubs.nist.gov/nistpubs/ir/2015/NIST.IR.8053.pdf) | Quasi-identifiers, re-identification risk, why pseudonymization is reversible | 08 09 |
| NIST SP 800-188, De-Identifying Government Datasets, 2023 (csrc.nist.gov/pubs/sp/800/188/final) | Generalization of figures into bands; de-identification as risk reduction | 08 09 |
| Anthropic, Commercial Terms of Service (anthropic.com/legal/commercial-terms) | No training on commercial API inputs and outputs by default | 09 15 |
18
Limits
What this document is not
- 01Not legal advice — Your counsel decides how these rules apply in the states and cities you work in. This document tells them what we do so they can. It covers the states named; licensing rules elsewhere are confirmed at intake.
- 02Not a SOC 2 report — We do not hold a SOC 2 attestation. We complete your vendor questionnaire and provide the policies and evidence behind each control instead.
- 03Not a contractor or salesperson — Tez I Solutions holds no contractor license, salesperson registration or real-estate license. It does not quote, bid or negotiate work, and it does not sign contracts on your behalf.
- 04Not permanent — Current as of October 2026. Rules in this area are moving — the FCC adopted further changes to its consent revocation rules in autumn 2026, and Texas’s text-message rule is in litigation. We review this document at least once a year and whenever a rule it relies on changes.
- 05Not a promise of results — A score says which leads to contact first, not who will book. Until your own outcomes are recorded, the odds behind it are estimates drawn from your team’s experience.
Part 2
AI services
How we handle your data inside your AI tools.
AI services puts a standing AI engineer across the AI tools your business already pays for — ChatGPT, Claude, Copilot, Gemini and the AI inside the software you use. We connect those tools to your CRM, inbox, calendar and files, build the workflows that do the repeat work, set up your processes and brand voice inside them, train your team, and look after the accounts. The tools stay yours, under your own contracts with each vendor. That changes how data protection works. In lead reactivation we keep names and contact details away from the AI provider by design. Here, a tool connected to your CRM will see the records it needs to do its job, names included. So the protections in this document are about something else: whose account it is, what each connection can reach, what the vendor's terms allow, who approves a workflow before it goes live, and how our access ends. Sections A1 to A6 are the same for every business we work with. Your industry's page adds sections A7 and A8: what your industry's rules mean for your AI tools, and where those rules come from.
A1
Commitments
Ten commitments, before the detail
- 01 · Your accounts, on business terms — We work only in accounts your business owns, on business plans. Never in a personal or consumer account — ours, yours or an employee's.
- 02 · A named user, never a shared password — You add us as a named user with our own sign-in and multi-factor authentication. We never ask for a shared password, and you should never send one to us by email.
- 03 · The least access that does the job — Each connection reaches only the data its workflow needs. Admin rights are used for set-up tasks, logged, and reduced afterwards.
- 04 · Nothing goes live without your approval — Every connection, workflow and set of instructions is approved by you, in writing, before it is switched on. So is every change to one that is already running.
- 05 · Automated where it is routine, a person in the loop where it is not — Routine, rule-based work can run on its own once you have approved it: sorting and tagging, summaries for your team, filing, and fixed-wording notices such as an appointment reminder from a template you signed off. Anything that needs a decision or a judgement — a reply written for a particular customer, a price, a term, a commitment, or anything your industry's page marks for review — has a person on your side in the loop before it goes anywhere. Each workflow's data sheet (A3) states which kind it is. Where your industry's page requires a person to review every customer message, that rule applies instead.
- 06 · Your data stays in your tools — We build and test inside your workspace. We do not copy your business data into Tez's own AI accounts. Where we need examples outside your tools, we use made-up records.
- 07 · Your data serves your business only — No reuse across clients, no sale, no training of anything by us. Prompts, instructions and workflows built from your material are yours and are not reused for anyone else.
- 08 · Vendor data settings confirmed in writing — During onboarding we read each tool's current data terms, set its controls with you, and give you a written record. We re-check it whenever a vendor changes its terms.
- 09 · Incident notice within 72 hours — As soon as possible and no later than 72 hours, or sooner where your industry's page says so.
- 10 · Access removed, everything handed over — At the end, our access is removed, every credential we created is revoked or rotated, and every workflow is documented and handed over. We confirm it in writing within 30 days.
Evidence on request: every control in this document has a record you can inspect, listed in section A5. If you send us a security questionnaire, we complete it during onboarding.
A2
Accounts and access
Whose accounts, and how we get in
The AI tools, the systems they connect to and the accounts that run them all belong to your business. We are given access to them; we never hold them. That is what makes the work portable: if we part ways, everything keeps running and nothing has to be moved out of our name.
Nothing in this section starts before you have decided to work with us. The first session is a conversation. We do not ask for logins, exports or files beforehand.
Who owns what
| Item | Who owns it | How we handle it |
|---|---|---|
| AI subscriptions and workspaces | Your business — in its name, on its payment method | We administer them for you. If a new tool would genuinely pay for itself, we say so and why, and it goes on your account, not ours. |
| The owner or super-admin role | Your business keeps it, with at least one person on your side who is not us | We take the lowest role that does the work. Admin rights for a set-up task are logged and reduced when the task is done. |
| Our sign-in | A named user for each Tez person, in your directory or invited as a guest | Multi-factor authentication on. No shared logins. Never a password by email, text or chat. |
| Connections — API keys, app authorisations, service accounts | Created in your accounts, owned by you | Each one is named, listed in the access record (A5), scoped to its workflow, and stored where you control it — never pasted into a document or a message. |
| Personal and consumer AI accounts | Their owners | Not used for business work. If the audit finds business work in personal accounts, we tell you and recommend moving it to business seats. We never connect your systems to a personal account. |
How access is set up
- 01 · You decide what we need — We list the systems and the role each one needs, and why. You agree or strike items out.
- 02 · You add us — Usually by adding us as a user, on a call where we walk through it together. A password is never sent.
- 03 · We confirm the safeguards — Multi-factor authentication on, role as agreed, sign-in recorded in the access record.
- 04 · Reviewed every quarter — We go through the access record with you and remove anything no longer needed.
- 05 · Removed at the end — Section A5 sets out how access ends.
Roles
| Obligation | Your business | Tez I Solutions |
|---|---|---|
| Contracts with AI vendors | Holds them; the vendor processes your data under them | Reads the data terms and records them for you (A4) |
| Who on your team uses which tool | Decides | Sets up the seats and permissions you decide |
| Approval of workflows and changes | Approves before anything goes live | Proposes, documents and builds; never switches on without approval |
| Review of customer-facing output | Your people review before sending | Builds the review step into the workflow |
| Industry rules — licensing, records, supervision, privacy notices | Owns them | Builds to them as set out on your industry's page (A7) |
| Security of the access we hold | Oversees | Operates the controls in A5 |
| Notice to customers or regulators after an incident | Decides | Tells you within 72 hours and supports the investigation |
| Privacy requests from your customers | Receives and instructs | Helps find and remove the data in the tools we set up, within your deadline |
Where a state privacy law reaches your business, we act as your service provider or processor for the access we hold, and the agreement says so.
A3
What the tools can see
Connections, scopes, and what stays out
An AI tool connected to one of your systems can see whatever that connection lets it see. An assistant that searches your files can surface anything the person using it is allowed to open — Microsoft says of its own Copilot that it "only surfaces organizational data to which individual users have at least view permissions." So the work starts with permissions, not prompts.
Before anything is connected
- Who can see what — Before an assistant is pointed at a shared drive, inbox or CRM, we review who can open what. Folders that are open to everyone but should not be are fixed first, with your approval.
- One data sheet per workflow — Every workflow gets a written sheet: what it reads, what it writes, who sees the result, and where a person reviews it. You approve the sheet before we build.
- Add-ons are vendors too — A plug-in, connector, custom GPT or agent from a third party is another company handling your data. None is installed without your approval and a record of its data terms.
What a data sheet looks like
Illustration — not real client data.
| Workflow | Reads | Writes | Who sees the result | Human in the loop |
|---|---|---|---|---|
| Morning summary of new inquiries | CRM records created in the last 24 hours: name, source, service asked about, notes | One summary in the office manager's inbox | Office manager | Read before anyone acts on it |
| First-draft reply to a quote request | The single inquiry being answered; your approved reply templates and brand voice | A draft in the shared inbox — never sent | The person replying | Edited and sent by a person |
| Meeting notes to CRM | The transcript of a meeting the attendees agreed to record | A note on the matching CRM record | The account owner | Checked before it is saved |
What stays out by default
Unless your written decision says otherwise, after we have shown you what the vendor's terms and your industry's rules say, these are kept out of every prompt, instruction file and connection:
- Social Security numbers, tax IDs, driver's licence and other government ID numbers
- Full bank account and card numbers
- Passwords, access codes, gate, door and alarm codes
- Health information
- Anything your industry's page (A7) marks as restricted
Where a connection would expose one of these — a folder of scanned IDs, a CRM field holding card numbers — the connection is narrowed to leave it out, or not built.
Before a workflow goes live
| Check | What has to be true |
|---|---|
| Data sheet | Approved by you, in writing |
| Access | The connection reaches only what the sheet lists |
| Test | Run on made-up records, or on a small set of real ones you choose, with the results shown to you |
| Human in the loop | Marked on the data sheet. In place wherever a decision or judgement is involved: a reply written for a particular customer, a price or a term, or anything your industry's page marks for review. Routine, rule-based steps you have approved may run without one |
| Owner | A named person on your side who can pause it |
| Documentation | Written up and stored where you keep it |
AI tools make mistakes. Every workflow is built on the assumption that a draft can be wrong, which is why the review step is part of the design rather than a suggestion.
A4
Model providers and training
What the vendors do with your data, and how we check
When your team or a workflow uses ChatGPT, Claude, Copilot or Gemini, the vendor processes that data under its contract with your business. Tez is not a reseller or partner of any AI vendor, and not a party to those contracts. Whether a vendor trains its models on your data, how long it keeps prompts, whether its staff can review them, and where it processes them are set by the vendor's terms and by the plan you are on. Those terms change. So we do not promise what a vendor will do. We promise what we will do.
What we do
- 01 · List every tool — Each AI tool and AI feature you pay for, the plan it is on, and who holds a seat.
- 02 · Read the current terms — For each one we record what the vendor says about training on your data, retention, human review, where data is processed, and which admin controls exist. Each entry carries the date and the address of the page we read.
- 03 · Set the controls with you — Where a tool offers a choice — training opt-outs, retention periods, chat history, which add-ons are allowed — we recommend the most protective setting that still does what you need, and you decide.
- 04 · Give you the record — The settings record is yours, in writing. Your compliance contact can file it with your vendor reviews.
- 05 · Re-check when terms change — When a vendor changes its data terms, we re-read them, update the record and tell you if anything moved. We also re-check the whole record at least every six months.
What the main vendors said when we checked
Read on each vendor's own page on 6 October 2026. This is the vendor's statement to its customers, not a commitment by Tez. If it changes, the vendor's current terms govern, and we update your record.
| Vendor | What its page said | Where |
|---|---|---|
| Anthropic — Claude, under its Commercial Terms | "Anthropic may not train models on Customer Content from Services." The Commercial Terms cover Anthropic's API and the business offerings that reference them, not its consumer plans. Effective June 17, 2025. | anthropic.com/legal/commercial-terms |
| OpenAI — API | Data sent to the API is not used to train or improve OpenAI's models unless you opt in, as of March 1, 2023. Abuse-monitoring logs are kept for up to 30 days by default. | developers.openai.com/api/docs/guides/your-data |
| OpenAI — ChatGPT business plans | Read during onboarding against OpenAI's published terms for your plan, and recorded the same way. | openai.com/enterprise-privacy |
| Microsoft — Copilot | "Prompts, responses, and data accessed through Microsoft Graph aren't used to train foundation LLMs." Copilot only surfaces data a user already has permission to view. | learn.microsoft.com/en-us/microsoft-365/copilot/microsoft-365-copilot-privacy |
| Google — Gemini in Google Workspace | Your content "is not human reviewed or otherwise used for Generative AI model training outside your domain without permission." | knowledge.workspace.google.com/admin/gemini/generative-ai-in-google-workspace-privacy-hub |
| AI inside your other software | Each vendor's own terms — your CRM, phone system or accounting software. Recorded the same way during onboarding. | Each vendor's data or AI terms page |
Consumer plans and personal accounts
Consumer plans run on different terms from business plans — Anthropic's Commercial Terms, for one, state that they do not cover its consumer offerings. We do not do business work in consumer or personal accounts, and we do not rely on a consumer plan's settings to protect business data.
Our own tools
We use AI tools of our own to write code and documentation. Your business data does not go into them. Anything we build for you is built and tested in your workspace, or against made-up records.
A5
Records, security and incidents
What we keep, how it is protected, and what happens if something fails
Records you can inspect
Records describe what we built and changed. They live in a location your business owns, and they do not contain your customers' data.
| Record | What it holds |
|---|---|
| Access record | Every Tez sign-in and every connection we created: system, role or scope, date added, date reviewed, date removed |
| Settings record | Each tool's plan, data terms as read on a given date, and the controls set (A4) |
| Workflow register | Every live workflow, with its approved data sheet (A3), its owner on your side and its documentation |
| Change log | Every change to a live workflow or connection: what changed, why, when, who approved it |
| Training record | Who was trained, on which tools and processes, and when |
Changes to something already running
Every change to a live workflow is described, approved by you, tested, logged and reversible — the previous version is kept. If a vendor update breaks a workflow, or a workflow starts doing something it should not, we may pause it at once to stop harm, and tell you the same day. We do not change what a workflow does without your approval.
Security controls
| Control | Evidence you can ask for |
|---|---|
| Written information security program, modelled on Massachusetts 201 CMR 17.00 | The program document |
| Multi-factor authentication on every account we use to reach your systems | Access record |
| Access limited to named individuals, reviewed with you quarterly | Access record and review log |
| Tez devices: full-disk encryption, screen lock, current patches, endpoint protection | Configuration record |
| Your data is not stored on Tez devices or in our cloud storage; where a task needs a file locally, it is deleted when the task ends | Written procedure |
| Background check for anyone with access, on your request | Written confirmation |
| Cyber liability insurance, where your contract requires it | Certificate of insurance |
| Written incident response plan, reviewed each year | The plan and its last review |
If something goes wrong
An incident includes a workflow sending or showing data to the wrong person, a connection reaching more than its sheet allows, a suspected compromise of a Tez sign-in, and a vendor incident we learn of that affects your workspace.
- 01 · Contain — Pause the workflow, revoke the affected credential or connection, and stop the exposure.
- 02 · Notify you within 72 hours at the latest — Which systems and data, what window, what we have done. Sooner where your industry's page sets a shorter time. Updates follow as we investigate.
- 03 · Preserve evidence — Logs, the change log and the vendor's audit records are kept intact for your investigation.
- 04 · Support your notice, never pre-empt it — Whether customers or regulators are told is your decision. We never contact your customers about it. A vendor's own incident notice comes to you under your contract with that vendor.
When the engagement ends
| Step | What happens |
|---|---|
| Access removed | Every Tez user and role removed from every system, checked against the access record |
| Credentials ended | Every key, app authorisation and service account we created is revoked, or rotated and handed to you |
| Nothing in our name | Anything that ended up in a Tez name is transferred to you first — by design there should be nothing |
| Handover pack | The workflow register, data sheets, settings record, change log and plain-English run notes, so your team or the next provider can keep it running |
| Written confirmation | Within 30 days of the end of the engagement |
Everything we build is yours — documented and portable. If we part ways, it keeps working and your team knows how it runs.
A6
Limits
What this document is not
- 01 · Not legal advice — Your counsel or compliance officer decides how your industry's rules apply to your business. This document tells them what we do so they can.
- 02 · Not a SOC 2 report — We do not hold a SOC 2 attestation. If you send a security questionnaire, we complete it and provide the policies and evidence behind each control instead.
- 03 · Not the vendor — We do not run the AI vendors' systems or set their terms. Their security, retention, outages and incidents are governed by your contract with them. We are not a reseller, partner or certified provider of any AI vendor.
- 04 · Your obligations stay yours — Using AI tools does not move your duties to us: licensing, supervision, record keeping, privacy notices and your staff's use of AI remain your business's responsibility. We build to them, as your industry's page sets out.
- 05 · Not a promise about AI output — AI tools can be wrong, and confidently so. That is why anything that needs a judgement has a person in the loop, and why no workflow makes a decision your business would otherwise make.
- 06 · Not permanent — Current as of October 2026. Vendor terms and the rules on AI change often. We review this document at least once a year, and whenever a vendor term or rule it relies on changes.
A7
Construction
What your industry's rules mean for your AI tools
In construction, AI tools are mostly asked to write: proposals, follow-ups, bid responses, website copy and replies to homeowners. Each of those is your advertising or your correspondence, and the rules on what it must say — your licence number, honest claims, financing disclosures, cancellation rights — apply whether a person or a tool drafted it. A few rules also govern who you may contact and when. These are the ones that bear on the work, and what we do about each.
| Rule | What it means for AI tools | How we handle it |
|---|---|---|
| State contractor licensing and advertising laws — California, Florida, Massachusetts, New Jersey and others [1][2][3][4] | Several states want your licence or registration number on every advertisement, electronic messages included, and New Jersey on correspondence with consumers too. A drafted email or post that leaves it off is your ad without it. | Your licensed name and number are set in the tools' brand-voice instructions and in every template we build, for each state you work in. |
| FTC Act section 5; FTC rule on reviews and testimonials, 16 CFR Part 465 [5][6] | Claims must be true and backed up, whoever drafts them. AI-written reviews or testimonials presented as real customers' are banned. | Approved claims are a fixed list in the tools' instructions. We do not build anything that writes reviews or testimonials. |
| Regulation Z, 12 CFR 1026.24 [7] | Mentioning a monthly payment, rate or down payment in an ad triggers required disclosures — for contractors as well as lenders. AI tools add "as low as $X a month" freely. | Financing terms are left out of drafts unless your approved, complete disclosure is attached as a fixed block. |
| FTC Cooling-Off Rule, 16 CFR Part 429 [8] | Sales made in the buyer's home carry a three-day cancellation right and a required notice. A tool that drafts or edits proposals and contracts can drop or reword it. | Contract and cancellation language stays in your locked templates. AI tools may draft the scope description around it, never the notice itself. |
| Public procurement contact rules [9] | Many public bodies bar contact with their staff while a solicitation is open. An automated follow-up can break that without anyone noticing. | Workflows that write to contacts check an exclusion list you control, and public-sector contacts on open bids are on it by default. |
| TCPA, Do Not Call and CAN-SPAM [10][11][12] | A text or email a workflow sends is a marketing message under the same rules as one a person sends. CAN-SPAM has no exception for business-to-business email. | Workflows draft; a person sends, from your channels. A workflow that sends on its own is built only on written request, with consent and opt-out checks in it. |
| State breach notification laws — Florida 501.171, Texas 521.053 [13][14] | A vendor that holds data for you must tell you within 10 days in Florida and immediately in Texas. AI tools and connections are part of what a breach can expose. | We tell you as soon as possible and no later than 72 hours — at once where Texas law applies. |
| State privacy laws [15] | Larger businesses may fall under a state privacy law, with service-provider terms and access and deletion rights. | Service-provider terms in our agreement; help with requests in the tools we set up, within your deadline. |
In practice
- A workflow may draft a follow-up on a stalled proposal from the scope and the customer's last email. Your licence number and approved claims go in automatically; no financing figure appears unless the full disclosure goes with it.
- An assistant may turn site notes into a first-draft scope of work. The cancellation notice and payment terms come from your locked contract template, not from the assistant.
- An automated follow-up on bids skips any public-sector contact whose solicitation is still open.
- Plans, permits and subcontractor documents connected to an AI tool are scoped to the project team that already has access to them.
A8
Sources
Where these rules come from
1. California CSLB, Online Home Improvement Marketplace Companies (B&P Code 7030.5; 16 CCR 861) — https://cslb.ca.gov/Resources/IndustryBulletins/Online_Marketplace_Fast_Facts.pdf 2. Florida Statutes 489.119(5) — https://www.flsenate.gov/Laws/Statutes/2025/489.119 3. Massachusetts General Laws c. 142A, section 13 — https://malegislature.gov/Laws/GeneralLaws/PartI/TitleXX/Chapter142A/Section13 4. New Jersey Division of Consumer Affairs, Home Improvement Contractors FAQ (N.J.S.A. 56:8-136 et seq.) — https://www.njconsumeraffairs.gov/hic/Pages/FAQ.aspx 5. FTC Act section 5, 15 U.S.C. 45 — https://www.law.cornell.edu/uscode/text/15/45 6. FTC Rule on the Use of Consumer Reviews and Testimonials, 16 CFR Part 465 — https://www.ecfr.gov/current/title-16/chapter-I/subchapter-D/part-465 7. Regulation Z, 12 CFR 1026.24, Advertising — https://www.ecfr.gov/current/title-12/chapter-X/part-1026/subpart-C/section-1026.24 8. FTC Cooling-Off Rule, 16 CFR Part 429 — https://www.ecfr.gov/current/title-16/chapter-I/subchapter-D/part-429 9. Miami-Dade County, Cone of Silence (County Code 2-11.1(t)) — an example of a no-contact rule — https://www.miamidade.gov/global/strategic-procurement/procedures-cone-of-silence.page
- 01Telephone Consumer Protection Act, 47 U.S.C. 227 — https://www.law.cornell.edu/uscode/text/47/227
- 02FCC rules, 47 CFR 64.1200 — https://www.ecfr.gov/current/title-47/chapter-I/subchapter-B/part-64/subpart-L/section-64.1200
- 03FTC, CAN-SPAM Act: A Compliance Guide for Business — https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business
- 04Florida Statutes 501.171 — https://www.flsenate.gov/Laws/Statutes/2025/501.171
- 05Texas Business and Commerce Code 521.053 — https://statutes.capitol.texas.gov/Docs/BC/htm/BC.521.htm
- 06California Consumer Privacy Act; California Privacy Protection Agency, threshold adjustment — https://cppa.ca.gov/regulations/cpi_adjustment.html