These Terms of Service apply to the Retell integration apps listed below. Each app has its own section with terms specific to that integration. If a marketplace asks for a Terms of Service URL, you can link directly to the relevant app section (for example, /terms-of-service#salesforce).
1. Our Services
About these integrations
Each app is installed inside a third-party platform and connects your account on that platform to Retell AI (retellai.com), a conversational voice AI platform. This allows AI phone agents to place or receive calls using data from the connected platform. All apps use the same backend service, the "Integration API." See our Privacy Policy for details about how data is handled.
Retell for Salesforce
Managed package: Setup Wizard (LWC) + "Start Retell Outbound Call" Flow action, distributed via Salesforce AppExchange.
- Service. This package lets authorized users in your organization start outbound AI phone calls through Retell AI and view the results in Salesforce. You need your own Retell AI account and API key, and users must have the Retell Integration User permission set.
- OAuth connection. When you connect Salesforce, our Integration API is authorized only for the api and refresh_token scopes. We do not request broader scopes such as full or Chatter API access. Access is still limited by the sharing rules and permissions of the user who completes "Connect Salesforce."
- Your responsibilities. You are solely responsible for getting any consent required to call or record people whose information is in your organization's data. You must also follow all telemarketing, robocall, and call-recording laws that apply to your calls, including TCPA and equivalent state or national rules.
- Bulk calling limits. Salesforce callout limits apply (for example, 100 synchronous callouts per Apex transaction). Set your Flow entry criteria narrowly enough to stay within those limits.
- Two layers of access. Backend writebacks use the stored OAuth token from the user who connected Salesforce. Calls started inside Salesforce run as the Flow/Apex user, who must also have the Retell Integration User permission set.
- For warranty disclaimers, liability limits, and governing law, see the General Terms of Service below.
Retell for Zoho CRM
Zoho CRM extension (Sigma / Extension Toolkit): settings widget + outbound-call custom action, distributed via the Zoho Marketplace.
- Service. This extension lets you start outbound AI phone calls from Zoho CRM records and write the results back to those records. You need your own Retell AI account and API key and must authorize the connection through a Zoho Connected App OAuth flow.
- Two permission layers. The Sigma extension widget uses embedded SDK capabilities. Separately, "Connect Zoho CRM" authorizes our Integration API through OAuth with scoped access to ZohoCRM.org.READ, org variables, module metadata, and ZohoCRM.modules.READ. We do not request ZohoCRM.modules.ALL.
- Deluge functions. Outbound calling and server-side integration use Deluge functions installed by an administrator (bundled samples). These functions run with the permissions of the CRM user who triggers them and read phone numbers from records when a call is placed.
- Your responsibilities. You are solely responsible for getting the required consent to call or record contacts in your CRM. You must also follow all applicable telemarketing, robocall, and recording-consent laws.
- For warranty disclaimers, liability limits, and governing law, see the General Terms of Service below.
Retell for Airtable
Airtable Custom Extension (Blocks SDK): setup wizard + dashboard + Outbound Call tab.
- Service. This extension lets you start outbound AI phone calls from rows in an Airtable base and write the results back to the same row. You need your own Retell AI account and API key. When you connect through Airtable OAuth, you choose which bases the integration can access.
- Your responsibilities. You are solely responsible for getting the required consent to call or record people represented in your Airtable base. You must also follow all applicable telemarketing, robocall, and recording-consent laws.
- Collaborator access. Integration settings, including OAuth tokens, are stored in the extension's global configuration inside your base. Collaborators who can edit the extension may be able to see those settings. Only connect credentials you are comfortable making visible to those collaborators.
- For warranty disclaimers, liability limits, and governing law, see the General Terms of Service below.
Retell for Google Sheets
Google Workspace Add-on: setup wizard + sidebar, distributed via the Google Workspace Marketplace.
- Service. This add-on lets you start outbound AI phone calls from rows in a Google Sheet and write the results back to the same row. You need your own Retell AI account and API key. After you connect your Google account through our Integration API, backend Google OAuth for Sheets, Drive, and Docs may be used to sync call results and linked files.
- Your responsibilities. You are solely responsible for getting the required consent to call or record people listed in your sheet. You must also follow all applicable telemarketing, robocall, and recording-consent laws, especially when using auto-process.
- Auto-process. If you turn on auto-process, a call starts automatically when a mapped Phone cell is edited through an Apps Script installable trigger. Make sure this setup meets your consent and compliance requirements before using it on a live sheet.
- Local settings. Add-on preferences are stored in Google Apps Script user properties on your Google account. They are cleared when you uninstall the add-on.
- For warranty disclaimers, liability limits, and governing law, see the General Terms of Service below.
Retell for Notion
Notion public OAuth integration with a companion setup/dashboard web app.
- Service. This integration lets you start outbound AI phone calls from Notion database rows and write the results back to the same row. You need your own Retell AI account and API key. During Notion authorization, you choose which pages and databases to share with the integration.
- Notion capabilities. The integration only requires Read content and Update content. It does not request Insert content, user information, comments, or file access.
- Consent / DNC. Before an outbound call can be placed, your configured consent/DNC property must be set to an accepted value (checkbox, Yes, or Allowed). The integration skips duplicate automation events and numbers that were dialed recently.
- Your responsibilities. You are solely responsible for getting the required consent to call or record people represented in your Notion content. You must also follow all applicable telemarketing, robocall, and recording-consent laws.
- For warranty disclaimers, liability limits, and governing law, see the General Terms of Service below.
Retell for Slack
Slack app (bot + slash commands) with a companion setup/dashboard web app, distributed via the Slack App Directory.
- Service. This app lets members of your Slack workspace start outbound AI phone calls with a slash command (for example, /retell-call). Call summaries can then be posted to the configured Slack channels. You need your own Retell AI account and API key.
- Bot permissions. The app requests only these five bot token scopes: chat:write, channels:read, channels:join, groups:read, and commands. It does not request message-history scopes or user token scopes.
- Private channels. The bot cannot access a private channel unless a workspace member invites it using /invite @Retell AI.
- Your responsibilities. You are solely responsible for getting the required consent to call or record people reached through this app. You must also follow all applicable telemarketing, robocall, and recording-consent laws.
- For warranty disclaimers, liability limits, and governing law, see the General Terms of Service below.
Retell for Epic
SMART on FHIR EHR Launch web app embedded in Epic Hyperspace: setup wizard + outbound AI calls + clinical note writeback, distributed via Epic App Orchard / Build Apps.
- Service. This app lets authorized Epic users open Retell from a patient chart, place outbound AI phone calls through Retell AI, and write the call results back to Epic as a FHIR clinical note (DocumentReference). You need your own Retell AI account and API key and must authorize access through Epic's SMART on FHIR OAuth flow (EHR Launch from Hyperspace).
- Patient context. When you launch the app from Epic, it receives the current patient id and, when available, the encounter id from the SMART launch token. For outbound calls, you enter the phone number in E.164 format. The app does not automatically dial phone numbers stored in Epic unless you provide them.
- Epic FHIR permissions. The app is registered in Epic Build Apps with DocumentReference.Create (Clinical Notes) (R4) and Binary.Read (Clinical Notes) (R4). OAuth also includes the SMART launch scopes launch, openid, and fhirUser, plus offline_access when persistent access is enabled in Epic. We do not request broad chart-wide read access, such as access to all patient demographics, medications, or results. Access is limited to what is needed for launch context and clinical-note read/write.
- Clinical note writeback. After a Retell call ends, the integration creates a Progress Note-style DocumentReference for the patient and links it to the active encounter from the EHR launch. Writeback only works when the app is launched from an open patient chart with an active encounter. If there is no encounter id, writeback will fail until you launch the app again from the chart.
- Protected health information (PHI). This integration may process PHI, including patient identifiers, call summaries, recordings, and transcripts. Your organization is responsible for making sure the right Epic authorizations, workforce access controls, and patient consents are in place, and for following HIPAA and applicable state and federal healthcare and telephony laws.
- Your responsibilities. You are solely responsible for getting any legally required consent to call or record patients. You must follow applicable telemarketing, robocall, and call-recording rules and make sure your use of Retell AI and related data flows meet your organization's HIPAA obligations, including any required Business Associate Agreement with Retell AI and with us, if applicable.
- Backend Services (optional). Administrators can separately connect Epic Backend Services using a client-credentials JWT for server-to-server FHIR access. This connection uses the scopes you configure when you connect it and is covered by these Terms and our Privacy Policy.
- For warranty disclaimers, liability limits, and governing law, see the General Terms of Service below.
2. Eligibility & Accounts
To use any of these apps, you need an account with the connected platform (Salesforce, Zoho, Airtable, Google, Notion, Slack, or Epic) and your own Retell AI account with a valid API key. You are responsible for keeping your login credentials and API keys confidential.
3. Customer Responsibilities and Acceptable Use
- You must not use these apps to place or record calls, or to process personal data, unless you have the consent required by law. You must also follow all applicable telemarketing, robocall, do-not-call, and call-recording laws in every jurisdiction you call.
- You must not use these apps to harass, deceive, or defraud call recipients, or to send unlawful, infringing, or harmful content.
- You must not try to bypass rate limits or security controls, or access data that your account is not authorized to access in the connected platform.
4. Third-Party Services
These apps rely on Retell AI, the connected platform (Salesforce, Zoho, Airtable, Google, Notion, Slack, or Epic), and our hosting/database provider, which uses a PostgreSQL database. We are not responsible for the availability, accuracy, or actions of those third-party services. Each service is governed by its own terms and privacy policy.
5. Disclaimer of Warranties
These apps are provided "as is" and "as available." To the extent permitted by law, we make no express or implied warranties, including warranties of merchantability, fitness for a particular purpose, or non-infringement. We do not guarantee that call outcomes, transcripts, or AI-generated summaries will be accurate or error-free.
6. Limitation of Liability
To the maximum extent permitted by law, Retell AI is not liable for indirect, incidental, special, consequential, or punitive damages, or for loss of data, revenue, or goodwill, arising from your use of these apps.
7. Data Deletion Requests
You can request deletion of data we hold about your account at any time by emailing integrations@retellai.com. This is in addition to the uninstall option available inside each app. See our Privacy Policy for more details.
8. Changes to These Terms
We may update these Terms of Service from time to time. If we make a material change, we will update the effective date shown at the top of this page.
9. Termination
We may suspend or end access to an app if these Terms are violated or if the connected platform's developer or marketplace policies are violated.
10. Governing Law
These Terms are governed by the laws of [Governing Law / Jurisdiction], without regard to conflict-of-laws principles.
11. Contact
If you have questions about these Terms of Service, contact us at integrations@retellai.com.