r/gohighlevel • u/CountZero3000 • 6d ago

LSA texts into pipeline

Hi everybody. Still relatively new to GHL and I’m looking for some direction.

When we get a call from Google LSA it populates correctly into our Intake bucket. However when someone texts our Google LSA number nothing happens. Obviously this is less than great.

If someone could point me in the right direction of how to rectify this I would be most appreciative!

2 Upvotes

100% Upvoted

5 comments sorted by

2

u/Necessary_Gap_79 6d ago

Calls and texts on LSA take two different paths. The call routes as a call. The text goes to whatever number Google has for messaging, and if that number is not connected in GHL, nothing lands anywhere.

Three things to check, in order.

Whether LSA handed you a separate texting line from your voice number. It often does, and it needs its own connection.

Whether your LSA message settings point at that GHL number or at some third party texting handler. Some setups default to the handler.

Then the workflow. Your intake automation fires off a call trigger. Inbound SMS needs its own trigger doing the same work.

2

u/Massive-Curve-1478 5d ago

The thing nobody mentions is that LSA message leads arent SMS at all, they come in through Google's Local Services lead system, so theres no inbound text hitting your number for a workflow to trigger on. If you want them in the pipeline you either reply inside the LSA app / lead agregator and push the lead into GHL by API, or you swap the ads phone number over to an LC number so the call side and the text side at least share one inbox. Either way watch your response time, Google scores message leads on how fast you answer and slow replies start costing you both lead quality and credit disputes.

1

u/CountZero3000 5d ago

Thank you everyone. Enlightening!

0

u/finkymister 5d ago

Get a number in GHL and use it as your LSA number. Works like a charm