What This Update Actually Is
Customer Agent is HubSpot's AI-powered chat agent for customer-facing support. It can call your external APIs to retrieve data like order history, subscription status, or account details, and surface that information directly inside the chat.
Before this update, those API calls went out without a reliable visitor identifier. Your backend had no automatic way to know which visitor it was talking about. That meant extra work: asking the visitor for their email again inside the chat, or building custom middleware to pass identity along.
Now, when a visitor is verified, Customer Agent appends their email as a query parameter called hs_identified_email on every outgoing API request for actions with email protection turned on. For example: https://api.example.com/orders?hs_identified_email=jane@example.com. Your API can then use that as a lookup key and return the right data.
Two protection levels trigger this behavior: Match email and Verify email. Actions set to None are unchanged. If your action already uses a parameter named hs_identified_email, HubSpot won't overwrite it.
Why HubSpot Shipped This
The external problem is straightforward. When an AI agent calls your API to fetch order details or account data, it needs to know who it's fetching data for. Without a verified identifier, you either get generic results or you build a workaround.
The internal frustration is what we see in portals regularly. Humans spend time and budget wiring up middleware layers just to pass a piece of information that HubSpot already has. The chat flow asks a visitor for their email. The visitor has already verified it. Then a separate system has to intercept and relay that same piece of data. That's friction layered on top of friction.
HubSpot shipped this to close that gap cleanly. The verified email is already in HubSpot's possession. Passing it along automatically to your API is a logical, trust-appropriate next step, and it removes an entire category of custom development for most Customer Agent deployments.
How to Use It Step by Step
- Open Customer Agent settings in your HubSpot portal and navigate to the action you want to update.
- Check the protection level on each action. If it's set to Match email or Verify email, the hs_identified_email parameter will now be appended automatically. No toggle to flip.
- Review your API endpoint to make sure it can either accept the hs_identified_email parameter as a lookup key or gracefully ignore it if you don't need it right now.
- Update your backend logic to use hs_identified_email as the lookup key where relevant. For example, query your orders table by email and return only that visitor's records.
- Test with a verified visitor session to confirm the parameter is arriving and your API is returning the right scoped data.
- Remove any middleware you built specifically to pass visitor identity from HubSpot chat to your API. That layer is now redundant for verified actions.
What It Touches in Your HubSpot Strategy
This update sits at the intersection of Service Hub and your broader RevOps data architecture. It's not just a chat feature. It's a data-flow change that affects how your systems communicate with HubSpot's AI layer.
On the service side, Customer Agent actions that retrieve personalized data (orders, subscriptions, support history, account tiers) now work without a secondary verification prompt. That's a meaningfully cleaner experience for the humans visiting your site.
Key Takeaway
Any Customer Agent action with Match email or Verify email protection now passes hs_identified_email automatically. If you've built middleware to do this manually, you can retire that code and reduce your maintenance surface.
On the RevOps side, this reinforces why clean contact identity data matters so much. The verified email only flows through reliably when your HubSpot contact records are accurate and your verification flows are properly configured. Gaps in your CRM data hygiene will surface here as mismatches or empty lookups.
This also connects directly to how HubSpot handles API authentication and permission scoping. If you've been watching the
This also connects directly to how HubSpot handles API authentication and permission scoping. If you've been watching the evolution of HubSpot's granular OAuth scopes and self-service migration tooling, you'll recognize the pattern: HubSpot is tightening the trust model across its API surface. Verified identity flowing into API calls is part of that same direction.
On the integration side, review any tools connecting to HubSpot via Customer Agent actions. Make sure those endpoints are ready to receive or ignore the new parameter. Most REST APIs handle unknown query parameters gracefully, but it's worth a quick check before you assume everything is fine.
Key Takeaway
Clean contact identity in your CRM is now a direct dependency of Customer Agent's ability to return accurate, personalized data. This is a good moment to audit your verification flows and contact deduplication practices.
There's a bigger strategic point here worth naming. Humans don't want to feel personalized at. They want to feel known. We've written about this idea at length in why your B2B customers want to feel known, not just personalized. Customer Agent pulling the right order data without asking for an email again is a small but real moment of being known.
Who Should Care Most
This update matters most to the following roles and company profiles:
- RevOps leaders and HubSpot admins who configured Customer Agent actions with email protection and want to simplify the integration architecture.
- Developers and solutions engineers who built middleware to pass visitor identity from HubSpot chat to external APIs. That custom code is now replaceable.
- E-commerce and SaaS companies on Professional or Enterprise whose Customer Agent fetches order details, subscription info, or account data. The visitor experience improves immediately.
- Service Hub managers who want Customer Agent to feel more intelligent and reduce escalations caused by the agent not having context about who it's talking to.
- Growing companies with lean engineering teams who couldn't justify building a custom identity-passing layer. This gives them the same outcome with zero custom code.
George's Take
“The best AI experiences don't feel like AI at all. They feel like the tool just knew. That's exactly what happens when Customer Agent stops asking for an email it already has. Small change, big shift in trust.”
When I look at portals that have Customer Agent deployed, one of the most common friction points I see is the identity gap between chat and backend systems. Teams either accept that the agent can't fetch personalized data, or they invest engineering hours in a middleware fix. This update removes that choice entirely. What I love about it is that it's quiet. No new settings to learn, no UI overhaul. HubSpot just closed a gap that was costing real time and real trust. If you're on Professional or Enterprise and you haven't evaluated Customer Agent for authenticated support flows yet, this is the update that makes that conversation worth having.
If you want help mapping Customer Agent into your existing support or RevOps workflows, or you're not sure whether your API integrations are ready to handle the new parameter, let's talk. Book a strategy call with the Sidekick team and we'll walk through your portal together.
Frequently Asked Questions
What is the hs_identified_email parameter in HubSpot Customer Agent?
It's a query parameter HubSpot Customer Agent now automatically appends to outgoing API requests when a visitor has been verified. For example: https://api.example.com/orders?hs_identified_email=jane@example.com. Your API can use it as a lookup key to return the correct visitor's data without any additional identity-passing logic.
Do I need to configure anything to enable this feature?
No. If your Customer Agent action already has a protection level of Match email or Verify email, the hs_identified_email parameter is added automatically. The only thing to check is that your API endpoint can accept or gracefully ignore the new parameter. No settings to toggle, no new setup required.
Which Customer Agent protection levels trigger the verified email parameter?
Only actions set to Match email or Verify email will include the hs_identified_email parameter. Actions with a protection level of None are not affected and will continue to behave exactly as they did before this update.
What if my API already uses a parameter called hs_identified_email?
HubSpot won't overwrite it. If your action already includes a parameter with that name, Customer Agent respects the existing value and skips adding its own. This prevents any collision with custom integrations that were built before this update shipped.
Which HubSpot tiers get access to this Customer Agent update?
Customer Agent is available on Professional and Enterprise plans. This verified email parameter behavior ships automatically for any eligible action on those tiers. Starter and Free plan customers don't have access to Customer Agent.
Can I use the verified email to pull personalized data like order history inside a chat?
Yes, that's exactly the intended use case. Once your API receives the hs_identified_email parameter, you can query your database by that email and return the matching records. Customer Agent then surfaces that data in the conversation, giving visitors a personalized, context-aware support experience without re-asking for their email.
