LexLint.ioBeta

Know the law your code answers to.

Activities / What code does

Sends automated outreach

automated_outreach

Your app contacts people through automated calls, texts, or messages that a person did not individually compose and send.

  • scope code
  • in the registry since 1.0
  • 1,192 laws in 236 jurisdictions name it

What triggers it

The lint's definition. It sends people messages by email, text, call or direct message that the software initiates, rather than a person sending each one. Requests under a records law are statutory_requests.

This covers an automated phone campaign, a bulk text reminder service, and a voice call generated by a speech model rather than recorded by a person.

What does not

A single email a staff member writes and sends by hand does not count, even if a template supplied the boilerplate.

Often confused with Files records requests.

The law it brings into scope

The kinds of law that name this activity in the LexLint law library, with the number of laws and jurisdictions in each, as of . The examples are chosen by rule, laws in force first and the widest jurisdiction first; each section's page lists every law.

Area of lawLawsJurisdictions
Privacy law

Have a legal basis for personal data, honor people's rights over it, and report a breach.

 930 233
Communications law

Get consent before marketing, calling, recording or storing data on a device, and honor an opt-out.

 143 49
Cybersecurity law

Build software securely, handle reported flaws, and report incidents on a deadline.

 91 67
Product and AI liability law

Answer in damages when defective software or an AI system causes harm.

 23 22
AI law

Tell people when they are dealing with an AI system or its output, and control the uses the law calls high-risk.

 7 7
Scraping law

Stay within computer-access law, a site's terms, and the copyright in what is copied.

 5 5

Counterparties that usually come with it

  • an email delivery service
  • a carrier gateway for text messages and calls

A component that cannot run as documented without one of these names it in its ACTIVITIES.md under talks_to, with required: true. That party's jurisdiction then joins the run of every product that uses the component, and the finding says why it is there. A default the deployer can change is asked about, never added. Talking to a party never makes a product that party.

In a declaration

A library or framework that makes this possible enables it; an application whose shipped code does it performs it.

For a library

activities: - id: automated_outreach mentioned: enables enabled: requires_configuration where: [<the module that carries it>] note: <one sentence>

For an application

activities: - id: automated_outreach mentioned: performs enabled: by_default where: [<the module that carries it>] note: <one sentence: what it does, and the kind of law it attracts>

History

In the registry since version 1.0, .

In the glossary: Sends automated outreach.

The activity registry is LexLint's open list; this page's text is licensed under Creative Commons Attribution 4.0.