Lead Docket Integration

Overview

The Lead Docket integration pushes each new lead created by Eve's voice agent into LeadDocket as a new opportunity.

It exists so an intake team working in LeadDocket gets every voice-agent lead where they already are, without opening Eve to find out one came in.

What Gets Sent, and When

• What. One new LeadDocket opportunity per new voice-agent lead. Leads and calls created by a phone system integration are not sent.

• When. Automatically, before the warm transfer where there is one, otherwise shortly after the call ends.

• Fields. Five: First, Last, Email where one was captured, Phone, and a Summary carrying the lead score, a short summary, and a link back to Eve.

A lead signed through the voice agent during the live call has its Summary begin with Lead signed via Eve voice agent. That covers a signature captured during the call, not one that happens afterwards.

One Lead Integration at a Time

Only one lead management integration can be active on an account. LeadDocket cannot run alongside Clio Grow or another lead destination, so the choice is which system the intake team actually works in.

What This Integration Does Not Do

• It creates, it does not update. Each lead is pushed once. An existing opportunity is never modified by Eve afterwards.

• The fields are fixed. What Eve sends cannot be configured or extended.

• It does not cover phone system leads. Only the voice agent feeds it.

• Nothing comes back. Status changes and staff work in LeadDocket are invisible to Eve.

Key Terms

• Opportunity: The lead record Eve creates in LeadDocket.

• Integration URL: The LeadDocket JSON POST endpoint, including an API key, that Eve posts new opportunities to.

• Warm transfer: A live handoff of the caller from the voice agent to a person, which is the point the lead is sent.