What This Update Actually Is
HubSpot shipped a meaningful expansion to Customer Agent for calling on May 7, 2026. Before this update, your voice agent could answer questions. That was it.
Now it can do three things it couldn't do before. First, it can read contact properties during a live call and share that data with the caller after verifying their identity. Second, it can write back to those same contact properties, updating a billing address or profile field in real time, without a human touching the record. Third, you can now set a custom welcome message and test your voice setup inside an improved agent tester before you go live.
This is still a private beta. Everyone in your account is included, but it requires HubSpot Credits to run. The feature lives under Service > Customer Agent in your portal.
Why HubSpot Shipped This
Voice channels have always been the weak link in automated service. Chatbots got smarter. Email workflows got smarter. But the phone? It stayed stuck in the same old IVR loop, press 1 for billing, press 2 for support, wait on hold, speak to a human.
The internal frustration for service teams is real. Humans who call in for routine updates, like confirming a shipping address or correcting a billing record, still get routed to a live agent. That agent spends two minutes on a task that should take zero minutes of human time. Meanwhile, the caller waits.
HubSpot is building toward a world where agents take real action on behalf of callers, not just talk. This update is a direct step in that direction. It connects the voice channel to the CRM in a way that actually resolves requests, not just deflects them.
How to Use It Step by Step
Follow these steps inside your HubSpot portal to enable property reading and editing for your voice agent:
- Navigate to Service > Customer Agent in your HubSpot account.
- In the left sidebar, click Define, then click Permissions.
- Click Add CRM Data. A right panel opens.
- Use the CRM property dropdown to select the property you want the agent to access (for example, Billing Address or Phone Number).
- Toggle View Property on. This lets the agent read and speak the property value.
- Set a Data Protection Level. For most use cases, choose Match Email or Phone Number. This tells the agent to confirm the caller's identity by matching their inbound number to the contact record before sharing any data.
- In the Instructions field, write plain-language guidance for the agent. Example: "If a customer says they haven't received their bill, share their billing address to confirm it's correct."
- To enable write-back, click Edit Settings. Toggle Edit Property on, configure your data protection level and instructions for edits, then click Save.
- Use the improved agent tester to run a voice simulation before going live. Catch gaps in your instructions here, not in front of a real caller.
One important caveat: each property you expose requires its own verification level and instruction set. Don't shortcut this step. Sloppy instructions mean the agent shares or edits data at the wrong moment.
What It Touches in Your HubSpot Strategy
This update is bigger than it looks on the surface. Here's where the ripple effects hit:
- Contact records stay current without a human touching them, which tightens your data quality across every workflow that depends on clean properties.
- Service Hub ticket volume drops for routine update requests. Agents get fewer low-value calls. That's a direct impact on your team's capacity.
- Any automation or workflow that triggers off a contact property change, like an address update triggering a re-shipment workflow, fires correctly because the write-back happens at the CRM level.
- Reporting on self-service resolution rates becomes possible. You'll be able to track which property changes happened via voice agent versus human agent, giving you a real metric for AI deflection.
- Sales Hub teams using calling features should evaluate whether Customer Agent can handle inbound call routing and pre-qualification updates before a rep joins the conversation.
Key Takeaway
Every contact property the agent can edit is a task your human team no longer has to handle. That's not a small efficiency gain. That's a structural shift in how your service capacity works.
This update is a direct extension of HubSpot's broader agentic platform strategy. If you want the full picture of where Breeze agents are headed and what's available today, the HubSpot Agentic Platform pillar gives you George's on-the-record breakdown of the roadmap.
Key Takeaway
The identity verification step isn't optional etiquette. It's your compliance layer. Always set a Data Protection Level before toggling View or Edit on any property that contains personally identifiable information.
This calling update is part of a larger week of Customer Agent improvements. If you want the full context of what else shipped alongside this feature, see our roundup of the week Customer Agent got its biggest promotion yet.
Who Should Care Most
Not every HubSpot portal needs this right now. Here's who should move fast and who can watch from the sideline:
- Service Hub Pro and Enterprise teams with high inbound call volume for routine updates, address changes, billing confirmations, or profile corrections. This is the primary use case.
- RevOps leaders who want accurate self-service deflection metrics and clean CRM data without relying on humans to enter updates after every call.
- Sales Hub Enterprise teams exploring AI-assisted inbound call handling before a rep takes over.
- Growing companies with small service teams who can't afford to staff every routine call with a live human. This lets fewer humans handle more complex work while the agent handles the predictable stuff.
If your inbound call volume is low, or if most of your calls require nuanced judgment calls, this update is worth bookmarking but not worth rushing to configure today.
George's Take
We've been inside enough portals to know that the gap between "we have HubSpot" and "HubSpot is actually working for our humans" is almost always a process gap, not a tool gap. What excites me about this update is that it closes one of those gaps at the voice layer. I keep seeing companies invest in chat automation, in off-hours messaging, in AI-powered email, and then the phone rings and everything reverts to 2008. That stops here, if you set it up with care.
“The phone channel has been the last holdout of manual, repetitive service work. This update is HubSpot saying that era is over. But it only works if you write good instructions and respect the verification layer. Don't skip that step.”
My honest caution: the agent is only as good as the instructions you write for it. We've seen AI tools underperform not because the tech failed but because the humans configuring it were vague. Treat every instruction field like you're writing a script for a new team member on their first day. Specific, clear, and scoped.
If you're ready to put Customer Agent to work across your service strategy but aren't sure where to start, or if your portal already has a calling setup that needs an honest audit, let's talk. Book a strategy call with the Sidekick team and we'll map out exactly which properties to expose, how to structure your verification rules, and how this fits into your broader service playbook.
Frequently Asked Questions
What contact properties can HubSpot Customer Agent read during a call?
Customer Agent can read any contact property you explicitly grant it access to inside Service > Customer Agent > Define > Permissions. You select each property individually, set a verification level, and write instructions for when the agent should use it. There's no blanket access. You control exactly what the agent can see and speak.
Can HubSpot Customer Agent update a contact record without a human agent?
Yes. When you toggle Edit Property on for a given contact property, the voice agent can write changes back to the CRM in real time during a call. The caller must pass identity verification first. Once verified, the agent updates the record automatically, and any workflows tied to that property fire as normal.
What is the Data Protection Level setting in Customer Agent for calling?
Data Protection Level controls how the agent verifies a caller's identity before sharing or editing contact data. The current option is Match Email or Phone Number, which means the agent confirms the caller's inbound number matches the contact record. You must set this for every property you expose. Skipping it creates a privacy risk.
Who can use the Customer Agent calling actions feature?
This feature is available to HubSpot Sales Hub Professional, Sales Hub Enterprise, Service Hub Professional, and Service Hub Enterprise customers. It also requires HubSpot Credits to run. The feature is in private beta as of May 2026, and all users in qualifying accounts are automatically included in the beta.
How do I test my Customer Agent voice configuration before going live?
HubSpot added an improved agent tester to the Customer Agent setup flow. Use it to simulate a voice conversation and verify your instructions behave as expected. Run through scenarios where a caller asks for data, then run scenarios where they request a change. Fix gaps in your instructions before flipping the agent live.
Does Customer Agent calling work with HubSpot Service Hub workflows?
Yes. Because the agent writes property changes directly to the CRM contact record, any workflow that triggers on a property change will fire normally. For example, if a caller updates their billing address and you have a workflow that sends a confirmation email when that property changes, that workflow runs automatically after the call.
