Map the campaign before asking whether consent is required
Identify who is selling, who is calling, whether the contact is marketing or informational, and whether the destination is a mobile, residential or business number. Record whether the system uses live manual calls, an automatic telephone dialling system within the applicable legal definition, artificial or prerecorded voice, or text messages.
These distinctions affect the FCC rules under the TCPA framework. A platform’s marketing label is not a legal classification. Ask for a technically accurate description and obtain US-law advice on the actual functionality. [1]
Also identify the states being targeted. Federal analysis is not a substitute for potentially applicable state calling, registration, privacy, recording or consumer-protection requirements. Do not assume that manual calling removes every other obligation.
The FCC and FTC frameworks must be checked separately
FCC rules under 47 CFR § 64.1200 address different categories of calls and texts, permissions, identification and do-not-call or revocation requirements. The FTC’s Telemarketing Sales Rule addresses its own covered activities, prohibited practices and seller or telemarketer obligations. Compliance with one framework does not automatically satisfy the other. [1] [2]
Business-to-business calling is not a universal safe harbour. The FTC’s 2024 changes extended important protections against material misrepresentations in B2B telemarketing. Determine which provisions and exemptions actually apply rather than relying on the recipient’s job title. [3]
A Pakistani service provider should ask the client to identify the campaign’s legal basis and responsible US adviser. A client assurance is useful evidence of instruction, not a substitute for investigating obvious defects.
Consent and suppression must be demonstrable
Where consent is required, preserve the record supporting the particular contact and technology. Review what the person was told, who was identified and the scope of permission. Do not assume that a lead broker’s “opted in” statement proves every legal requirement.
Maintain the applicable national and seller-specific do-not-call processes, record objections and prevent rejected contacts from being reintroduced through later list imports. The rules and exceptions depend on the campaign; an existing relationship does not create unlimited permission for every method of contact. [1] [2]
Allocate responsibility for list screening, complaint handling and revocation updates between seller and call centre. Then test whether the process works across the actual systems. A clause assigning responsibility is not enough if the technical workflow silently ignores requests.
Keep the records required by the current TSR
The current TSR recordkeeping provision requires covered records to be retained for five years. Relevant categories can include campaign and call information, scripts, consent, suppression and the parties involved. Check the regulation for the records required in the actual circumstances and how responsibility is allocated. [4]
The FTC’s implementation guidance explains the updated recordkeeping framework and the importance of written responsibility arrangements between sellers and telemarketers. Do not use older guidance referring to a shorter period without checking subsequent amendments. [5]
Retention is not permission to collect unnecessary sensitive information or keep it insecurely. Define access, storage, lawful transfers and deletion after applicable obligations and legal holds end. Evidence of compliance should be usable, not merely a large archive no one can interpret.
October 2026 status check: final, future and proposed are different
A final FCC rule published on 26 October 2026 is stated to take effect on 25 November 2026. It modifies aspects of robocall consent-revocation handling, including specified informational-call categories and designated revocation methods. On this article’s research date, 29 October 2026, those changes are not yet effective. Do not implement future permissions early. [6]
A companion publication on 26 October 2026 is a proposed rule seeking comments on further changes. A proposal is not current operating permission. Review the final text, effective dates and any later developments with US counsel before changing production systems. [7]
Maintain a rule-change register showing the requirement, legal status, effective date, affected workflow and approval to deploy. This is safer than treating the publication date of every regulatory notice as the date a new practice becomes lawful.
Worked example: a broker supplies “US business leads”
Suppose a client supplies numbers described as business contacts and asks the Pakistani team to use prerecorded sales messages. The B2B label does not answer whether the destination numbers, technology, permission and specific rules allow that campaign.
Before launch, verify the lead provenance, actual recipients, intended seller, calling method, suppression process and state-law review. Preserve the technical configuration and the permission evidence relied upon. If the client cannot answer those questions, commercial urgency is not a reliable reason to proceed.
The example is a screening exercise, not a conclusion that every prerecorded business campaign is unlawful. The point is that technology and destination details cannot be omitted from the assessment.
Put cross-border responsibility into the contract and workflow
Specify who supplies legally usable leads, verifies consent, performs screening, approves scripts, handles complaints and preserves the required records. Include audit access, prompt escalation and a lawful suspension route for unresolved risks. Do not rely solely on an indemnity that may be difficult to enforce against an overseas client.
Pakistan-side PSEB, telecom and PECA compliance remains necessary where applicable. US compliance does not authorise deceptive or otherwise prohibited conduct in Pakistan, just as Pakistani registration does not resolve US calling rules. [8]
A properly scoped review uses qualified US counsel for US-law conclusions and Pakistan counsel for local obligations, with a shared factual campaign description so the advice addresses the same operation.
Legal assistance for this issue
Legal Bridge LLP can advise on Pakistan-side contracts, PECA and regulatory exposure and help coordinate the factual brief for US counsel. This article does not represent the firm as licensed to give US legal opinions.
