Ask Breeze First: Coaching the Agent, Every Email as a Contact and Who Has Gone Quiet

Another Orange Morning Recap: Thursday, October 29, 2026

Two days before Halloween, Trisha Merriam took the Thursday chair next to Casey Hawkins and Chris Carolan, and the three of them worked through five updates in depth. One of them was not on the list I brought. It surfaced while Trisha and Chris compared what their boards showed.

Here is what we got into: coaching a customer agent by talking to Breeze, a new setting that turns incoming email into contacts and the question of whether HubSpot can be your inbox, a refreshed Add to Dashboard panel, the official Epic app for medical records, and supervised mode for customer agent. Will It Breeze asked who has gone quiet across tickets, and Breeze answered with a recommendation to check before you automate.

Before the Updates: Agents, Tool Sprawl and a House Rule

Chris opened with the Houston HUG, which went full Men in Black this week: take down the villains of bad data and missing context in your HubSpot portal. The free virtual workshop was at 1 p.m. Central today, ninety minutes, and the promise is that you leave with a working agent and an idea of what it costs. Chris shared one thing from the registrations: among the people who rated themselves intermediate or advanced, he said about a third feel good about using Breeze in HubSpot. I said that was no surprise for us, and Chris's answer was that this is why they are doing it. He also pointed everyone to the events calendar, which pulls HubSpot-led events, our shows and community-led events into one place. I jumped in that I need to talk to the agents about getting the Thursday webinar that Trisha and I run added to it.

Then we were on to You Just Inherited HubSpot, our LinkedIn series. This week is week four, licenses and functionality, and Trisha did great prep while I was out. She talked about the portals she has worked on as a consultant, where a new tool gets bought and nobody mentions it, and every once in a while she gets to ask whether you are paying for something that only does one thing and has not been touched in six months. I added my favorite example, Calendly, which people buy and then I ask whether they know HubSpot has a meeting scheduler. Chris said it is easy to reach for a pet tool and check the connectors first when you are inheriting a portal, without looking for the native feature that might already do it.

Trisha then asked a starting question: do we skip today's updates and leave them for tomorrow? I used to, I told her, "and then Chris said, no." The reason is a Boston clock. Updates land when work starts in Boston, the show starts about fifteen minutes after that, and when we used to start earlier we would watch a big update go by on LinkedIn that we could not talk about. Chris's rule now: "We're doing it live." Her screen showed four from today, mine showed two and Chris had three, and "We're just here reporting the news, folks."

Five Updates, One More in Passing

Customer Agent Reporting and Coaching in Breeze

Chris's pick, and he said he loved the first one, as you might imagine. Breeze Assistant now supports customer agent reporting and coaching: you can ask Breeze about your agent's performance, get improvement recommendations tied to your coaching opportunities, and make configuration changes, all from one conversation. It is in public beta for the Professional and Enterprise tiers of Marketing, Sales, Service, Content and Data Hub, and Smart CRM, with a release date of November 10 on the update panel.

Trisha recognized the text from the last time she was on, and said they must be doing this with a bunch of tools, pulling the experience into one place instead of making you hop around. Chris's point was that most admins do not know how to piece it all together, so you do not need to learn everything about AI to coach a customer agent, you can just ask Breeze. The part he kept returning to: coaching the agent is also coaching your people. When someone is coaching a customer agent and realizes the team should do something differently, "it's basically indirect coaching about your process," and the interpersonal dynamics that make people hold back from telling a human rep get out of the way.

Then Chris asked whether you can even build one report in the report builder that shows customer agent alongside email, text and help desk, and said he was looking. Trisha answered, "I don't know and I don't want to try." Chris: "You shouldn't want to try." His read is that people will start "trusting reporting coming from this conversation is much faster than everybody expects." Trisha pulled out one of the sample prompts as something that "probably never would have occurred to me": telling your customer agent to hand off whenever legal issues come up. Chris asked whether this means you now get to configure customer agents. I said it does seem that way, since the sample prompts include syncing your website as a data source and creating actions. Chris's next thought: "I guess I'll have to figure out how I can use credits." He also called Breeze as an orchestrator exciting, and said the Houston HUG would get into it later in the day. Before moving on he pointed at a close cousin, analyze your Help Desk and Customer Agent performance by topic, where the word is observability: being able to watch customer agent in all the ways.

Why it matters: before you open the report builder for an agent question, start the conversation in Breeze and see what it hands back. The coaching you do on the agent will also show you which parts of your own process need fixing.

For more details: customer agent reporting and coaching in Breeze.

Create New Contacts From Logged Emails

This is live for all hubs and tiers. A new contact email logging rules option automatically creates a CRM contact from incoming email to a connected personal account. Until now, connected personal inboxes only logged email from people who were already contacts. Service Hub could already do this through team email channels on the Inbox or Help Desk, which is not where sales reps usually work.

Trisha set the frame right away: "let's really get these logging rules right," because she did not want a cold pitch from someone offering to SEO her website ending up in her CRM. I took the explainer and agreed, "this might add a lot of people that you might not want necessarily." Chris's answer was to manage it like your forms: "if one in ten of them is the contact you care about, turn it on," and he pointed out that creating the record in the first place is the tedious part for most people. Trisha added the caution that stuck with me. If you have workflows that fire every time a new contact is added, "here's one area where I would say don't just turn it on, like, spend five minutes thinking about this," and broken processes create broken automation.

The part Chris said he had not noticed the last time he read it: "Does this activate HubSpot as a full inbox?" With the setting on, new email shows up under the emails dropdown in the record index views, which means you could manage the inbox you care about in HubSpot without having to look at Gmail. I agreed, "No, yeah, you're right." Chris said it is a big deal, "I don't think most people even know that email's index page exists," let alone that you can use HubSpot as your primary inbox, and you can now trigger lots of workflows off one-to-one email.

Why it matters: this setting creates a lot of records, and each new record can start a workflow. Look at your logging rules and every workflow that fires on a new contact before you turn it on, and if the answer is yes for your team, the email index may be the next place worth a look.

For more details: create new contacts from logged emails.

Updated Add to Dashboard Panel

This one was not on the list I brought. It came up while Chris and Trisha compared their boards, and then the screens disagreed. Chris said that "this is the part that we don't really know how it works," because your schedule for release is different than mine. Trisha said hers showed the update as live. Chris's answer: "Rolling out." and "This is just how GA works." Our record for this one has it as public beta, so how you see it depends on your portal.

What changed: a dedicated recently viewed section on the My Reports tab, and the panel layout goes from three main sections to two, with "recommended for you" renamed "suggested for you." Breeze surfaces the suggested reports based on what is already on your dashboard and your activity in HubSpot, such as saved pages and frequently used tools. I have used it, and said, "I've used this and it has been very nice," because you can finally "drop a report at the top" instead of having to drag it up from the bottom. Trisha asked whether the ready-made reports tab was new, and then gave her own reaction: "I am the laziest person alive." She wants HubSpot to know what she wants.

Chris spent his time on the rename. It seems like a small change, but "suggested for you" is a nudge, maybe check this out, while recommended implies there is a strategic reason you should be using it. In his words, recommended "puts more accountability and pressure on Breeze and AI versus the word suggested."

Why it matters: if you manage dashboards for a team, take a look at what Breeze suggests next to the reports you already trust, and do not read "suggested" as a recommendation.

For more details: updated Add to Dashboard panel.

HubSpot Epic App for Medical Records

Chris picked this one because it is the kind of situation where HubSpot was not even in the running, since it was not compliant. The Epic app connects Epic, the electronic health record system, with HubSpot, so teams can use Epic data for patient segmentation, workflow automation and reporting without manual exports. It is live for HIPAA customers in the U.S. with an eligible Enterprise subscription, and Sensitive Data has to be turned on in HubSpot. Custom field mappings require Data Hub Starter.

I took the Why: Epic is one of the two big medical apps, and the lack of it was "pretty much a deal breaker for people using Epic that wanted to potentially use HubSpot," with sensitive data being the other big one. HubSpot has put real effort into sensitive data, so this is closing the gaps. Chris took the How. The sync runs one way, "From Epic to HubSpot, Epic remains the source of truth," with patients syncing to contacts and appointments syncing to appointment records. He added, "It's very rare I get to talk about appointments in HubSpot. I think it's a very underrated object," and he noted that real-time sync means requesting access to Epic's outgoing HL7 interfaces.

Chris had two cautions. Turning sensitive data on can mean other features stop working, and the room added Breeze to that list. And on the risk question, this is an official app, "no third party building this app." Epic has to stay compliant to build it, so he does not read much risk into it, since "Epic stands behind HubSpot if they're going to build this."

Why it matters: if you work with healthcare organizations and HubSpot was ruled out for compliance reasons, this is the update to put in front of them again. Check the requirements first: HIPAA, an eligible Enterprise subscription, and the tradeoffs that come with Sensitive Data.

For more details: HubSpot Epic app for medical records.

Supervise Mode for Customer Agent

Trisha raised this one when Chris asked what else was on the screen. Her question: "What is supervised mode for customer agent? Is that new?" It is not even in beta, so "What does it mean when it's in development?" I said it is on the roadmap, and Chris added the forward-looking statement, so no promises made. It is in development for Service Hub Professional and Enterprise. Supervise mode is a deployment option that lets human agents review, edit and approve AI-drafted email replies before they are sent, an on-ramp for teams that want to see how customer agent does in real conversations before it replies on its own. It also lets you see how the agent uses actions during a conversation.

I read the Why and said it is very interesting: lots of teams want to reduce inbound volume with AI and are not ready to hand over full control. Trisha asked how it would work today, whether you would just turn it on knowing it was going to email people. Chris's answer was that testing it takes role playing, which people are not used to, and that "you can't test for every situation," but if you can turn it on and be there to approve, "that puts you in a good spot." He thinks the reason it is still in development is that "there's a whole approval layer that needs to exist that really hasn't before to be able to do that."

Why it matters: this is a preview of where Customer Agent is heading. Start deciding who on your team would review the drafts, and what they would look for, before the option arrives.

For more details: supervise mode for customer agent.

Will It Breeze: Who Has Gone Quiet?

Will It Breeze ran, and I drove it on my screen. I asked who wanted a role, and Trisha said "Success." The prompt, which I copied: "So as our customer success lead, using agentic automation, can you tell me who has gone quiet across tickets?" I opened it in the Tickets index on purpose, because the page you start on matters. Sometimes I ask from the product updates page and Breeze tries to tie in whatever update I have open. Chris agreed that it makes a big difference, and he also starts from the place where the context is. More on the Will It Breeze page.

Chris read Breeze's answer aloud. In a demo portal, it found twenty-eight tickets marked waiting on contact across two hundred seventy-one. It called them "potential gone quiet cases, not confirmed customer silence," because reply dates were missing and it could not retrieve linked conversation history or a named contact. I noticed that it gave us the tickets, the priority and how long each had been waiting, and that it did not use agentic automation at all. We looked at the last line, and Chris read the recommendation: start with the high priority cases, and before any automated outreach, verify the latest conversation and identify the recipient so you do not chase someone who already replied elsewhere. Someone in the room said it was coaching already.

That is where I told a story from client work. The help desk inbox is not connected, or a rep's inbox is not, and the conversation history lives somewhere else. Then someone asks you to set up a follow-up for tickets that have gone quiet, and "a week later, you get a Slack message that's like, why did this customer get this email?" The team has been in active conversations, even contract negotiations, "and now we look like idiots." Chris's response: you look like idiots because you do not manage your contact associations, and he took it back to the inbox thing from earlier. When the customer chooses which email to reply from, or their replacement writes to you directly, there is no ticket tied to that person, so automatically creating the contact, which he assumed happens when the company domain matches, matters for moments like this one. Chris also said that most other systems are account based, with Trisha chiming in, and that then you try to automate outreach, and Breeze has to ask who it is going to, because there are no contact records associated.

Chris's lesson was the one he started the day with: "The coachability already coming into Breeze, which is why we want you to ask Breeze first." The next move, he said, is that agentic automation becomes about getting those contacts associated, which he put at one or two prompts away. It is the kind of CRM administration that used to feel like a project nobody wanted.

The Rest of Thursday's Updates

Also on Thursday's board and not pulled forward: the Developer Secrets API is in public beta for accounts with developer apps, and lets agents and automation list, create, update and delete an app's secrets without ever reading their values. You can now filter segments for records that do not have a given association, or a specific association label, which retires the extra segment or calculated property people used to build for it. That one is live for all hubs and tiers. Date property validations now allow today when you choose "Any future date" or "Past dates only," also live for all hubs and tiers. Everything else that shipped is in the HubSpot updates feed.

The Sign-Off

Chris reminded everyone that he has Hubsessed Office Hours today on Unified Revenue View, at 11 a.m. Central. If that is not your lane, Trisha and I are doing our thing on LinkedIn, and Value-First AI Daily will preview what Chris and Nico are building with HubSpot Academy in December, all things Breeze and HubSpot AI. Then back to the Houston HUG at 1 p.m., where you can come build some agents with us. You probably already own the value you are looking for in HubSpot. You just need to wake up to it. We will see you tomorrow morning.