Manage Google Local Services Ads conversations

Google Local Services Ads (Google LSA) is available in the Messages workspace when it is enabled for your team and your role can view texts. Initial account connection is coordinated with Avoca. Once an account is available in the dashboard, use the customer-facing Google LSA tabs to manage it; there is no generic self-service connection procedure that applies to every account.

​

Conversations

Use Conversations to review inbound customer messages and their current handling state. Before replying manually, check whether AI responses are enabled for the account and whether another teammate is already handling the conversation. Use the conversation details to verify the customer, account, status, and message history. Respect the displayed opt-out state and do not continue messaging a customer who has opted out.

​

Configure the Google LSA message agent

Open Settings → Agents → Messages and select the Google LSA agent for the account. Depending on the agent and rollout, its customer-facing controls can include:

• Enabling or disabling AI responses
• Assistant and response configuration
• Customer contact details such as a phone number or booking link
• Follow-up nudges and their timing
• ServiceTitan campaign and tag attribution

Enable AI responses only after the account-specific business information, escalation behavior, booking behavior, and attribution have been reviewed. The channel’s Messages → Google LSA → Settings page is a separate generic settings surface. Some tabs there are rollout or administrative placeholders; use the message-agent editor for the account-specific behavior above.

​

Notifications and Opt-Outs

The Google LSA Notifications tab is a legacy, read-only summary. Configure escalation recipients under Settings → Business Info → Team Alerts → Google LSA. This is separate from the dashboard-wide Email Notifications page. Opt-Outs lists customers who opted out of text messages. Removing an opt-out re-enables messaging, so do it only when the customer has validly asked to opt back in and your organization has documented that consent.

​

Lead Source and Reporting

Lead Source provides general information about the Google LSA connection. Account provisioning and connection verification are coordinated with Avoca; the informational card is not proof that a specific account is connected. Reporting appears separately when Google Ads Reporting is enabled. It shows available account- and campaign-level Google Ads performance; it is not required to manage conversations.

​

Go-live check

1. Confirm the correct Google LSA account is connected.
2. Review the account’s message-agent AI, contact, nudge, and attribution settings.
3. Confirm Google LSA escalation recipients under Team Alerts.
4. Verify opt-out handling.
5. Test an approved customer journey with Avoca before enabling AI responses broadly.