Legal
Messaging & Consent
This product texts your customers automatically. That is regulated conduct, the exposure sits mostly with you rather than with us, and pretending otherwise would not do you any favors. Here is precisely which parts are ours.
Last updated: August 2026 · Counsel review pending. See the note at the end of this page.
The short version
- This system sends texts to your customers for you. Texting is regulated by law.
- The rules mostly land on you, because your name is on the message and your number sends it.
- You need your customer's okay before you text them. Keep a record of it.
- We register your business with the phone carriers, write STOP into every message, and set quiet hours so nothing sends late at night.
- A sequence stops the moment somebody replies or books.
- We are not a health company. There is no PHI here and HIPAA does not apply to us.
This box is a plain summary. The detail is below, and none of it is legal advice.
We do not handle protected health information
Worth saying plainly. YaContesta.pro is for trade contractors. It is not a healthcare product, we are not a business associate, there is no Business Associate Agreement, and HIPAA does not apply to what we do. If your business does handle health information, this is the wrong product and we will say so on the call.
Aday Interactive, Inc. is also not a licensed contractor. We build and support the software. We do not perform, supervise, inspect, or warrant any trade work, and we do not vet or endorse the companies who use this system.
What the TCPA is
- A federal law, the Telephone Consumer Protection Act, plus FCC rules and state analogues, governing automated calls and texts to consumers.
- A consent regime. For marketing messages it generally requires prior express written consent; for transactional messages about a job the customer asked for, the standard is lower but not absent.
- Enforced privately. Statutory damages run per message, and it is one of the most actively litigated consumer statutes in the country.
- Also a Florida question. The Florida Telephone Solicitation Act sits on top of the federal rules and has its own consent and calling-hours requirements.
What it is not
- Something a piece of software can hold on your behalf. Consent attaches to your business and the number the message comes from.
- Satisfied by a checkbox nobody can produce later. What matters in a dispute is the record of who agreed, to what, and when.
- A certification. There is no TCPA seal, for us or for anyone, and we do not claim one.
- Legal advice, which this page is not. We are not attorneys, and this page is pending review by counsel.
Who is responsible for what
Three parties, and the split matters because only one of them can actually hold the consent.
The platform
HighLevel (GoHighLevel)
Provides the messaging infrastructure, the carrier connections, A2P brand and campaign registration plumbing, opt-out keyword handling, and the consent fields on the record.
Us
Aday Interactive, Inc.
Registers your brand and campaign, writes the sequences so they carry identification and opt-out language, configures quiet hours and stop-on-reply, and trains your staff on what may be sent.
Your company
The sender of record
Owns the customer relationship and the consent behind it. Your brand is on the message, your number sends it, and the obligation to have permission is yours.
What we configure, on every account
A2P 10DLC registration before a single message sends
Carriers require a registered brand and campaign for business texting. Unregistered traffic is filtered or blocked outright, which reads like a broken system rather than a compliance failure. We register you as part of setup.
Opt-out that actually works
STOP, CANCEL, END, UNSUBSCRIBE and the Spanish equivalents suppress the contact across every sequence, not just the one they replied to. We test this before go-live rather than assuming the platform default is enough.
Quiet hours
Nothing automated sends between 8 PM and 8 AM local time unless you specifically ask for it, and we will ask you why before we do. Federal and Florida rules both constrain calling hours.
Stop on reply, stop on booking
A follow-up sequence ends the moment the customer answers or schedules. The most common complaint that turns into a claim is the sequence that kept running after the person responded.
Business identification in the first message
The first outbound message names your company, because a text from an unidentified number is both a compliance problem and a conversion problem.
Consent captured where the lead is captured
Web forms carry explicit language about what texting the customer is agreeing to, and the answer is stored on the record with a timestamp rather than assumed.
What stays yours
None of this is us being cagey. Consent belongs to whoever has the customer relationship, and that is you.
- Having permission to contact the people you upload. If you import an old list, that list is yours and so is its consent history, or its absence.
- Not repurposing a service relationship into a marketing one without separate consent. Someone who called about a broken water heater has not agreed to a monthly promotion.
- Honoring an opt-out everywhere, including the ones that arrive by phone, by email, or in person rather than by replying STOP.
- Your own retention of consent records, which is what you would need to produce if a claim is ever made.
- Telling us if you are calling or texting outside Florida, because state rules vary and some are stricter than the federal baseline.
- Any recording of calls. Florida is a two-party consent state, and if you record, the disclosure obligation is yours.
- Whatever your own industry or licensing body requires of your advertising, which is between you and that body.
What we cannot yet confirm
Open questions, stated as open rather than papered over.
AI voice agent disclosure
FCC rulemaking on AI-generated voice in outbound calling has moved quickly and is still moving. What is settled is that an artificial voice placing calls to consumers is regulated conduct; what is less settled is the exact disclosure wording required in every context.
Our position. We scope the voice agent to inbound calls and to scheduling and logistics, and we configure it to identify itself as an automated assistant on the first turn. We would rather over-disclose than argue about it later.
Carrier filtering is not a compliance verdict
Carriers filter traffic on their own heuristics. Messages get through that should not, and messages get blocked that are perfectly lawful. Delivery is not evidence of consent.
Our position. We do not treat a good delivery rate as proof that a campaign is compliant, and we will tell you when a sequence looks lawful but risky.
What the platform publishes about consent storage
HighLevel provides consent fields and opt-out handling, but does not publish a guaranteed export format or retention period for that consent history, the same gap that exists for the rest of the data.
Our position. We export consent state along with contacts on request, and our commitment is to act promptly and in good faith rather than to a service level we do not control.
Not legal advice
This page describes how we configure the system and how we understand the split of obligations. It is not a legal determination that your messaging program complies with the TCPA, the Florida Telephone Solicitation Act, or any other law, and it is not legal advice. We are not attorneys. This page is pending review by qualified counsel.