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

# Configure Speed-to-Lead sources

> Connect a lead source, assign its workflow and mappings, and take it live.

Open **Products → Speed-to-Lead → Settings** to manage lead sources. Each source shows its connection and outreach status.

## Understand source status

* **Live:** the source is connected, outreach is enabled, and it has an active campaign.
* **Fallback:** the source is connected and eligible leads use the team's fallback campaign.
* **Not contacting:** leads can arrive, but no active campaign or live fallback will contact them.
* **Outreach off:** ingestion can continue, but Avoca does not start outreach for the source.
* **Start:** the source has not completed setup.

The page-level **Live** control manages outreach across standard sources. Use it deliberately: turning outreach off does not necessarily disconnect ingestion.

## Configure a standard source

1. Select the source from the Settings list.
2. On **Leads Ingestion**, choose an offered method such as email alerts or webhook delivery and follow the generated setup instructions.
3. Send a sample lead and confirm that Avoca attributes it to the intended source.
4. On **Workflow**, select a published Speed-to-Lead workflow.
5. On **Mappings**, assign the correct phone number for every service area. If your CRM is connected, also review the CRM campaign and job tags.
6. On **Launch**, enter the campaign name and resolve every incomplete checklist item.
7. Select **Go live**.
8. Return to the source list and verify that its status is **Live**.

Some directly connected channels use a guided agent configuration instead of the standard workflow-and-mapping steps. If Avoca provisions the connection, complete the customer-facing agent settings shown after the account is connected.

## Configure webhook ingestion

The ingestion step shows the team-wide webhook endpoint and API key. Open **Speed-to-Lead → Webhooks** to:

* Route incoming payloads to the correct source
* Map source fields to Avoca lead fields
* Review delivery logs
* Send a test payload

Without a matching source-routing rule, Avoca may rely on source fields in the payload or classify the lead as uncategorized.

## Use the fallback campaign

Fallback can catch eligible leads from connected sources that do not yet have their own active campaign. It is useful during setup, but it should not hide unfinished source configuration.

<Warning>
  A connected source with **Not contacting** status can ingest real leads without contacting them. Resolve it before relying on Speed-to-Lead for production response.
</Warning>

After launch, send one controlled lead and verify ingestion, source attribution, campaign entry, first contact, and lead journey before increasing volume.