> ## Documentation Index
>
> Fetch the complete documentation index at: https://lithi.ai/llms.txt
>
> Use this file to discover all available pages before exploring further.

# SMS & Calling Policy

Last Updated: October 10, 2026

This policy describes SMS messages Lithi may send in an enabled account or service workflow. A Compute estimate or approval for Connect email or LinkedIn does not authorize SMS or voice. Providing a phone number or using the website is not general permission for Lithi or a customer to send marketing messages or calls.

## Contents

- [Message scope](#message-scope)
- [Permission and channel choice](#permission-and-channel-choice)
- [Applicable SMS workflows](#applicable-sms-workflows)
- [Stopping SMS](#stopping-sms)
- [Calls and other channels](#calls-and-other-channels)
- [Carrier charges and delivery](#carrier-charges-and-delivery)
- [Provider and jurisdiction terms](#provider-and-jurisdiction-terms)
- [Privacy and security](#privacy-and-security)
- [Primary action](#primary-action)

## Message scope

Lithi may use SMS for account or service notifications where an enabled workflow uses that channel. This policy does not turn a Compute job, estimate, quote, or Connect email or LinkedIn plan into an SMS or voice service.

## Permission and channel choice

Access to an account or permission to use one source does not approve a message. A Connect plan is limited to the sender, recipients, content, purpose, and timing that you reviewed. Approval for Email or LinkedIn does not authorize SMS, a call, or a change of recipients or content.

## Applicable SMS workflows

Where enabled, an SMS may carry an account or service notice such as billing or status information. A message is limited to the service workflow, sender, recipient, and purpose it names. This policy does not promise marketing campaigns, lead qualification, recurring outreach, or AI voice calls.

## Stopping SMS

Reply STOP to an applicable SMS or email sms-optout@lithi.ai. Use any additional stop instructions included with the message. This policy does not promise a confirmation time or a deadline for processing a request.

## Calls and other channels

An SMS permission does not authorize a phone call. If a separate service agreement covers calling, its sender, recipients, purpose, consent, provider path, and stop conditions govern. This policy does not establish universal calling hours or authorize outbound marketing calls.

## Carrier charges and delivery

Messages identify the applicable service and sender and include the available stop instructions. A recipient's mobile provider may apply its own message or data charges. Delivery depends on the provider and recipient service; this policy does not guarantee timing or delivery.

## Provider and jurisdiction terms

Communications requirements depend on the actual message, sender, recipient, channel, provider, jurisdiction, and applicable agreement. The current [Subprocessor register](/trust/subprocessors) describes provider roles for their stated purposes. This policy does not establish a general legal basis or permission to contact third parties.

## Privacy and security

Phone numbers and messaging records are handled for the service purpose that uses them. See the [Privacy Policy](/legal/privacy) and applicable agreement for data categories and terms. Do not send passwords, payment details, or private customer content through ordinary support channels.

A phone number in a business dataset is not permission to contact its owner. Compute data preparation and classification do not supply SMS or calling consent. A separate communications workflow must establish its own authority before any message or call.

## Primary action

[Request a communications review](/contact)