Broker OSEARLY ACCESS
Home / Legal / Dialer and Messaging Addendum

Dialer and Messaging Addendum

Effective date: November 17, 2026 Last updated: November 17, 2026

This Dialer and Messaging Addendum (the "Addendum") forms part of the Broker OS Terms of Service (the "Agreement") between MF Automations LLC ("MFA") and Customer. It governs Customer's use of the Communications Features of Broker OS: the dialer, calling, manager listen/whisper/barge, voicemail, SMS and MMS messaging, AI voice agents, telephone numbers and related tools. Capitalised terms not defined here have the meanings in the Agreement. If this Addendum conflicts with the Agreement about the Communications Features, this Addendum controls.

1. Customer is the caller and sender

1.1 For every call, text message, voicemail and other communication made, sent or initiated through the Service under Customer's account (each a "Communication"), Customer is the caller, sender, seller, telemarketer and initiator for all purposes of applicable law, including the Telephone Consumer Protection Act (47 U.S.C. § 227) and the FCC's rules at 47 C.F.R. § 64.1200 (together, the "TCPA"), the Telemarketing Sales Rule (16 C.F.R. Part 310) (the "TSR"), the Florida Telephone Solicitation Act (Fla. Stat. § 501.059) (the "FTSA"), and other state telemarketing, mini-TCPA and do-not-call laws.

1.2 Customer decides whom to contact, when, how often, by what method, with what content, and on what basis of consent. MFA provides the technology and transmits Communications at Customer's direction. MFA does not originate Communications on its own behalf from Customer's account.

1.3 Customer is responsible for Communications made by its Users, reps, employees and contractors, and for any lead vendor, lead generator or marketing partner whose leads or consents it relies on.

2.1 Required consent. Customer will obtain, before each Communication, the consent applicable law requires, including: (a) prior express consent for non-telemarketing calls and texts to wireless numbers using an automatic telephone dialing system or an artificial or prerecorded voice; (b) prior express written consent, meeting 47 C.F.R. § 64.1200(f)(9) and any stricter state requirement (such as the FTSA), for telemarketing calls and texts that use an automated system or an artificial or prerecorded voice; and (c) any consent required by state law for telephone solicitations, regardless of technology.

2.2 Business numbers are not exempt. Customer acknowledges that the TCPA's restrictions on calls and texts to wireless numbers apply even where the person called is a business owner or the number is used for business, and that many small-business owners use personal mobile numbers.

2.3 Consent capture tools. The Service includes lead-capture forms with consent language and a consent gate that records consent evidence and blocks dialing or texting where no consent is recorded. Customer is responsible for the wording of its consent language, for ensuring it names Customer as the seller, for configuring the consent gate correctly, and for the accuracy of consent records it imports from other sources or lead vendors.

2.4 Records. Customer will retain consent records (including the consent language shown, the date and time, the source page or channel, the IP address or other identifying information, and the phone number) and opt-out and do-not-call records for at least five years from the last Communication made in reliance on them, or longer if a limitations period under the TCPA, the FTSA or another applicable law, or the TSR's recordkeeping rule (16 C.F.R. § 310.5), requires. The Service stores these records during the Subscription Term; Customer is responsible for exporting them before its Customer Data is deleted under Section 18.5 of the Agreement.

3. Do-not-call

3.1 National Registry. Before making telephone solicitations, Customer will register with the National Do Not Call Registry, obtain its own Subscription Account Number (SAN) for each area code it calls, and scrub its calling lists against the Registry at least every 31 days, unless an exemption applies that Customer can document.

3.2 State lists. Customer will subscribe to and scrub against state do-not-call lists that apply to its calls, such as Florida's.

3.3 Internal do-not-call list. Customer will maintain a written internal do-not-call policy and an internal do-not-call list, record every do-not-call request, and honour it within the time the law allows (no more than 10 business days under 47 C.F.R. § 64.1200(d)). The Service provides an internal do-not-call list and blocks calls and texts to numbers on it; Customer is responsible for adding requests made outside the Service.

3.4 Reassigned numbers. Customer will use the FCC's Reassigned Numbers Database, or an equivalent method, to check whether a number has been permanently disconnected and reassigned since consent was obtained, before calling or texting on that consent.

4.1 Any reasonable means. Customer will honour a revocation of consent made by any reasonable means, including a reply of "stop", "quit", "end", "revoke", "opt out", "cancel" or "unsubscribe", a voicemail, an email, a statement on a call, or any other words that reasonably express a wish not to be contacted. Under the FCC's revocation rule (47 C.F.R. § 64.1200(a)(10)), in effect since April 11, 2025, Customer must honour revocations within a reasonable time not exceeding 10 business days, and may send one confirmation text within five minutes that does not include marketing.

4.2 Scope of revocation. Customer will apply a revocation to all of its marketing calls and texts to that number, not only the channel or campaign in which it was made, and will not use an informational message as a pretext to resume marketing.

4.3 Rule changes. The FCC has adopted further changes to the revocation rules (including FCC 26-67, with an effective date of November 25, 2026, under which a marketing opt-out revokes consent to all of a caller's marketing robocalls and robotexts) and has asked for comment on shortening the 10-business-day window. Customer is responsible for following the rules as they change.

4.4 Do not wait. Customer will not rely on any state safe-harbour cure period (for example, the FTSA's 15-day notice period for texts) to continue texting a person who has opted out.

5. Calling hours and frequency

5.1 Customer will not make telephone solicitations before 8:00 a.m. or after 9:00 p.m. in the called party's local time (47 C.F.R. § 64.1200(c)(1); 16 C.F.R. § 310.4(c)), or outside any narrower state window, such as 8:00 a.m. to 8:00 p.m. under the FTSA, or state limits on weekends and holidays.

5.2 Customer will comply with state frequency limits, such as the FTSA's limit of three commercial telephone solicitation calls to the same person within a 24-hour period on the same subject matter.

5.3 The Service can block calls outside configured calling hours based on the area code and, where available, the address of the called party. Area codes do not reliably indicate a person's location; Customer is responsible for using the strictest applicable window where location is uncertain.

6. Caller ID, numbers and STIR/SHAKEN

6.1 Accurate caller ID. Customer will transmit accurate caller-identification information, including a number that Customer has the right to use and that can be called back during business hours to reach Customer or make a do-not-call request, as 16 C.F.R. § 310.4(a)(8) and 47 C.F.R. § 64.1601(e) require. Customer will not spoof numbers in violation of the Truth in Caller ID Act (47 U.S.C. § 227(e)).

6.2 Numbers. Telephone numbers are provisioned to Customer's account through MFA's carrier and are subject to carrier rules. Customer will use only numbers provisioned through the Service or numbers it owns and has properly ported or verified. Customer will not rotate or cycle numbers to evade call blocking, call labelling or opt-outs.

6.3 STIR/SHAKEN. MFA's carrier signs outbound calls under the STIR/SHAKEN caller-ID authentication framework. The attestation level depends on the carrier's relationship to the number and to Customer. Accurate attestation depends on Customer using numbers it has the right to use. MFA does not guarantee any attestation level or that calls will not be labelled or blocked by terminating carriers or analytics engines.

6.4 Number release. On termination, telephone numbers may be released to the carrier unless Customer ports them out first, subject to Section 18.4 of the Agreement.

7. Messaging registration (10DLC and toll-free)

7.1 10DLC. Application-to-person text messaging from 10-digit long codes requires brand and campaign registration with The Campaign Registry and carrier approval. Customer will provide accurate, complete information about its business (including legal name, EIN, address, website and contact), its use cases, sample messages and its opt-in method, and will keep it current. Registration may be delayed, limited or rejected by The Campaign Registry or carriers, and MFA does not control the outcome.

7.2 Toll-free. Text messaging from toll-free numbers requires toll-free verification. The same obligations apply.

7.3 Fees. 10DLC brand and campaign registration and vetting fees, toll-free verification fees and other carrier registration fees are passed through to Customer at cost as part of the Usage Charges under Section 8.3 of the Agreement.

7.4 Use within approved campaign. Customer will send only messages that match its approved campaign use case and sample messages, and will re-register before materially changing its use.

8. Message content and opt-out handling

8.1 Identification. Each message campaign will identify Customer by name in the first message and periodically after that, and will include opt-out instructions (such as "Reply STOP to opt out") in the first message and periodically after that.

8.2 STOP and HELP. Customer will keep the Service's automatic STOP and HELP handling enabled. Help responses must identify Customer and give a working contact method.

8.3 Prohibited content. Customer will not send SHAFT content (sex, hate, alcohol, firearms or tobacco), content about cannabis or illegal drugs, or high-risk financial content carriers disallow (such as payday loans, third-party debt collection, or debt relief), except as permitted by its approved campaign, and will follow the CTIA Messaging Principles and Best Practices and carrier codes of conduct.

8.4 Links. Customer will not use public URL shorteners in messages, and will use only links to domains it controls or has the right to use.

9. Predictive dialing and abandonment

9.1 Where Customer uses any dialing mode that may place calls before an agent is available, Customer will keep call abandonment at or below 3% of calls answered by a live person, measured per calling campaign over each 30-day period; connect each answered call to a live agent within two seconds after the called person's completed greeting, or else play a prerecorded message identifying the seller and its telephone number and providing an automated opt-out (where the law permits that message); allow the phone to ring for at least 15 seconds or four rings before disconnecting an unanswered call; and keep records of compliance (16 C.F.R. § 310.4(b)(4); 47 C.F.R. § 64.1200(a)(7)).

10. Call monitoring and recording

10.1 Monitoring. Manager listen, whisper and barge features allow a manager to hear a live call. Customer will give any notice of monitoring required by law to the parties on the call, and will configure its scripts accordingly.

10.2 Recording (when available). Call recording and transcription are not yet available; they are rolling out. When they are available, Customer will not enable them for any call unless Customer has given the notice and obtained the consent required by law, including the consent of all parties in states that require it, such as Florida (Fla. Stat. § 934.03) and California (Cal. Penal Code § 632). Where a call may involve a person in an all-party-consent state, Customer will treat the call as requiring all-party consent.

11. AI voice and artificial voices

AI voice agents are on the roadmap and are not part of the Service today. This Section 11 applies to any AI voice agent MFA makes available later and to any artificial or prerecorded voice Customer uses through the Communications Features.

11.1 Consent. The FCC has ruled that calls using AI-generated voices use an "artificial or prerecorded voice" under the TCPA (Declaratory Ruling, FCC 24-17, released February 8, 2024). Customer will not use an AI voice agent or any artificial or prerecorded voice to call any person without the consent required by Section 2.1, which for telemarketing calls means prior express written consent.

11.2 Identification and opt-out. Every artificial or prerecorded voice call will, at the beginning, clearly identify Customer; state the telephone number of Customer during or after the message; and, for telemarketing, offer an automated, interactive opt-out mechanism, as 47 C.F.R. § 64.1200(b) requires. Customer will disclose that the caller is an AI or automated system where any law requires it, and will not use AI voices to impersonate a real person.

11.3 Supervision. Customer is responsible for the scripts, instructions and knowledge given to AI voice agents and for what they say on its behalf. Section 7 of the Agreement applies to AI output.

12. Telemarketing Sales Rule and state registration

12.1 Customer will determine whether the TSR applies to its campaigns, including campaigns to recruit independent representatives (which are generally to individuals, not businesses) and any campaign that falls outside the TSR's business-to-business exemption, and will comply with it, including its disclosure, misrepresentation, advance-fee, recordkeeping and calling-time requirements.

12.2 Customer will obtain any state telemarketing or telephone-solicitor licence or registration and post any bond required for its calling activity (for example, under Florida's Commercial Telephone Seller law, Fla. Stat. ch. 501, part IV, unless an exemption applies) and in each other state where it calls.

13. MFA's tools are aids, not guarantees

13.1 The Service includes tools designed to help Customer comply, including the consent gate, internal do-not-call list and blocking, calling-hour blocking, STOP/HELP handling, and licence and registration tracking. These tools depend on the accuracy of the data and configuration Customer provides, and on third-party data sources that may be incomplete or delayed.

13.2 MFA's tools are aids, not guarantees. They do not cover every rule that may apply, and they do not replace Customer's own compliance program, policies, training, supervision and legal advice. Customer remains solely responsible for the lawfulness of every Communication, whether or not a tool allowed it to be made.

14. Cooperation, complaints and enforcement

14.1 Traceback and complaints. Customer will respond within 24 hours to any traceback request, carrier inquiry or consumer complaint about its Communications that MFA forwards, and will provide consent and call records on request. MFA may share Customer's identity and relevant records with carriers, the Industry Traceback Group, The Campaign Registry and regulators as required or permitted by law and the Agreement.

14.2 Suspension. MFA may suspend Communications Features, numbers or campaigns immediately under Section 18.2 of the Agreement where it reasonably believes this Addendum or the AUP has been breached, where complaint or opt-out rates indicate unlawful or unwanted traffic, or where a carrier, registry or regulator requires.

14.3 Indemnity and liability. Customer's obligations under this Addendum are covered by Customer's indemnity in Section 16.2 of the Agreement, and breach of this Addendum is excluded from the limitation of liability under Section 17.3 of the Agreement.

15. Fees

Usage of the Communications Features is billed under Section 8.3 of the Agreement at the Usage Rates published at https://brokeros.mfautomations.ai/pricing, and registration fees are passed through at cost, monthly in arrears.

16. No emergency calling

The Service does not support calls to 911 or other emergency services.

17. Contact

MF Automations LLC, 233 NE 27th St, Miami, FL 33137 Maui · (305) 216-3272 · maui@mfautomations.ai

Questions: maui@mfautomations.ai