LEX Reception picks up when you can't. Your ads never find out which of those callers hired you.
Your phone rings first, then rolls to a LEX receptionist, who runs your intake script and logs the inquiry in Clio, MyCase or Filevine. Google Ads only sees a call that lasted long enough, and the Clio record shows the inquiry but not the ad. We tag each call before it forwards, put the campaign on every LEX intake, and send signed retainers back to Google Ads and Meta.
Free30 minutesNo obligation
LEX Reception · what breaks
What goes wrong when LEX Reception answers your ad calls
- 01
"Google Ads counts every call LEX picks up, my current clients included"
Google counts any call past the minimum length you set. A client asking about their court date clears it just as easily as a new injury case, so bidding buys more of the wrong calls, and LEX bills each one by the minute, rounded up.
- 02
"The Clio entry has the inquiry but not the ad"
LEX documents that the Clio sync carries name, contact details, the nature of the inquiry, case notes and documents. Nothing about campaign or click ID, so a signed DUI or immigration matter can't be traced to what you paid for it.
- 03
"Website chats book consults, but Meta never hears about it"
The LEX chatbox installs with one line of code and is staffed by real receptionists. LEX lists its own visitor history but no Google Analytics or Meta Pixel option, so a chat that becomes a consultation teaches your ads nothing.
- 04
"Some ad calls skip our tracking numbers entirely"
Every LEX plan includes a dedicated business phone number, and the LEX app calls and texts clients from it. If that number ends up on a landing page or your Google profile, those calls never pass through a tracking number, so no click ID is ever attached and the ads that produced them go uncredited.
LEX Reception · the fix
What changes after we fix it — LEX Reception
Only new-matter intakes count as leads
The lead conversion fires from the LEX intake once it lands in your case management system, so status calls, court clerks and vendor pitches stop teaching Google Ads what a lead is.
Each LEX intake carries its campaign
We match the caller's number on the LEX message to the tracked call that holds the click ID, so the Clio or MyCase record shows campaign and keyword next to the case notes.
Retainers train bidding, not answered minutes
Qualified matters and signed retainers go to Google Ads and Meta from your records, so a personal injury or employment firm bids toward clients who sign, not callers who talked longest.
LEX Reception · architecture
What LEX Reception actually lets you hook into
LEX answers calls and chats with live human receptionists, no AI, and moves intake into your software. It reports nothing to ad platforms. Here's what its own pages document.
- 1
Carrier call forwarding
Forward-all, busy, no-answer or scheduled forwarding to your dedicated LEX number; LEX recommends forwarding when unanswered. Call tracking sits in front of that hop.
- 2
Inbox, recordings and live transfer
Messages land in the LEX app inbox with call recordings, and live call transfer comes with every plan. Transcription is a $30 monthly add-on.
- 3
Case management and CRM integrations
Clio, MyCase, Filevine, Lawmatics, Smokeball, CASEpeer, CloudLex and PracticePanther, plus HubSpot, Salesforce and Keap. Messages can become leads, cases or tasks by your rules. No lead source field is documented.
- 4
Zapier
One trigger, New Message, and one action, Create Contact. We check which message fields the trigger passes before building on it.
- 5
Live chat and Setmore
A one-line chat install and Setmore scheduling (Setmore Pro, per LEX's homepage) come with every plan, and receptionists book consults into your Setmore slots. No GA4, GTM or Meta Pixel setting is documented for either.
- 6
No Google Ads, GA4, Meta or webhook connection documented
Outcomes go back from your case records through a first-party container instead.
LEX Reception · diagnose
Where LEX Reception tracking breaks, in diagnostic order
Start with the phone chain, because a call that reaches LEX without its ad source can't be fixed later in Clio.
- 01
Check which number your ads and pages show
A tracking number, your office line or the LEX business number. Only the first carries a click.
- 02
Place a test call from an ad-tagged visit
Let it ring out to LEX, then confirm the click was logged and the LEX message shows the caller's real number.
- 03
Review the Google Ads call conversion setting
Counting every call past a set length means counting current clients and court calls LEX answers for you.
- 04
Open the intake in Clio or MyCase
Look for campaign or click ID on the record. Out of the box there won't be one.
- 05
Run a chat and a live transfer
Confirm a chat intake is labeled as chat and a transferred caller still leaves a record with a source.
- 06
Compare signed retainers with reported conversions
Client by client, over a closed month.
LEX Reception · prove
The QA evidence — LEX Reception
Run on live calls to your real tracked numbers, answered by LEX receptionists on your actual script, not on a test line.
Source of truth
LEX Reception messages and call recordings, the intakes it created in Clio, MyCase or your CRM, and the retainers you signed
- A test call from an ad click, with its click ID on the matching Clio or MyCase record.
- A live chat intake labeled as web chat, not phone.
- Existing-client, court and vendor calls absent from the lead conversion.
- A live-transferred caller confirmed as a lead with its source.
- Signed retainers reconciled one by one against Google Ads and Meta over a closed month.
- Repeated a month later, and again whenever forwarding, phone carrier or the LEX script changes.
LEX Reception · free audit
What we check in the free audit
- Check which number your ads and pages show
- Place a test call from an ad-tagged visit
- Review the Google Ads call conversion setting
- Open the intake in Clio or MyCase
- Run a chat and a live transfer
- Compare signed retainers with reported conversions
Checked against
LEX Reception messages and call recordings, the intakes it created in Clio, MyCase or your CRM, and the retainers you signed
Free30 minutesNo obligation
LEX Reception · when not to buy
When you don't need this with LEX Reception
Plenty of firms using LEX have nothing to fix on the ads side.
- If clients come from referrals and organic search and you run no paid ads, LEX's inbox and Clio sync already cover you.
- If Local Services Ads is your only paid channel, Google's lead dashboard is the report; LEX answers those calls, but there's no ad click to match.
- If one small campaign brings a few calls a month, reading each LEX message by hand beats a build.
- If call tracking already writes click IDs onto your intakes and signed matters already reach Google Ads, you need a short check, not a project.
LEX Reception · what we deliver
The event map on LEX Reception
Call to the tracked ad number
Logged by call tracking before your phone rolls to LEX, with click ID, campaign and keyword.
Live chat started
Recorded only if the LEX chatbox exposes an event your site tag can read, which we test first. A diagnostic signal, never a bidding target.
New-client intake taken
A prospective client's message or chat intake. Existing clients, courts, opposing counsel, vendors and solicitations excluded.
Qualified matter
Set in Clio, MyCase or your CRM when practice area, jurisdiction and facts fit the cases you take.
Consultation booked
Including consults LEX receptionists put into Setmore, and paid consultations collected through LawPay where you use it.
Retainer signed
The bidding target, valued from your fee agreement or an agreed case value and sent server-side.
Written guarantee
95%+ tracking accuracy
Measured against LEX Reception messages and call recordings, the intakes it created in Clio, MyCase or your CRM, and the retainers you signed. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
LEX Reception questions, answered
Not according to its own pages. LEX connects to legal case management tools, CRMs, Setmore and Zapier, so conversions reach Google Ads and Meta from your case records instead.
They shouldn't: the tracking number rings your office line, which forwards unanswered calls to LEX as before. We still place a live call through your setup and confirm the receptionist sees the real caller number.
Not on its own. The documented Clio sync covers name, contact details, inquiry, case notes and documents, so we match the caller's number to the tracked call and write the campaign onto the record.
LEX documents no Google Analytics or Pixel option for its chatbox. We test what a site tag can read, and chat intakes get their own label in your CRM either way.
Drop call length as the conversion. Count the new-client intake, then the qualified matter and signed retainer from Clio or MyCase.
No. LEX keeps answering and running intake; tracking sits in front of the forward and behind your case management system.
More on LEX Reception
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
RELATED GUIDES
Booking tools beside LEX Reception, and what their bookings feed
- Alert CommunicationsAlert Communications signs the retainer. Your ads never hear about it.
- Smith.aiSmith.ai picks up every call. Your ads still can't tell which ones became clients.
- PATLivePATLive answers every call. Your ads still can't tell which ones paid off.
- BlazeoBlazeo sends you the chat leads. Google and Meta still can't tell which ad sent them.
- Ngage Live ChatNgage Live Chat conversion tracking: see which ads start the chats that sign
- Answering LegalAnswering Legal takes your ad calls. Your ads still can't tell which ones signed.
- Avoca AIAvoca AI books the job. Your ads never hear about it.
- HyroHyro books the appointment. Your ads never find out.
Free · 30 min
Find out which ads send LEX Reception your signed clients
Free30 minutesNo obligation
