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

# DP360

> ADF email forwarding with the vendor ID prefix DP360 needs.

Use this if DP360 is your CRM. If your CRM takes standard ADF/XML by email without a special subject prefix, use [generic ADF](/sales-agent/integrations/overview) instead.

DP360 expects leads by email with a specific subject-line prefix so it can route them to the right tenant. That is the only meaningful difference from generic ADF.

## Set it up

<Steps>
  <Step title="Open the DP360 sub-page">
    **Resource settings → Integrations → CRM → DP360**.
  </Step>

  <Step title="Enter your vendor ID">
    The identifier DP360 gave your dealership. **Required.** It becomes the email subject prefix DP360 uses for tenant routing.
  </Step>

  <Step title="Add destinations">
    Click **Add destination** and enter the address DP360 leads should go to. Add more if several addresses should receive each lead.
  </Step>

  <Step title="Save">
    Ekho starts sending ADF/XML prefixed with your vendor ID on the next qualifying lead.
  </Step>
</Steps>

<Warning>
  A wrong or missing vendor ID means DP360 receives the email but cannot route it, so leads silently fail to appear. If leads are not showing up, check this first.
</Warning>

## Update or remove

* **Update** — return to the DP360 sub-page, edit the vendor ID or destinations, and save.
* **Remove** — click **Remove**. Other configured vendors keep receiving leads.