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

# Set up Elevate

> Create your company's Elevate API credentials, enter them in Slant, and connect each advisor through OAuth.

Connect Elevate to sync calls, available recordings, voicemail, and read-only SMS history with your Slant books.

Your company completes credential setup once. Each advisor then signs in to Elevate to connect their own identity to a book.

## Before you start

You need:

* An existing Elevate business account and an Elevate login for each advisor who will connect.
* An Elevate account owner or technical administrator with permission to manage **Elevate API access**.
* A Slant user with permission to manage integrations for the company setup step.
* Slant's redirect URL: `https://slant.app/settings/oauth`. Register this URL in Elevate; Slant supplies it automatically when each advisor connects.

Enable recording, voicemail, and texting in Elevate for the features you want to sync. Slant can import only history and media that Elevate makes available.

If you need an Elevate account for testing, contact your Elevate reseller or [Intermedia sales](https://www.intermedia.com/contact-sales). Ask about API access and test users; these instructions do not require a separate developer account for each advisor.

## Create your company's credentials in Elevate

Use your company's Elevate account for both registrations below. You are registering Slant's access, not building an application yourself.

Follow Elevate's [API access instructions](https://support.serverdata.net/app/articles/detail/a_id/23712) alongside these steps.

<Steps>
  <Step title="Open Elevate API access">
    Sign in to your company's Elevate Control Panel using the address supplied by your provider. Go to **Elevate** → **Apps & Integrations** → **Elevate API access**.
  </Step>

  <Step title="Create a service account">
    Under **Service Accounts**, click **Add Account**. Enter a descriptive name, such as **Slant history sync**, then click **Next**.

    Save the generated **Client ID** and **Secret Key** securely. These become **Service client ID** and **Service client secret** in Slant. Elevate shows the service account's secret only when it is created.
  </Step>

  <Step title="Register a confidential OAuth client">
    Under **OAuth Client IDs**, click **Add Client ID**. Enter a name, such as **Slant**, and enter `https://slant.app/settings/oauth` as the **Redirect URI**.

    Choose **Confidential** as the client type, then click **Next**. Save this client's ID and secret separately from the service account credentials. These become **Confidential OAuth client ID** and **OAuth client secret** in Slant.
  </Step>
</Steps>

You now have two credential pairs: one for company API access and one for individual user authorization.

<Note>
  Service credentials grant broad access to your company's Elevate data. Enter secrets directly into Slant; do not include them in support tickets or email. Create dedicated credentials for Slant without deleting or resetting existing Elevate Archiving credentials.
</Note>

## Enter the credentials in Slant

Go to **Settings** → **Phone and SMS**. Under **Elevate**, click **Set up company account** and complete these fields:

| Slant field | What to enter |
| - | - |
| **Service client ID** | The **Client ID** from the service account you created. |
| **Service client secret** | The **Secret Key** from that same service account. |
| **Confidential OAuth client ID** | The client ID from the **Confidential** OAuth client you registered. |
| **OAuth client secret** | The secret belonging to that confidential OAuth client. |

Click **Verify account**. Successful verification closes the form and shows **Company access connected** on the Elevate card.

This verifies company service access. Each advisor must still complete OAuth authorization. Company setup alone does not connect employees or import their history.

<Note>
  You do not supply a webhook URL or webhook secret in this form. Slant manages webhook registration and authentication. Your personal Elevate password is entered only on Elevate's sign-in page.
</Note>

## Connect each advisor to a book

<Steps>
  <Step title="Choose your destination book">
    Select the Slant book where you want your Elevate history to appear, then go to **Settings** → **Phone and SMS**.
  </Step>

  <Step title="Authorize your Elevate account">
    Under the company account, click **Connect my Elevate account**. Sign in with your own Elevate user from that company and authorize Slant.

    After Elevate returns you to Slant, your connection shows **User authorized** and the history sync status.
  </Step>

  <Step title="Choose your calling settings">
    Open **Calling settings**, choose your **Calling device** and **Outbound caller ID**, then click **Save**.

    Caller ID applies across your Slant books and Elevate apps. Only the connected owner can change these settings or place calls using this identity.
  </Step>
</Steps>

Each advisor repeats these steps with their own login. To connect your identity to another book, repeat the connection there using the existing company configuration.

Calls and messages appear when the external phone number matches a contact in the destination book. Other book members can read imported history.

To check the connection, complete a call with someone whose number is saved in that book, then open their record's **Phone** tab. History sync runs in the background; recordings can arrive later.

When you start a call from Slant, **Call requested** means Elevate accepted the request. It does not confirm that the call connected.

<Note>
  Elevate SMS history is read-only in Slant. Send texts from Elevate; Slant does not offer Elevate SMS composing, sender defaults, outbound SMS automations, or sequence sending. Image MMS appears only when Slant can retrieve the attachment.
</Note>

## Troubleshoot setup

<AccordionGroup>
  <Accordion title="Why can't I see Elevate API access?">
    Ask your Elevate account owner or technical administrator to complete the registration. Elevate limits this page to administrators with the required product permissions. Your Elevate provider can help if API access is unavailable.
  </Accordion>

  <Accordion title="Why does company verification fail?">
    Check that the service client ID and secret belong to the same service account. Do not use the OAuth client's credentials in the service fields. Confirm the credentials have not been reset or removed in Elevate.
  </Accordion>

  <Accordion title="Why does user authorization fail after company verification succeeds?">
    Confirm that the OAuth client is **Confidential**, its ID and secret match, and its registered redirect URI is exactly `https://slant.app/settings/oauth`. Sign in as an Elevate user belonging to the configured company. Company verification checks service access; it does not prove that OAuth registration is correct.
  </Accordion>

  <Accordion title="How do I update a secret?">
    A Slant integration manager can select **Update credentials** on the company account. Enter the replacement secret and click **Verify account**; leave unchanged credential fields blank to keep their saved values. If you replace a client registration after users have connected, create a separate company configuration in Slant.
  </Accordion>

  <Accordion title="Does every advisor need API credentials?">
    No. Your company integration manager supplies the two credential pairs once. Advisors use **Connect my Elevate account** and sign in through OAuth.
  </Accordion>

  <Accordion title="What happens when I disconnect a book?">
    Imported history remains visible, and connections to other books continue working. The disconnected book stops syncing new activity. See [Phone and SMS](/setting-up-slant/integrations/phone) for connection and history controls.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.