> ## 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.

# Set up lead email forwarding

> Forward lead alerts into Avoca, confirm source attribution, and validate the first outreach journey.

Email forwarding is a common Speed-to-Lead ingestion method. The lead provider continues sending its normal alert email; a forwarding rule sends a copy to the unique Avoca lead inbox shown for the source.

<Info>
  Avoca does not need access to your entire mailbox. It receives only the messages forwarded to the generated lead inbox.
</Info>

## Get the Avoca lead inbox

1. Open **Products → Speed-to-Lead → Settings**.
2. Select the lead source.
3. Open **Leads Ingestion**.
4. Choose email forwarding when it is offered.
5. Copy the generated Avoca lead inbox address.

Use the address for that source only. Reusing one source's inbox for another source can produce incorrect attribution or parsing.

## Choose the forwarding point

### Forward directly from the lead provider

Create a rule in the mailbox that receives the provider's alert emails. Match the provider's sender and a stable subject or message pattern, then forward matching alerts to Avoca.

This is usually the best option when the original provider email contains the customer's name, phone number, request, location, and source identifier.

### Forward a supported CRM lead alert

If the lead first enters the CRM, use the supported alert or booking-notification email selected during implementation. Confirm that the email contains the fields Avoca needs and that the rule excludes unrelated CRM notifications.

<Warning>
  Do not forward an entire inbox. A broad rule can send customer data and unrelated business email to the wrong workflow.
</Warning>

## Test the rule

1. Submit a controlled test lead through the real source.
2. Confirm that the original alert reaches the expected mailbox.
3. Confirm that the forwarding rule sends it to the generated Avoca address.
4. Open **Speed-to-Lead → Leads** and find the test record.
5. Verify the customer phone number, source, received time, service area, and request details.
6. Confirm that the expected campaign and workflow appear in the Lead Journey.
7. Verify the first contact only after the source's outreach setting is intentionally enabled.

## Use multiple lead sources

Each source can have its own generated inbox, parsing behavior, campaign, CRM mappings, and phone-number mappings. Create and test the sources independently.

Do not combine multiple providers under one generic mailbox rule unless Avoca has configured a reliable way to distinguish them.

## Troubleshoot a missing lead

Check in this order:

1. Did the provider send the alert?
2. Did the source mailbox receive it?
3. Did the forwarding rule match it?
4. Was it forwarded to the exact Avoca address?
5. Did the email format change?
6. Does the record appear under another or uncategorized source?
7. Is the record present but marked **Not Contacted** because a phone number, campaign, mapping, or eligibility check is missing?

When escalating, provide the Avoca team, lead source, test time, and the subject line of the test alert. Do not include mailbox credentials.