Beta Agreement
Client:
This Beta Agreement is between Rook LLC, a Utah limited liability company ("Rook"), and the Client identified above. An adult authorized to bind Client must sign or affirmatively accept this Agreement and the incorporated terms identified at acceptance.
On this page
1. Beta service
Rook provides enabled AI-assisted messaging, scheduling and administrative features for evaluation and feedback. Beta features may change, be unavailable or be withdrawn. No uptime or support-response commitment applies. Express contractual obligations, including data protection and confidentiality, remain in effect.
2. No beta fees or automatic paid enrollment
Rook charges no fees during the beta; Client pays for its independently contracted third-party services. Paid service requires Client's affirmative acceptance of disclosed pricing, recurring billing, usage limits, additional charges and cancellation terms. Beta participation or continued use does not authorize billing. Client may decline and request its data under Section 8.
3. Related terms
Rook's Terms of Service (rooksync.com/terms), Messaging Terms (rooksync.com/messaging-terms) and supplied Data Processing Addendum ("DPA"), in the versions provided at acceptance, are incorporated. The Privacy Policy (rooksync.com/privacy) explains information practices. Refund terms apply only to an accepted paid plan.
This Agreement controls beta-specific conditions; the DPA controls personal-data processing on Client's behalf; Messaging Terms control messaging requirements. The Terms of Service otherwise apply, including governing law and disputes. Exhibit A governs customer wording and workflows. Client acceptance does not supply customers' consent.
4. Client responsibilities and oversight
Client must provide accurate, lawful business information; secure accounts; authorize integrations; and lawfully provide customer data. Client remains responsible for its work, prices, policies, invoices, payment links, professional decisions and approved drafts.
Obtain and retain consent required by law and provider policies.
Outbound texting to imported contacts, including invoice reminders based on uploaded lists or connected billing records, is disabled. Importing a record does not authorize a text. A later direct inquiry or separate approved opt-in must use the applicable consent workflow.
The U.S.-number restriction in the Terms applies during beta. Keep the no-marketing and consent-evidence requirements.
No marketing, purchased lists or bypassing opt-outs. Texting imported customers and payment reminders remain disabled until required permissions and an approved workflow are established.
Maintain current escalation contacts, monitor handoffs and approvals, and provide a person for emergencies, complaints, refunds and human-assistance requests. AI and delivery can fail; maintain alternative customer-service arrangements. Rook is not an emergency response or continuous monitoring service. Do not remove its AI disclosure or present it as human.
5. Feedback
Client will provide reasonable, honest feedback. Rook may use suggestions without compensation, subject to confidentiality and the DPA. Feedback does not authorize customer-data disclosure or AI training. Public statistics must be supported and properly aggregated or de-identified; identifying Client requires separate written approval.
6. Testimonials and publicity
Any testimonial, named case study, name or logo requires separate written approval of its exact content and intended use. Public endorsement is voluntary; free access is not conditioned on positive reviews. Endorsements must be truthful, support performance claims and disclose free beta access or other material benefits where required. Approval does not authorize customer-data disclosure.
7. Support
Use dashboard Help chat, the "contact admin" text command or support@lunisolutions.com. Beta response times are not guaranteed. These channels do not provide emergency assistance.
8. Data and exit
Client retains its rights in Client Data, subject to others' rights. Export, return and deletion follow the DPA, including requests after dashboard access ends while records remain available. Active records are deleted within 90 days after service ends, or earlier on lawful instruction, subject to the DPA's limited retention exceptions and protected backups. Minimal consent and suppression records are retained only as lawfully necessary. Data protection obligations continue after beta access ends.
If separately launched, enabled and authorized by Client and the homeowner, selected home-file records are retained under the Terms' home-file provision and the homeowner's direct agreement. Client's ordinary records remain subject to the DPA's deletion schedule. Client's beta acceptance alone does not activate a home file or replace homeowner acceptance.
9. Disclaimers and liability
TO THE EXTENT PERMITTED BY LAW, ROOK'S TOTAL AGGREGATE LIABILITY ARISING FROM FREE-BETA SERVICE IS LIMITED TO $100, INCLUDING CLAIMS CONCERNING CONFIDENTIALITY OR DATA SECURITY. THIS BETA CAP CONTROLS OVER THE GENERAL AND SECURITY CAPS IN SECTION 12 OF THE TERMS OF SERVICE FOR THOSE CLAIMS. THE TERMS' DAMAGES EXCLUSIONS AND TREATMENT OF DIRECT INCIDENT-RESPONSE COSTS OTHERWISE APPLY. THESE LIMITATIONS DO NOT APPLY TO FRAUD, WILLFUL MISCONDUCT, GROSS NEGLIGENCE, OR LIABILITY THAT APPLICABLE LAW DOES NOT PERMIT THE PARTIES TO LIMIT. THEY DO NOT EXCUSE CONTRACTUAL DATA-PROTECTION DUTIES OR LIMIT REGULATORS' POWERS OR NON-PARTIES' RIGHTS. THEY DO NOT GOVERN A HOMEOWNER'S SEPARATE HOME-FILE AGREEMENT.
10. Ending participation
Client may leave at any time through support@lunisolutions.com or an available cancellation method. Rook may end participation on 14 days' email notice, or suspend or end access immediately when reasonably necessary for unlawful use, an incurable breach, a serious security risk or a provider restriction. Rook will give notice and reasons where lawful and practical; other curable breaches follow the Terms' notice and cure procedure.
This Agreement ends when participation ends or an expressly accepted paid plan begins. Accrued rights, approved feedback rights, confidentiality, data protection, applicable liability and dispute terms survive as needed. Rook will provide the accepted Agreement and incorporated terms.
Client representative: __________________________ Title: ______________________
Signature or recorded electronic acceptance: __________________ Date: __________
For Rook LLC: Tyler Chambers, Member
Signature or recorded electronic acceptance: __________________ Date: __________
EXHIBIT A
Customer Consent and AI Disclosure
Rook must automatically insert the actual Business Name, Business Contact, Amount, Work Description, Payment Link and Appointment Details wherever indicated below. Business Contact means the business’s public telephone number or website. Payment links must be verified and belong to the business.
Use these notices only in enabled workflows. Texting is restricted to U.S. numbers. Consent must identify the sending business and permitted message categories; importing records or having an existing customer relationship does not itself authorize texts.
Keep consent checkboxes separate and unticked. Record the recipient’s number, business identity, consent scope, exact wording and version, date, time and method. For website consent, also record the page and IP address; for message-based consent, retain the disclosure, affirmative response and message identifiers.
An existing opt-out remains effective until valid renewed consent is recorded. Coordinate provider and Rook responses to avoid duplicate confirmations. Planned workflows remain disabled until implemented and approved.
A1. Website Form or Chat SMS Consent
Separate, unticked checkbox:
“I agree to receive automated service texts from [Business Name], sent through its AI assistant, at the number I provided about my request and related work, including replies, price ranges, scheduling, appointment reminders, job updates, invoice notices, payment reminders and nonpromotional requests for feedback after a job. No marketing texts. Message frequency varies. Message and data rates may apply. Reply STOP to opt out or HELP for help. Consent is optional and is not required to request or purchase services. Privacy: https://rooksync.com/privacy. Messaging Terms: https://rooksync.com/messaging-terms.”
Allow submission without SMS consent and provide the business’s non-text contact method. Link the business’s own applicable privacy notice alongside Rook’s disclosures where available.
A2. Missed-Call Greeting
“You’ve reached [Business Name]. Sorry we missed your call. To request texts from our AI assistant about this call, press 1. Message and data rates may apply. Reply STOP to stop texts or HELP for help. If you prefer not to text, contact us at [Business Contact].”
Record the caller’s number, date, time, prompt version and key press. Calls are not recorded.
Pressing 1 requests a response about that call, not recurring reminders. Use this method only where permitted by the applicable messaging program. Obtain any additional required written consent before recurring messages.
A3. Opening Customer Text
“Hi, this is [Business Name]’s AI assistant. I can help with your request or scheduling. Ask to reach a person anytime. Reply STOP to opt out or HELP for help. Message and data rates may apply.”
Use after an authorized inbound exchange or approved opt-in. For urgent or distressed customers, use the appropriate A4 or A5 notice instead of the ordinary assistance language.
If the first message clearly declines further contact, including “no thanks,” send only the A6 opt-out confirmation, which includes AI identification. Do not send a separate opening or continue the conversation.
Use A13 for website chat.
A4. Hand-Off to a Person
After the hand-off succeeds:
“I’m [Business Name]’s AI assistant. I’ve sent your request to the business’s team so a person can follow up. You can also contact them at [Business Contact].”
If it fails:
“I’m [Business Name]’s AI assistant. I couldn’t send your request to the team. Please contact the business directly at [Business Contact].”
Confirm delivery only after success. Do not promise a response time. If this is the first SMS, include the STOP, HELP and message-and-data-rate disclosures from A3.
A5. Urgent Situation
Fixed system message:
“I’m [Business Name]’s AI assistant, not an emergency service. If anyone is in immediate danger, call 911. Please contact the business directly at [Business Contact] about this urgent request.”
After successful escalation only, add:
“I’ve sent your message to the business’s team.”
The system supplies the fixed 911 referral; the AI must not generate emergency advice. The assistant must not give property-safety instructions, including instructions to turn things off, leave the property, or use buckets or tarps. Do not promise monitoring, dispatch or a response time.
Consent and opt-out controls continue to apply.
A6. STOP, START and HELP
STOP confirmation:
“You’ve been unsubscribed from [Business Name] texts. No further service texts will be sent unless you choose to subscribe again. — [Business Name] AI assistant”
Send one nonpromotional confirmation. Honor supported keywords and clear requests to stop through other reasonable channels.
START confirmation after valid renewed consent:
“You’re subscribed again to the automated service texts you agreed to receive from [Business Name]. No marketing. Message frequency varies. Message and data rates may apply. Reply STOP to opt out or HELP for help. — [Business Name] AI assistant”
A deliberate START from the recipient’s number may document renewed consent for the same business and previously disclosed scope when the supporting record is available and the approved program permits it. A second reply is not automatically required. If the disclosure or scope is missing, unclear or changed, obtain informed confirmation before resuming service messages. Carrier unblocking alone must not enable additional categories.
HELP response:
“[Business Name] uses an AI assistant for service texts. For help or a person, contact the business at [Business Contact]. Reply STOP to opt out. Message and data rates may apply.”
A7. Client Import Confirmation
“Importing customer records does not authorize text messages. Before enabling invoice reminders, I confirm that each selected recipient has provided documented written consent to receive these messages from [Business Name], that I can provide the consent record, and that no opt-out has been overridden.”
Outbound texting to imported contacts, including invoice reminders, remains disabled. Use this unticked acknowledgment for any approved future activation, together with recipient-level consent checks. It neither supplies customer consent nor clears an opt-out.
Do not require the acknowledgment merely to store records while messaging remains off.
A8. Invoice Notice and Reminders
Invoice notice:
“Hi, this is [Business Name]’s AI assistant. Your invoice is $[Amount] for [Work Description]: [Payment Link]. Questions or a person? Reply here. Reply STOP to opt out.”
First reminder:
“[Business Name]’s AI assistant here. Our records show your invoice for $[Amount] for [Work Description] remains unpaid: [Payment Link]. Already paid or need to discuss it? Reply and the team will check. Reply STOP to opt out.”
The default schedule is days 3, 7, 14 and 21 after the invoice notice, with no more than four automated reminders per invoice. Apply the invoice’s payment terms; do not describe it as overdue before its due date.
Before every send, check consent, opt-out status, recipient, amount, link and payment status. Stop on payment, a dispute, a wrong-recipient report or an opt-out. Refer disputes and recipient errors to a person and keep reminders suspended while unresolved. Pausing or reissuing an invoice must not reset the count for the same obligation.
No threats or promotions. A first SMS after opt-in must also include HELP and message-and-data-rate information.
A9. Continuing AI Identification
Add this identifier to every automated customer text that does not already clearly identify the AI assistant:
“— [Business Name] AI assistant”
Apply it to conversational replies, reminders, follow-ups, job updates, feedback or review requests, invoice notices and payment reminders. Identify actual human replies accurately.
A10. Appointment-Reminder Consent by Text
Within an authorized SMS exchange, send:
“Would you like one automated text reminder from [Business Name] the day before your appointment on [Appointment Details]? Reply YES to agree. Message and data rates may apply. Reply STOP to opt out or HELP for help. — [Business Name] AI assistant”
Record YES with the full disclosure, number, appointment details, wording version, date, time and message identifiers.
Permission covers that appointment reminder only. It does not authorize invoice or maintenance reminders or unrelated recurring messages. Do not send an unsolicited consent request or use YES to bypass an existing opt-out.
A11. AI Unavailable, Paused or Usage Limit Reached
After successful notification:
“Thanks for your message. Automatic replies are currently unavailable. I’ve sent your message to [Business Name]’s team. Please contact them directly at [Business Contact] if you need a response sooner. — [Business Name] AI assistant”
If notification fails:
“Automatic replies are currently unavailable, and I couldn’t notify the team. Please contact [Business Name] directly at [Business Contact]. — [Business Name] AI assistant”
The independent urgent-message check must continue without the AI during unavailability, usage limits and operational pauses. Use A5 for detected urgent situations and attempt the owner alert. Describe this safeguard as operational only after implementation and testing.
Respect opt-outs and avoid repeated unavailable notices during one conversation.
A12. Moving Facebook or Instagram Messages to Text
Within the permitted social-platform messaging window, send:
“Want to continue this request by text with [Business Name]’s AI assistant? Reply with your own U.S. mobile number and YES to agree to automated texts about this request, including replies and scheduling. No marketing. Message frequency varies. Message and data rates may apply. Once texting begins, reply STOP to opt out or HELP for help. Consent is optional and is not required to request or purchase services. Privacy: https://rooksync.com/privacy. Messaging Terms: https://rooksync.com/messaging-terms.”
A number alone is not consent. Retain the disclosure and affirmative response and verify control of the supplied number through the approved process before substantive SMS communication.
An existing opt-out requires valid re-enrollment under A6; social-platform consent must not bypass it. Obtain additional permission for message categories outside the disclosed request.
A13. Website Chat Disclosure
Display before the visitor sends the first message:
“You’re chatting with [Business Name]’s AI assistant, not a person. You can ask to reach a person anytime. The business will respond when available.”
Keep “[Business Name] AI assistant” visible in the chat header throughout the automated conversation. Clearly identify a human takeover.
STOP and HELP are SMS controls, not website-chat controls. Use A1 separately if the visitor chooses texts.
A14. Spanish-Language Communications
Use reviewed Spanish versions of the applicable notices when customers communicate in Spanish. Preserve the same consent scope, optional consent, business identity, AI disclosure, contact information and messaging disclosures. Record the language and wording version.
Opening SMS:
“Hola, soy el asistente de inteligencia artificial (IA) de [Business Name], no una persona. Puedo ayudarle con su solicitud o programar una cita. Puede pedir hablar con una persona en cualquier momento. Responda STOP para dejar de recibir mensajes o HELP para obtener ayuda. Pueden aplicarse tarifas de mensajes y datos.”
Continuing identifier:
“— Asistente de inteligencia artificial (IA) de [Business Name]”
Website chat:
“Está conversando con el asistente de inteligencia artificial (IA) de [Business Name], no con una persona. Puede pedir hablar con una persona en cualquier momento. La empresa responderá cuando esté disponible.”
STOP confirmation:
“Ya no recibirá mensajes de texto de [Business Name], a menos que decida suscribirse de nuevo. — Asistente de inteligencia artificial (IA) de [Business Name]”
Fixed urgent referral:
“Soy el asistente de inteligencia artificial (IA) de [Business Name], no un servicio de emergencias. Si alguien está en peligro inmediato, llame al 911. Comuníquese directamente con la empresa en [Business Contact].”
After successful escalation only:
“He enviado su mensaje al equipo de la empresa.”
Present consent disclosures in Spanish before seeking a Spanish-language affirmative response. Support “SÍ” or “SI” where appropriate to the approved workflow. Keep STOP, START and HELP available and honor clear Spanish requests to stop, even when they are not configured keywords.
Spanish-language service remains restricted to U.S. numbers.
A15. Photo Descriptions and Assessments
Show prominently before the first photo description or other personalized assessment in a conversation, in SMS and website chat:
“You’re interacting with [Business Name]’s AI assistant, not a person. Photo descriptions are preliminary observations, not an inspection or diagnosis. A licensed professional must assess the work.”
Spanish:
“Está interactuando con el asistente de inteligencia artificial (IA) de [Business Name], no con una persona. Las descripciones de fotos son observaciones preliminares, no una inspección ni un diagnóstico. Un profesional con licencia debe evaluar el trabajo.”
Descriptions say what is visible, never a final diagnosis, and give no property-safety instructions. Repeat this notice if the conversation resumes after the AI identification would otherwise be renewed.
A16. Estimate Follow-Up Consent by Text
Within an authorized SMS exchange, send:
“Would you like automated follow-up texts from [Business Name]’s AI assistant about this estimate, including updates and answers to questions? Reply YES to agree. We’ll stop when this request closes or after 60 days without your reply. Consent is optional and not required to purchase services. Message frequency varies; message and data rates may apply. Reply STOP to opt out or HELP for help. Terms: rooksync.com/messaging-terms. Privacy: rooksync.com/privacy.”
Record YES with the full disclosure, number, estimate request, wording version, date, time and message identifier. An inbound text permits the immediate conversation only; it does not authorize recurring follow-ups.
Stop follow-ups when the estimate request closes, the customer opts out, or 60 days pass without the customer’s reply, whichever happens first. Permission covers follow-ups about that estimate only.
Rook LLC
Privacy Policy: https://rooksync.com/privacy
Messaging Terms: https://rooksync.com/messaging-terms
Rook technical support: support@lunisolutions.com