SMS Program Terms

These are the public opt-in steps:

1) Open lol.gl, sign in, and start the required new-agent onboarding chat at /onboard.

2) Enter the phone number for the account/agent setup. The next onboarding card asks for communication preferences before the rest of the app is available.

3) Optionally check the dedicated SMS consent box (unchecked by default, with Privacy, Terms, and SMS Terms links) and separately choose whether account support calls are allowed.

4) Select Save and continue. The user's consent choices, version, timestamp, source, path, and consent copy are recorded with the account in our auth system for audit.

5) To receive any SMS, the user must have given this explicit opt-in or, where applicable, initiated a service-related text conversation to our platform number in line with the first message we send.

SMS checkboxes on Create account are off by default, with links to Privacy, Terms, and this page; we store consent version, time, and consent copy in the user’s auth record. Optional AI/recorded-voice calls use a different checkbox where offered.

Reply STOP, CANCEL, END, QUIT, or UNSUBSCRIBE (case and spacing as supported by the carrier) to end SMS from this program. After STOP, the user should receive a confirmation; we will not send further program SMS to that number until the user opts back in, except where a carrier or law still allows strictly essential transactional text. The product and edge logic treat STOP as a hard outbound suppress for the platform path.

Reply HELP for a short, plain summary of the program, how to get support, and the STOP instruction. A typical help reply can direct you to email the support address and link to the SMS and privacy terms on the web.

Where the platform supports re-subscribe after a prior opt-out, reply START to the same sending number, or complete an in-product re-opt-in, so we can re-verify consent before new traffic.

For anything keywords do not cover, or to confirm opt state for a ticket: support@lol.gl.

The following are representative. Actual wording and length may change slightly, but the sender identification, use case, and help/stop path stay consistent. These lines are suitable for Twilio, Telnyx, and similar portals when the form requires sample messages (usually two or more).

Sample 1: Ava Associates / lol.gl: Your operator setup step is complete. Questions? support@lol.gl Reply STOP to opt out, HELP for help. Msg & data rates may apply.

Sample 2: Ava Associates / lol.gl: Reminder: your operator needs a quick approval in the app. Reply STOP to opt out, HELP for help.

Sample 3: Ava Associates / lol.gl: We received your HELP request. Email support@lol.gl or reply with your question. STOP to opt out.

We will not sell or share user mobile information or SMS program opt-in data and consent for promotional or third-party marketing purposes, as our Privacy Policy states in the dedicated section. Operational sharing with our messaging and host providers is only for delivering and protecting the service.

Our Privacy Policy URL, Terms URL, and this page should be the three links used in a typical US A2P or toll-free submission unless the portal has additional optional fields. Keeping those URLs current and identical across forms is essential for one-pass approval.

We may add or change message types in line with the same overall use case (e.g. new in-product reminder when we ship a new feature) without starting a new cold SMS program, provided the consent and this page are updated and, where a carrier requires, the registration is updated. Material changes to opt-in, STOP, or the basic character of the program will be reflected in this “Last Updated” line and, where the law and product require, in additional notice in app or by email to affected users.