Open Products → Speed-to-Lead → Settings to manage lead sources. Each source shows its connection and outreach status.
Understand source status
- Live: at least one configured contact path is active. A standard source normally has its own live campaign. A classic Google LSA or Yelp account is Live when AI replies are enabled; a workflow-managed account is Live when AI replies are enabled and its workflow campaign is active.
- Fallback: a standard source is covered by the team’s fallback campaign, or a workflow-managed Google LSA or Yelp account can reply to inbound conversations but has no proactive workflow campaign yet.
- Not contacting: the source or account lacks the contact path required for its setup. For Google LSA and Yelp, this can mean that AI replies are off even when a workflow exists.
- Outreach off: ingestion can continue, but Avoca does not make the first contact with a new lead from this source. An already-started native conversation can continue when that account’s AI replies remain enabled.
- Start: the source has not completed setup.
For a Google LSA or Yelp source with several accounts, the row shows the strongest current account status and adds an account needs setup note when another account is not in that state. Review the individual accounts before treating the source-wide badge as complete.
The page-level Live control manages source outreach. Use it deliberately: turning outreach off does not disconnect ingestion, and native account AI-reply controls remain separate.
- Select the source from the Settings list.
- On Leads Ingestion, choose the offered method and follow the generated setup instructions. See email forwarding and native sources.
- Send a sample lead and confirm that Avoca attributes it to the intended source.
- On Workflow, select a published Speed-to-Lead workflow.
- On Mappings, assign the correct phone number for every service area. If your CRM is connected, also review the CRM campaign and job tags.
- On Launch, enter the campaign name and resolve every incomplete checklist item.
- Select Go live.
- 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.
New sources begin with outreach off. Keep them that way until ingestion, attribution, workflow selection, mappings, and the intended first response have passed a controlled test.
Change the customer-facing source name
To rename what customers and dashboard users see without changing ingestion, open the source, go to Launch, expand Advanced settings, and edit Display name.
The display name labels the source in the dashboard and analytics and fills the {{lead_source}} variable in outbound calls, texts, emails, direct mail, and human-callback steps for leads enrolled after the change. It does not change the source’s underlying ingestion key. Leave it blank to use the original lead-source name.
A display-name change can alter live customer-facing workflow copy. Preview every published workflow that uses {{lead_source}}, then send a controlled lead and confirm the rendered wording before relying on the new name.
- Confirm with your Avoca contact that the underlying product or connection is enabled.
- Select Mark as configured, or Reconnect when the existing source was disconnected.
- Continue to Workflow and choose a published Speed-to-Lead workflow.
- Complete the mappings and launch checks shown for the source.
- Send a controlled event from the originating product and confirm source attribution, campaign entry, and first contact.
These sources do not show webhook or email credentials because ingestion is controlled by the originating Avoca product. Marking the row as configured does not turn on Web Chat, Responder follow-up, Genesys, or Simple Scheduler by itself.
Open the source’s actions menu and choose the narrowest action that matches the change:
- Turn off outreach (log only): keeps ingestion available but stops first contact for new leads. It does not necessarily stop replies in native conversations that already started.
- Reconfigure: keeps ingestion on, permanently closes and archives campaigns dedicated only to that source, and reopens setup for a fresh workflow and mappings. A campaign shared with another source stays running. Existing native conversations can continue according to the account’s AI-reply setting, but unsent proactive workflow steps from the closed campaign do not resume.
- Reconfigure using workflows: when offered, makes a one-way move from the classic native setup to workflow-managed outreach. Follow-up behavior must then be represented in the workflow you assign.
- Disconnect source: stops new ingestion and closes campaigns dedicated to the source. For Google LSA or Yelp, it also turns off AI replies and nudges for the connected accounts.
For workflow-managed Google LSA and Yelp sources, reconfiguration is available per account in the Workflows setup step. Reconfiguring one account closes that account’s campaign without disturbing campaigns for the other accounts.
Reconfiguration is not a temporary pause. The closed dedicated campaign cannot be resumed; taking the source live again creates a new campaign for future leads. Read the confirmation dialog and verify the source status after the action, especially if Avoca reports that a campaign could not be stopped.
Keep ingestion methods separate
- Email forwarding receives only provider or CRM alert emails sent to the generated lead inbox.
- Webhooks receive structured payloads at the team endpoint and use routing and field mappings.
- Native sources use a provider-specific account connection and setup.
- CRM polling or alerts use supported records or notifications from the connected CRM.
One lead should normally arrive through one intended path. If two ingestion methods are active for the same provider, test for duplicate records before launch.
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.
JobNimbus contact webhooks can use the standard Speed-to-Lead webhook path. Avoca recognizes common JobNimbus fields such as display_name, mobile_phone, work_phone, address_line1, source_name, and jnid, along with the contact’s email, city, state, ZIP, country, and description.
The payload must include a usable mobile or work phone number. A JobNimbus contact that supplies only home_phone is rejected as missing the required phone number and does not enter outreach. Send a controlled sample contact, then confirm the normalized name, phone, source, external ID, address, and notes before enabling the source.
Keep one intended ingestion path for each JobNimbus lead population. Sending the same contact through both a webhook and an alert email can create duplicate lead journeys.
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.
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.
