Connect native lead sources

Some Speed-to-Lead sources connect directly to Avoca instead of using a generic forwarded email or team webhook. Current guided onboarding can include Google Local Services Ads (GLSA), Yelp, and Angi when enabled for the team.

​

How native sources differ

A native source can provide:

• Direct source attribution
• Provider-specific lead fields
• Provider conversation or response handling
• A source-specific assistant or objective
• Provider-specific notification and opt-out controls
• Health or connection status

It still needs a complete outreach path, but the path varies:

• Google LSA and Yelp can use guided, account-level AI response settings or an account-level native messaging workflow.
• Standard lead-source integrations, including an Angi lead webhook, use the regular ingestion, workflow, mapping, and launch path when those steps appear.

A connected provider does not automatically mean that customer responses are live. For Google LSA and Yelp, three controls cover different parts of the lifecycle:

• Source Outreach controls the first Avoca message to a new lead.
• Account AI Replies controls replies after a provider conversation has started.
• A launched workflow campaign controls proactive follow-up for that account.

Turning off one control does not automatically turn off the other two. Review both the source row and each connected account before concluding that the channel is silent.

​

Prepare the provider account

Before setup:

1. Confirm the exact provider account or business location.
2. Identify an administrator who can approve access.
3. Confirm which locations, categories, or lead types Avoca should handle.
4. Review the customer-facing business name and response expectations.
5. Decide who owns the provider response and which guided agent or workflow path the dashboard should use.

Never send provider passwords through a support ticket or help-center form. Use the authorization flow or secure credential process shown by Avoca.

​

Complete the Avoca setup

1. Open Products → Speed-to-Lead → Settings.
2. Select the provider source.
3. Complete the account connection or invitation.
4. Follow the setup path shown for that source:
   • Guided native agent: configure the objective, AI responses, escalation, and other account-level behavior shown for every Google LSA or Yelp account. This path does not require a campaign or service-area phone mapping unless the dashboard presents one.
   • Native workflow: select a published native messaging workflow for each Google LSA or Yelp account you are ready to configure, add the optional CRM campaign or tag mappings shown, then complete Launch. You can launch one ready account and return for the remaining accounts later.
   • Standard lead source: complete Leads Ingestion, select a published workflow, configure required service-area, phone-number, CRM campaign, or tag mappings, then complete Launch.
5. Send a provider-side test lead or inquiry.
6. Verify the source and customer details in the corresponding native conversation for Google LSA or Yelp, or in Lead Journey for a standard lead source.
7. Confirm the intended first response and downstream CRM result.
8. Enable production outreach or AI responses only after the path shown for that source passes.

In a multi-account workflow setup, Go live creates campaigns only for accounts that have a changed, published workflow selection. An account with AI replies on but no launched workflow shows Fallback: it can reply to inbound provider messages, but it has no proactive follow-up sequence. The source-wide row can still show Live when another account is live, so review any account needs setup note.

​

Provider-specific checks

​

Google Local Services Ads

• Confirm the intended Google Ads or Local Services account and locations.
• Make sure the account invitation or authorization is accepted by the correct administrator.
• Verify lead notification settings and the source connection before enabling Avoca outreach.
• Compare one GLSA lead in Google with the corresponding Avoca Lead Journey.

​

Yelp

• Confirm the correct Yelp Business account and locations.
• Review the Yelp objective and the responses Avoca is permitted to send.
• Verify a real test inquiry is attributed to Yelp and does not enter a generic source.

​

Angi

• Confirm the Angi or HomeAdvisor account and routing details requested during setup.
• Verify the direct webhook or native connection status.
• Test the lead type and location combinations the business actually receives.

​

Separate source health from outreach health

When a lead does not receive outreach, determine which layer failed:

• Provider: no lead was created or delivered
• Connection: Avoca did not receive it
• Attribution: Avoca received it under the wrong source
• Eligibility: the lead was duplicate, excluded, missing a phone number, or outside the intended mapping
• Guided agent: for guided Google LSA or Yelp, the account is disconnected, AI responses are off, or the account-level agent or escalation settings do not cover the inquiry
• Campaign: for campaign-backed paths, no active source or fallback campaign covered it
• Workflow: for native-workflow and standard paths, the workflow was unpublished, paused, outside execution hours, or failed
• Channel: the phone number or messaging configuration was unavailable

Start with the source settings and the provider or native conversation. For a guided path, inspect the channel account’s connection, AI response, and escalation settings. For a campaign-backed path, add the Lead Journey, campaign and workflow state, and webhook or email logs. Reprocessing a real lead can contact the customer again, so resolve the cause before retrying.