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

# Getting help

> How to reach the Alli team for questions, changes to your account and anything that does not look right.

A real person on the Alli team reads every message. Reach us whichever way is easiest.

## From your dashboard

1. Select **Support** in the bottom right corner of any page.
2. Enter your first and last name, and tell us what you need help with.
3. Select **Send ticket**.

We already know the email you signed in with, so you do not need to type it.

## By email

Write to [support@carroll.media](mailto:support@carroll.media).

## What to contact us about

The Alli team takes care of these for you:

* Adding or removing a teammate's access
* Changing what Alli says on your calls, such as your hours, services or transfer number
* Changing where call summary emails go
* Connecting a marketing source that is dimmed in Dashboards
* Adding AI Lead Detection or another Alli product
* A call, lead or number that does not look right

## Help us find the problem

Include your business name, the page you are looking at and what you expected to see. Add the exact message shown on screen, if there is one.

* **A call or recording:** caller number, number dialed, approximate date and time with time zone, and the point in the recording involved.
* **A missing or incorrect lead:** Voice or Web, selected date range, the lead's name or contact detail and what appears wrong.
* **A dashboard number:** tab name, date range, the number you see and what you are comparing it with.
* **A connection that stopped working:** the tools involved, the last time it worked and one example that did not arrive.

For an empty list or missing result, the [troubleshooting guide](/troubleshooting) has quick checks you can do first.

## Change how Alli handles calls

Tell us which business or phone line the change applies to, the change you want and when it should take effect. Useful examples include:

* Updated hours, including the time zone and holiday dates
* A new service, price or answer to a common customer question
* A transfer destination and what should happen if nobody answers
* A new address for call summary emails

If a call prompted the change, include its date, time and caller number. A concrete example helps us understand the result you want.

## Website lead detection

For a new website, a redesign or a site that stopped showing leads, send:

1. Your live website address and business name.
2. Your website platform, such as WordPress, Shopify, Wix or Webflow, and whether your team uses Google Tag Manager.
3. What changed and when, if the connection was previously working.
4. The person who manages the website and can help with any installation changes.

The team will check your account's setup and coordinate any site-specific instructions. Use the code and instructions supplied for your business; an example script from an older guide is not your account's installation code.

You can check whether Web leads are available in **Leads > Web**. See [AI Lead Detection](/ai-lead-detection) and [Troubleshooting](/troubleshooting#web-says-not-connected-yet).

## Connections and integrations

Tell us the name of the CRM, calendar, spreadsheet or other tool you want to connect, and describe the outcome you need. For example: where a new lead should appear, which calendar should receive bookings, or which team should receive a notification.

Include whether this is a new connection or a change to an existing one. For an existing connection, add a specific example and the last time it worked. The team can confirm what is available for your account and the setup required.

For a lead export, include the source (**Voice** or **Web**), date range, fields you need and preferred file format so the team can confirm the available option.

## Account or billing changes

See [Account and billing questions](/account-and-billing) for teammate access, service changes, invoices and cancellation requests.


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