TCPA Rules for Texting Yelp Leads (What Contractors Should Know)

What Is the TCPA and Why Does It Matter Here?

The TCPA is a federal law that regulates automated calls and texts to cell phones. It was written in 1991 for robocalls, but courts and regulators have applied it broadly to text messages too, including texts sent from software that dials or sends in bulk.

For a contractor, the practical version is this: sending a text to someone's personal cell number, especially through any kind of automated or bulk tool, can trigger TCPA obligations even if your intent is completely reasonable, like following up on a quote request. The law does not care that the lead came from Yelp. It cares whether the person on the other end of that phone number agreed to receive texts from you specifically.

This is general background information, not legal advice. TCPA cases turn on specific facts, and enforcement and case law shift over time, so nothing here should be treated as a legal opinion about your business.

Why a Yelp Lead's Phone Number Isn't Automatic Consent

When a consumer submits a Request-a-Quote on Yelp, they are agreeing to Yelp's terms and typically expecting a reply inside Yelp, whether that's a message in the Yelp app, an email notification, or a call. They are not necessarily agreeing to receive a text message from a business they've never contacted directly, sent to their personal cell number, outside of Yelp.

That distinction matters. Consent under TCPA is generally supposed to be specific to the calling or texting party, not implied because a phone number appeared somewhere in a form. A phone number sitting in a Yelp lead is contact information, not a green light to text.

This is exactly why pulling a number out of a Yelp lead and dropping it into a separate SMS tool is the pattern to avoid. It feels efficient, but it also strips out the context Yelp provided and replaces it with a new, unconsented channel.

What Does TCPA-Safe Contact Actually Look Like?

In broad, general terms, the patterns that are typically viewed as lower-risk share one thing: the consumer chose the channel, or clearly agreed to it, before you used it.

Replying inside Yelp's own Request-a-Quote thread is the clearest example. The consumer opened that thread, on that platform, expecting a response there. You are not reaching them anywhere new.

A second pattern is waiting for the consumer to explicitly say, in their own words, something like "text me at this number" before you start texting them directly. That kind of express, in-context statement is generally treated very differently from a number that simply exists in a form field.

What is not a safe pattern: buying or using a bulk texting tool, exporting phone numbers from leads, and sending texts to consumers who never asked to be texted outside Yelp. That is the exact fact pattern TCPA claims tend to target.

Where Does Yelp Lead AI Fit Into This?

This is one of the reasons Yelp Lead AI is built the way it is. It reads incoming Yelp Request-a-Quote leads, decides whether a lead is worth a paid response, and drafts a reply. On the Instant plan, that reply gets posted back into the Yelp thread itself, not sent as a separate text to the consumer's personal number.

If a consumer's phone number is included in a lead, Yelp Lead AI surfaces it to the business owner so a human can decide whether and how to call or follow up. It does not auto-text or auto-call that number on its own. The reply itself is also written to actually answer the consumer's question, not to redirect them to "just call us," which keeps the conversation useful on its own terms rather than functioning as a workaround to get them on the phone.

That's a design choice, not a guarantee about your specific legal exposure. If your business has a different follow-up process, or you're combining Yelp leads with other outreach, that's worth its own look.

Common Mistakes Contractors Make With Yelp Lead Phone Numbers

The most common mistake is treating a phone number on a Yelp lead the same as a phone number a customer texted you directly. They are not the same thing from a consent standpoint.

A second common mistake is bulk-importing lead numbers into a CRM or texting tool that auto-sends follow-ups. Even a single automated "just checking in" text to a number pulled from a Yelp lead, with no prior consent, is the kind of pattern that draws TCPA scrutiny.

A third mistake is assuming a consumer's silence, or the fact that they submitted a form, counts as opt-in. Generally, TCPA consent is supposed to be clear and specific, not inferred from the mere existence of a lead.

When in doubt, keep the reply inside Yelp, answer the actual question the consumer asked, and only move to direct texting after they've clearly asked for it themselves.