A completed remote-support session does not, by itself, prove that a customer agreed to the charge. A payment approval does not establish that the sales description was accurate. For a tech support business, the strongest operating record connects the offer, customer permission, actual service and payment.
That connection is especially important when phone calls are part of selling the service. Federal telemarketing coverage changed in 2024 and 2025, and an older compliance checklist may miss both inbound tech support calls and expanded recordkeeping.
Scope and date: U.S. federal Telemarketing Sales Rule considerations checked September 21, 2026. Coverage depends on the activity, customer and applicable exemptions. Other federal and state requirements may apply, including rules affecting calls and recordings. This is general operational education, not a complete legal compliance program.
Inbound calls can fall within the rule
The FTC's final amendment published December 10, 2024 expanded coverage to inbound telemarketing calls responding to advertisements or direct-mail solicitations that offer technical support products or services. The effective date was January 9, 2025. It was initially proposed earlier in 2024, but describing it as only a proposal is now outdated. See the published final rule.
The current definition generally addresses offerings marketed to repair, maintain or improve device performance or security. It excludes services where the repair provider obtains physical possession of the device. That does not create a blanket exemption from other law or all other TSR provisions for a repair shop. The current rule's definitions and exemptions need to be assessed together.
Map the actual journey: advertisement, landing page, inbound call, diagnosis, offer and payment. “The customer called us” is not enough to conclude that a sales call is outside the TSR. Equally, do not assume that every ordinary support interaction is a covered telemarketing transaction.
Business customers do not make deceptive selling acceptable
The FTC's separate 2024 amendments extended specified prohibitions on misrepresentations and false or misleading statements to business-to-business telemarketing. This did not simply apply every consumer TSR requirement to every business call. See the FTC's explanation of the B2B changes.
For an owner, the practical review starts with claims. Does your script accurately identify the seller? Can a customer distinguish your company from the device manufacturer or software publisher? Does the salesperson describe a real observed issue, or assume a security problem before diagnosis?
Use language that matches what your technicians can establish. Do not imply an affiliation, certification or urgent threat that you cannot substantiate. Review ads and affiliate landing pages as well as your own website; customers form expectations before they reach your staff.
Separate permission to access a device from permission to charge
A remote-access approval is permission for a particular technical interaction. Your payment record should separately identify the agreed service, amount, charging account and whether any recurring arrangement was accepted.
For covered telemarketing, the TSR requires express informed consent to the charge and identified account. Additional authorization provisions depend on the payment method and transaction facts. See 16 CFR 310.3 and 310.4(a)(7). Have counsel and your provider review the implementation instead of treating a generic recorded “yes” as a universal solution.
As a practical workflow, present the service scope and price before checkout, use the approved payment experience and link the resulting transaction reference to the job. Do not ask a technician to enter a customer's online banking session or collect payment credentials into a free-text support ticket.
Update recordkeeping and vendor responsibilities
The FTC's October 2024 guidance explains that expanded call-detail record requirements began October 15, 2024, following other changes effective that May. Covered records must be retained for five years. Without a contract allocating recordkeeping responsibility, both seller and telemarketer are responsible for the required records. See the FTC's recordkeeping update.
A five-year rule is not a reason to collect every possible piece of personal information. Determine the required categories, retention start points and access controls with counsel. Build the records around the applicable requirements and avoid unnecessary duplication.
If you use a call center, request evidence that records can actually be retrieved. A vendor promise to “handle compliance” is difficult to evaluate without a clear allocation, sample export and named contact. Test retrieval using synthetic data or appropriately authorized, masked records.
Document what the service delivered
For each job, maintain a plain-language service record: reported issue, agreed scope, technician actions, relevant timestamps, result and unresolved items. Record customer communications accurately. If a problem remained unresolved, preserve that fact.
Never manufacture completion evidence to answer a dispute. An edited screenshot, invented sign-off or backdated acceptance undermines the purpose of the record. The useful question is whether the actual evidence explains the transaction fairly.
Keep remote-session access permissions separate from ongoing subscriptions. If support ends after one job, make that visible. If the customer buys an ongoing plan, connect it to the agreed recurring terms and cancellation process. Staff should be able to tell which arrangement applies without interpreting a vague note.
Prepare an accurate merchant-account packet
For tech support payment processing, organize your service catalog, customer types, acquisition channels, sales scripts, refund process and service records. Include third-party lead generation and call-center arrangements when relevant.
Describe remote repair, in-person repair, software resale and managed support distinctly. Those activities can create different review questions. Do not rename an operation solely to make it sound less risky or omit a channel because it produces a minority of sales.
Provider acceptance, reserves and contract terms vary. A clean packet helps a provider understand the business; it does not guarantee approval.
Owner checklist
- Trace every advertising and phone-sales journey.
- Obtain advice on current TSR scope and other applicable call rules.
- Review claims, affiliations and diagnosis language.
- Separate remote access, service acceptance and payment consent.
- Update required records, retention and vendor contracts.
- Link each payment to truthful service documentation.
- Test refunds, subscription cancellation and record retrieval.
Questions support owners ask
Are all inbound calls exempt?
No. The technical-support amendment specifically brings certain ad- and solicitation-driven inbound sales calls into coverage. Assess the actual call path and applicable exemptions.
Must we record every call?
Do not assume that call-detail recordkeeping and audio recording are identical requirements. Specific consent situations can require recordings; other records have different forms. Have counsel define the applicable requirements, including recording-consent law.
Can a signature eliminate disputes?
No record guarantees a dispute outcome. Accurate terms, genuine consent, clear service delivery and responsive support provide a more complete transaction history.
Discuss the actual operating model
Bring one anonymized customer journey from first ad through service completion and payment. Book with Joseph to review where your tech support operation needs clearer records, provider questions or payment integration work. Stratamize can help scope those connections while your legal advisers assess the applicable obligations.