The furnace in a house outside Columbus quits on the first cold night of the year. The owner doesn’t open a browser. They tell their agent: find an HVAC company near us that can come out tomorrow, find out whether it’s worth repairing at its age, and ask the right one to send someone.
Their agent does the research. It reads what a handful of companies publish, asks questions of the sites that can answer them, and makes the request with the one that fits, once the owner says to go ahead.
Now open your analytics for that night. If yours was the company it chose, you will not find this customer there.
What your analytics can count
Web analytics count people in browsers. A page loads, a script runs, and a visit is recorded with where it came from. Your ad pixels fire on the same page loads. Your form tool counts the forms people send.
An agent working from its own servers does none of that. It reads your pages without running your scripts, and if your site offers agents tools, it calls them directly. There is no page view to count and no pixel event to fire. When it makes the request for the person, there is no form fill either.
This is not a tracking gap a better tag will close. There is no browser for the tag to run in.
The request is how you know them
For this customer, the first thing your team sees is the request: the estimate, the service visit, the consultation or the tour their agent asks you for. That makes the request how you know them, and what it carries decides how fast you can act on them.
A request from a contact form carries a name, a phone number and a box that says “furnace broken.” A request made through your Agent Concierge carries what their agent gathered on the way:
- what they need, in their own words: “The furnace quit last night, it’s the one that came with the house, and we have a baby at home.”
- the facts your intake asks for, which tell you whether it’s your kind of job: what the work is, where it is, and how soon they need you;
- how they said yes: on a card in your brand if they were on your page, or through their own agent, with their go-ahead;
- what their agent asked first: whether you service that make, whether you’d repair or replace at that age, whether anyone can come tomorrow;
- a link to replay the conversation, turn by turn, in your dashboard.
It lands in your Leads inbox and in an email that opens with what their agent asked first. Their agent can ask you to call them back, but it can’t sign them up for your marketing. Only the person’s own tick does that.
Act on them faster, and close more of them
Because the facts arrive with the request, your team can act on them before the first call instead of during it.
Route the urgent ones first. A furnace out on a cold night, with a baby in the house, goes to whoever can call back now, not to Monday’s queue. Put the best fits at the top: the replacement you are built for ahead of the job you would rather refer out. Use the rules you already run your business by. The request carries what you need to apply them.
Then make the first call the right one. Whoever calls back already knows what the person needs and what their agent asked before it chose you, so they can open with the answer: yes, at that age we would look at replacing it, and we can be there in the morning. That is a shorter road to a sold job than “so, what seems to be the problem?”, and it is how you close more of the customers their agent sends you.
Their agent does the research. You win the customer.
The research that didn’t become a request
Not every agent’s research ends in a request, just as not every visit ends in a form. The difference is that this research used to be invisible too.
When an agent uses your site’s agent tools (your MCP endpoint, your agent endpoints or the tools on your pages), each visit is recorded in your workspace as one conversation: what it asked, exactly what it was told, whether that was a real answer, and how far it got. Found, understood, chosen, acted, delivered.
So you can see where each one stopped, in words you can act on:
- The agent got real answers and left without acting.
- The agent reached the confirmation step and the person did not say yes.
- A general answer went out for a specific question.
Marketing gets a list it never had: every question agents ask your site, how often, and whether your site had a real answer. Open the ones your site could not answer, and you have a content plan in the words buyers’ agents use. Fix them, starting with the ones asked most.
The honest limits
- The record covers agents that use your site’s agent tools, not every crawler that fetches a page.
- It follows one sitting. Research an agent did on an earlier day arrives as a separate conversation.
- What their agent asked first reaches your inbox and your dashboard, not your CRM.
Where this stands
The request tools, both ways of saying yes, the lead with what their agent asked first, and conversation recording are built and deployed. Recording is on from day one for new workspaces, and we run our own site on it. We do not have a customer’s numbers to show you yet, and we will not invent any.
Want to know what their agent finds when it looks at you? Run the free audit, or book a demo.