RelayKite Business Terms of Service

This document is a working draft for qualified legal review. It has not been approved as RelayKite’s final contract. The RelayKite operating legal entity and notice address, exact managed-service scope and providers, privacy and data-processing details, commercial policy, and governing law and venue have not been confirmed in the available product materials. Those items are called out below and must be completed and reviewed before this draft is represented as legally approved or used as the complete paid-service agreement.

The business representative’s acceptance records agreement to this identified draft version for the business workspace. It is separate from any consent a business must obtain from its leads or other end customers. Acceptance does not itself create or record a lead’s consent to receive calls, texts, or other messages.

The intended service relationship is between the RelayKite operator (whose legal name and notice address remain to be confirmed) and the local business identified in the business workspace and its accepted written service order, if any (the “Business”). A person accepting for the Business represents that they are its owner or are authorized to bind it to these terms. The Business is responsible for activity by its account users and for keeping access limited to people it authorizes.

People who contact a Business, submit an inquiry, or appear as lead records are not parties to this subscriber agreement and are not asked to accept it.

The checked-in RelayKite workspace currently supports business profile and timezone settings, booking-URL and lead-channel labels, lead records, response-template records, manually recorded lead status and appointment details, activity history, and a shareable inquiry form. Lead-channel labels are preferences; they do not connect an external channel. Response templates are stored in the workspace; the application has no message-send API or automatic calendar integration in this checkout. The inquiry form records a lead from the information the visitor submits.

RelayKite’s public marketing describes managed setup, configured follow-up, after-hours communication, monitoring, and calendar handoff. The repository does not establish which of those managed operations, messaging channels, integrations, personnel, or providers are active for a particular Business. Any such work is included only when RelayKite and the Business confirm it in a written service scope or order that identifies what is provided, by whom, through which channels, and any applicable dependencies. Marketing language alone does not add an integration or operational commitment to the workspace.

RelayKite does not promise a particular response time, message delivery, lead conversion, revenue result, or booked appointment. An inquiry may be delayed, filtered, incomplete, duplicated, or unavailable. Where an agreed service depends on carriers, messaging platforms, calendars, internet access, customer systems, or other third parties, their availability, rules, and changes can affect the result. The Business remains responsible for reviewing inquiries and confirming appointment details with its customers.

Workspace records and configured settings are operational tools. A booking URL, channel label, template, or manually entered appointment is not evidence that an external calendar or messaging system was connected or that a message or appointment was completed.

The Business must provide and maintain accurate business identity, service and offer details, contact information, availability, timezone, booking instructions, and any written service configuration. It must review inquiries and appointments, correct errors, respond where needed, and make its own decisions about customer eligibility, pricing, and service commitments.

The Business is responsible for the lawfulness, accuracy, and permissions for information it collects or supplies; for notices and legal bases required for its use of lead data; for controlling account access; and for instructions it gives RelayKite. It must not submit information it has no right to use, and should limit submitted personal information to what is reasonably needed for the agreed service.

A Business that uses any separately agreed messaging or calling service is responsible for obtaining and retaining legally sufficient consent and other permissions appropriate to the sender, purpose, recipient, technology, and channel before communication; providing required disclosures and sender identity; and complying with applicable laws, carrier requirements, platform policies, and registration rules. The Business must promptly honor consent revocation, do-not-contact requests, and opt-outs through every channel and method that applies to its program.

The workspace does not currently record SMS consent or provide a verified SMS suppression or opt-out workflow. Neither this agreement nor a lead record is consent to message that lead. Do not assume RelayKite captures consent, registers a number, sends a text, or processes an opt-out unless the written service scope confirms the actual operation and assigns responsibility for each step. Before any SMS program is enabled, the Business and RelayKite must document the consent source, disclosures, sender identity, supported opt-out paths, monitoring, and who acts on requests. Qualified counsel must verify current federal, state, carrier, and program-specific requirements, including how different revocation methods and timing rules apply. The FCC’s 2024 consent-revocation order is one relevant source, not a substitute for that review.

Reference for review: FCC 2024 consent-revocation order · FCC 2023 proposed rule text.

The application stores workspace business name and type, timezone, booking URL and channel labels; lead name, company, email, phone, notes, source/channel, status, and manually recorded appointment date and time; activity entries for status, appointment, and conversation-note changes; response templates; and name, email, and message submitted through a shareable inquiry form. The acceptance record also stores the terms version and content hash, acceptance time, acting account identity snapshot, submitted Business name, and the authority and agreement confirmations.

The available materials do not establish a retention or deletion period, the complete processor or subprocessor list, the parties’ privacy-law roles, a privacy notice, a security certification, or specific breach-notification commitments. Those facts and the applicable privacy documentation must be confirmed with the operator before this draft is treated as complete. This document does not invent those practices or make a compliance certification. The Business must provide required notices to people whose information it collects and should avoid placing sensitive or regulated information in free-text fields unless the written service scope and applicable safeguards have been confirmed.

The application has no checkout or subscription billing flow, and the available materials do not state a price or commercial policy. These draft terms therefore do not set a subscription fee, billing cadence, renewal, tax treatment, failed-payment process, cancellation method or effective date, or refund rule. Before paid service begins, a written order must state the actual price and each applicable commercial term. No amount, renewal, cancellation deadline, or refund entitlement should be inferred from signup copy or workspace access.

The Business must keep its credentials secure, remove access when a user no longer needs it, and promptly report suspected unauthorized use through the operator’s confirmed support or notice channel. The Business may use the service only for its own lawful business operations and must not misuse the service, interfere with its operation, or submit unlawful content or data.

Service availability and features may change as software, third-party dependencies, or an agreed scope changes. The parties should document material managed-service or integration changes in writing. A party may raise a material breach through the confirmed notice channel and seek a reasonable opportunity to resolve it where appropriate; urgent action may be needed to address security, legal, or third-party platform risks. The operator’s identity, support channel, notice address, customer-data export/deletion process, and any paid-service termination procedure remain to be confirmed and must be stated in the final terms or order.

Each party remains responsible for its own conduct, its own legal obligations, and losses to the extent caused by its breach, negligence, or willful misconduct, subject to applicable law. The Business remains responsible for its offers, customer relationships, lead-data permissions, and instructions. RelayKite remains responsible for obligations it actually undertakes in the final written service scope. Neither party uses this draft to claim that the other can never be responsible.

No monetary cap, consequential-damages exclusion, indemnity, or special allocation is set in this draft because the appropriate terms depend on the confirmed operator, service scope, insurance and commercial arrangement, and governing law. Qualified counsel must draft any such allocation with fair language and exceptions for liability that cannot lawfully be limited. Nothing in these terms waives a right or liability that applicable law does not allow a party to waive.

The RelayKite operator’s legal name, legal notice address, governing-law choice, venue, dispute process, and any required consumer or business notices have not been supplied. These terms do not select a jurisdiction or forum. Those details must be completed from the operator’s real business facts and reviewed by qualified counsel before this draft is approved.

Any paid or managed work must be described in an order or service scope accepted by both parties. If a later terms version is designated current, each Business must accept that version before using workspace features. The recorded acceptance identifies the version and a cryptographic hash of the content presented at that time; it does not record or replace an end customer’s communication consent.