Early-bird bonus: 30% extra credits.

AI calling laws for personal assistants in 2027

AI calling laws distinguish service calls from marketing, with separate consent rules for phone lines and automated speech. Your authorization does not replace required recipient consent, privacy safeguards, or account-access checks.

View .md

An AI assistant can call a business on a person's behalf to request records, discuss an existing account, or arrange an appointment. Whether the call is lawful depends on the rules governing its purpose, the recipient's location, and the telephone service involved. A legitimate reason for contacting the business does not, by itself, satisfy every requirement for an artificial-voice call.

This guide covers one-off, nonmarketing calls to published business service numbers for records, claims, account questions, scheduling, and status updates. It explains the main calling rules, then separates them from disclosure, recording, privacy, and access to protected information.

Prepared for 2027 using law, official guidance, and adopted future changes checked on 21 November 2026. Later developments may change the position. This is general information, not legal advice.

Authorization and the purpose of the call

Your instruction authorizes the assistant to act for you within the task you set. It does not establish the recipient's consent where the law requires consent to receive an artificial-voice call. Those permissions concern different people: you choose your representative; the recipient has any protections that apply to the incoming call. (TCPA §227(b))

Purpose matters because many calling restrictions address direct marketing, meaning communications that promote products, services, or similar offers. A request for an existing claim's status ordinarily lacks that purpose. Adding a sales pitch can change the classification, even if most of the conversation concerns service. (ICO service communications; Australian Act §5)

The following starting points apply to the nonpromotional task described here. The country sections explain their conditions.

Country or regionMain distinctionPractical consequence
United StatesArtificial-voice rules protect specified phone-line categories.A business mobile or toll-free number differs from an ordinary uncharged business landline.
United KingdomPECR regulation 19 concerns automated direct marketing.Classify the purpose before considering the unresolved live-AI technology question.
European UnionThe EU automated-call consent rule concerns direct marketing.Check national implementation, privacy rules, and the separate AI-disclosure duty.
CanadaADAD rules include non-solicitation calls.Calling conditions and restrictions can apply even to a useful service request.
AustraliaTelemarketing law examines the call's purpose.A nonpromotional service request ordinarily falls outside that test; other duties remain.

United States: artificial voices and the destination line

The federal Telephone Consumer Protection Act, or TCPA, regulates artificial-voice calls independently of its autodialer rules. The FCC has ruled that AI-generated human voices fall within "artificial voice." Selecting one number, dialing manually, or generating each reply live does not remove that trigger. (FCC AI voice ruling, paragraphs 5–9)

For a nonmarketing call, the next question is the type of line receiving it:

US destinationFederal starting point for an AI service call
Ordinary business landline, excluding toll-free and other charged servicesThis category alone falls outside the main artificial-voice recipient-consent prohibitions. State and other federal rules still apply.
Mobile, including a business mobilePrior express consent generally applies unless a specific exemption covers the call.
Toll-free or another service charging the recipient for incoming callsPrior express consent generally applies, even when the call contains no marketing.
Residential line, including one used for a home businessPrior express consent or a valid residential exemption is needed.
Emergency or protected hospital patient/guest-room lineSpecific statutory protections apply; these are not ordinary service destinations.

These distinctions follow the TCPA's separate protections for wireless, charged, residential, and other listed lines. Toll-free numbers deserve particular attention: the call is free to you, but the business can pay to receive it. The FCC includes charges covered by bundles of minutes. (TCPA §227(b)(1); FCC toll-free ruling, paragraphs 14–16)

On that statutory reading, a claim-status request to an ordinary uncharged business landline can fall outside the federal recipient-consent prohibitions. The same request to a business mobile or toll-free support number generally needs prior express consent, unless an applicable exemption provides otherwise.

Prior express consent does not universally require a signed form. For covered artificial-voice marketing, the rule generally requires prior express written consent: a signed agreement meeting specified conditions. Nonmarketing consent can take other forms, but its scope must cover the communication. FCC precedent recognizes consent arising from knowingly providing a number for related business communications; it does not settle whether every public support listing authorizes a customer's AI assistant. (47 CFR §64.1200(a), (f)(9); FCC consent guidance, paragraphs 9–10)

The residential exemptions for noncommercial calls and commercial calls without advertising or telemarketing each allow no more than three calls in 30 days, with automated opt-out and internal do-not-call duties. This allowance does not extend to mobiles or toll-free numbers. (Residential exemptions and opt-out conditions)

State law can reach further. Minnesota restricts covered synthesized-voice messages regardless of content, but expressly excepts messages to subscribers with whom the caller has a current business or personal relationship. Whether that relationship applies to the assistant's call requires attention to who is calling and for whom. It is not a general exemption for all business recipients. (Minnesota §§325E.26 and 325E.27)

For 2027 planning, FCC 26-67 adopts revised consent-withdrawal rules scheduled for 25 November 2026. They permit category-specific opt-outs from informational calls, subject to the rule's conditions. That effective date supersedes the earlier 31 January 2027 deadline. These changes affect withdrawal and later communications; they do not supply permission for an assistant's first call. (Final rule, sections I.A and I.E)

United Kingdom: service calls under PECR

Regulation 19 of the UK's Privacy and Electronic Communications Regulations, or PECR, restricts direct-marketing communications comprising recorded matter sent through an automated calling or communication system. Its system definition refers to stored instructions enabling calls to more than one destination and transmission of sounds that are not live speech. (PECR regulation 19)

A customer's assistant asking a utility about an existing bill ordinarily has no direct-marketing purpose. On that reading, regulation 19's marketing consent requirement does not govern the service request. ICO guidance supports the distinction between administrative service communications and promotion. The provider's privacy and recording duties still require separate consideration. (ICO service-message guidance)

The position for fully real-time conversational AI remains unresolved in the official material reviewed. The ICO has said that a recorded synthetic greeting followed by a human handler falls within regulation 19 when used for marketing. That example does not decide every element for dynamically generated speech. Nor does placing only one call settle a definition based on the system's capabilities. (ICO innovation guidance)

A separate delivery change is scheduled for 15 July 2027: updated Ofcom caller-ID guidance can affect how overseas calls presenting UK mobile numbers appear. This concerns caller-ID handling, rather than consent to receive an AI call. (Ofcom final statement, paragraphs 4.101–4.102)

European Union: national rules and AI transparency

Article 13 of the ePrivacy Directive requires prior consent for automated calling without human intervention for direct marketing. A genuine nonpromotional request for a booking or case update does not ordinarily meet that purpose. This conclusion follows the provision's scope; national communications and other laws still govern the call. (ePrivacy Directive, article 13)

National marketing rules also differ in how they protect business recipients:

CountryRelevant distinction
GermanyUWG §7 requires prior express consent for advertising through an automatic calling machine, including business addressees. It separately prohibits unreasonable commercial harassment. (UWG §7)
FranceCNIL's automated-call guidance distinguishes individuals' prior consent from notice and a simple, free objection for professional recipients, where the offer relates to their profession. (CNIL guidance)
SwedenMarketing Act §19 addresses a trader's use of automated individual communication systems to market to natural persons. This differs from a general rule for every corporate service line. (Marketing Act §§19–21)

These provisions do not turn a service request into advertising merely because AI speaks. They explain why marketing exceptions cannot be transferred unchanged between countries.

The AI Act's disclosure duty is separate from calling consent. Article 50(1), applicable since 2 August 2026, requires providers to make people aware of direct AI interaction unless that is obvious in context. The notice belongs at the first interaction and covers business staff as well as consumers. An ordinary human-sounding assistant should identify itself when it first speaks with a person. (Article 50; Commission transparency guidance)

The limited transition for machine-readable marking of certain older systems' synthetic outputs ends on 2 December 2026, before the coverage year begins. It does not postpone the interaction notice. Later high-risk implementation dates apply according to system classification; they do not create a new consent rule for every assistant call. (Regulation (EU) 2026/1744)

The EU and wider EEA also need separate treatment. AI Act incorporation into the EEA Agreement remained under review for Norway, Iceland, and Liechtenstein. An EU connection can nevertheless bring a non-EU provider within the Act's scope. (EFTA status; AI Act article 2)

Canada: non-solicitation calls under the ADAD rules

Canada's rules for automatic dialing-announcing devices, or ADADs, include equipment capable of storing or producing numbers and conveying prerecorded or synthesized voice messages. Part IV regulates non-solicitation calls as well as sales calls, so removing promotion does not end the calling analysis. (CRTC definitions and part IV)

Covered non-solicitation calls generally must stay within 9am–9:30pm on weekdays and 10am–6pm on weekends, in the recipient's time zone. Provincial activity-specific hours can apply. Conditions also cover opening identification and purpose, contact details, caller ID, repeat identification on longer messages, and disconnection after hangup. The full rule contains further requirements. (CRTC part IV.4)

Part IV.4 restricts covered calls to emergency lines and healthcare facilities. Its specified public-service exception does not automatically cover a patient's assistant booking an appointment. The business-to-business exemption from the National Do Not Call List likewise does not remove the separate ADAD rules. (CRTC part IV.4(a), (i); CRTC business guidance)

Canada is reviewing how the framework applies to AI and strictly personal assistant tasks. CRTC 2026-132 expressly raises those questions, including healthcare and restaurant bookings. We did not locate a final ruling resolving the review. The notice asks about possible changes; it does not establish a personal-AI exemption for 2027. (CRTC review)

Australia: a purpose-based telemarketing framework

Australia's Do Not Call Register Act includes recorded and synthetic voices, while its telemarketing definition examines promotional and other listed purposes. A purely nonpromotional request about an existing account or appointment ordinarily falls outside that definition. This is an application of the statutory purpose test, rather than a regulator's clearance of every personal-assistant design. (Act §§4–5)

Ordinary business voice numbers cannot join the Register, although mainly private mixed-use numbers can qualify. That distinction does not eliminate all rules: the telemarketing and research call standard can apply to unregistered numbers. Where telemarketing consent is needed, publication of a number alone is insufficient. (ACMA questions; ACMA standard guidance; Act schedule 2)

For 2027, the 2017 Industry Standard and Do Not Call Register Regulations are scheduled to expire on 1 April 2027. Check for a replacement or extension before relying on their detailed conditions after that date. The scheduled expiry concerns those instruments, not the Act. The Telecommunications Act also requires ACMA to keep a telemarketing industry standard in force, so the date does not promise a gap without calling rules. (Standard sunset; Regulations sunset; Telecommunications Act §125A(4))

Disclosure, data processing, and protected records

Permission to place a call does not decide everything that happens after answer. The assistant must also meet applicable identification duties, handle personal data lawfully, and establish authority for protected account information.

US federal rules require artificial-voice messages to identify the responsible caller and provide a callback number. The FCC's separate AI-specific disclosure requirements remained proposals in the material reviewed. Disclosing AI is sensible practice, and required in some jurisdictions, but an opening announcement cannot cure missing prior consent to the call. (Identification requirements; FCC AI-disclosure proposal)

Under GDPR, consent is one lawful basis for personal-data processing, not the only one. Necessary performance of the user's contract may cover that user's information. Processing a vendor employee's voice or details needs its own basis; the employee is not automatically covered by your contract. Legitimate interests requires necessity and a balancing assessment, and cannot replace communications consent required by another rule. Health data needs an additional article 9 condition. The household exemption can protect purely personal use without exempting the commercial provider. (GDPR articles 2, 6 and 9, recital 18; EDPB guidance)

Recording requires a separate check. Germany prohibits unauthorized recording of nonpublic spoken words. Canada's privacy commissioner requires covered organizations recording customer calls to explain the recording and its purposes and obtain consent. Transcription, streaming, storage, and later reuse also need review under the rules applicable to the actual service. (German Criminal Code §201; Canadian recording guidance)

Finally, authority to ask is different from authority to receive. UK subject-access guidance requires evidence that a representative may act and receive information. Australian access guidance likewise requires identity and authorized-agent checks. A provider can need these checks before releasing records, even where the call itself is lawful. (ICO representative guidance; OAIC access guidance)

Practical checks before the call

A reliable decision follows the call's facts, rather than treating "personal assistant" or "business number" as a legal category.

Cross-border routing deserves attention. The TCPA expressly reaches calls from outside the US to recipients inside it. A company's registration or the number's country code alone does not establish where the conversation takes place. (TCPA §227(b)(1))

Hail requires recipient_consent: true for outbound calls, including informational calls. Missing or false values receive a 422 rejection. This records your attestation; Hail does not verify consent for you. Selecting an informational message type does not bypass the field. (Hail terms, section 3; MCP documentation)

The API wording addresses the lawful consent required and your responsibility for a lawful basis. The connected MCP tool currently asks for confirmation that the recipient agreed to be contacted. The legal analysis and that requested statement remain separate: a public listing does not automatically establish what the tool asks you to confirm. Only make an attestation you can truthfully support.

That does not mean every jurisdiction demands a separate signed AI-specific form. The necessary agreement's form and scope follow the applicable rules. It does mean Hail's confirmation must not be treated as an exemption switch.

Hail enables AI disclosure by default. Disabling audio recording does not turn off transcription or all other data processing. Marketing also requires a consent_source; an optional consent date records timing rather than creating permission. (Call recording documentation)

Our AI phone agent guide explains practical assistant tasks. The voice overview covers Hail's calling features.

AI calling laws FAQ

Does a public business number automatically authorize an AI call?

No. A public listing may be relevant evidence, but does not settle the applicable calling rules. A US toll-free support number, for example, still requires the charged-service analysis. (FCC toll-free ruling)

No. US rules distinguish prior express consent from prior express written consent, generally required for covered artificial-voice marketing. Other countries use different purpose and technology tests. (47 CFR §64.1200)

No. Where consent must precede the AI call, obtain it before dialing. Disclosure at answer performs a different function. (FCC AI voice ruling)

Can a personal assistant call a Canadian clinic for an appointment?

Sometimes, but a covered non-solicitation ADAD call faces a healthcare-facility restriction. The CRTC review does not provide a personal-assistant exemption. Establish the applicable classification and rules before calling. (CRTC part IV.4)

Does switching off audio recording remove privacy duties?

No. Speech processing and transcripts can still contain personal data. Check what the service processes, retains, shares, and reuses. (GDPR articles 4–6)

Make your first call.

Connect your assistant and start calling.