I'm implementing it · 4 min read
Decide before you configure the CRM you already have
The decision to turn something on is close, and you need to know what to decide first and what each step actually costs.
If you have five minutes
- Several of the features in this year's Smart CRM wave are still public or private beta.
- "Configuring" one of them usually means opting into a beta with a policy question attached to it, not flipping a settled switch.
Decide before you configure
Several of the features in this year's Smart CRM wave are still public or private beta. "Configuring" one of them usually means opting into a beta with a policy question attached to it, not flipping a settled switch. Decide the policy first — the beta will still be there once you have.
Five decisions and owners
| Decision | Owner | What it costs to get it late |
|---|---|---|
| Who is allowed to click revert on a property | HubSpot admin or RevOps | Your audit trail carries a human-reverting-human entry with no policy behind it. Casey Hawkins: "One-click restore is awesome — it also means your audit trail now has a new kind of entry to explain: a human reverting a human." |
| Who reviews what customer agent drafts before it becomes knowledge-base "law" | Whoever the org has already made accountable for HubSpot | Whatever the agent guessed gets saved as if it were policy, and AI then treats it as policy. Chris Carolan: "The ones that never decide end up with whatever the agent guessed, saved in the knowledge base as if it were law — and then AI treats it as law." |
| Whether to migrate off your extra-properties-and-record-IDs workaround before turning on cross-object filtering | Whoever owns the data model | You keep two systems finding the same records two different ways. Chris Carolan: "that workaround is working and it is not trivial to unwind." |
| Whether your AI or MCP write access respects the same conditional-property rules your humans do | Admin plus whoever owns AI write access | An agent can set a gated property and stop, straight past the rule you built. Casey Hawkins: "If Claude wants to update a deal type that you have gated with required properties, it will just set the deal type and stop." |
| Whether embedding live index pages on a dashboard changes how your team works, before you build a report send around it | Ops lead | Nobody has confirmed yet whether a scrollable CRM view survives being sent as a static dashboard email. Casey Hawkins: "I genuinely don't know how a live, scrollable CRM index view is supposed to render inside that kind of static send." |
The order to check things in
- Read your own portal's association labels and existing workaround properties before turning on Cross-Object Filtering Quantifier Controls.
- Write the revert policy — who, when, what gets flagged — before enabling Revert Single Properties in the history table (public beta).
- Decide the reviewer for customer agent's drafted knowledge before turning on knowledge generation (public beta), and start small: Chris Carolan's advice on air was "Start monthly, not daily. Twenty suggested knowledge moments, agree on one."
- Confirm which of your record edits happen through Android, iOS, desktop, or an AI/MCP integration — only the first three currently enforce conditional property logic.
- Test a dashboard with an embedded index page (private beta) against your actual dashboard-send workflow before anyone builds a process around it, since that interaction is unconfirmed.
What a workaround already taught the show
The workaround that got built days too early
"The workaround she described is the one every admin eventually builds: import something to get the record IDs, export it back out so you have them, then use those to associate everything across objects." — on Smart Duplicate Handling in Multi-Object Imports (live, first covered 2026-08-28)
As the take notes, Chris Carolan's point in the same segment was that the hardest part of a process like that isn't building it — it's testing it, since an import failure often only shows up after you're already most of the way through it. That's precisely why the workaround existed in the first place, and it's worth remembering the next time a beta promises to remove one: the workaround got built because the platform gap was real, and it will keep running until someone deliberately retires it.
Credit: Chris Carolan, on Cross-Object Filtering Quantifier Controls — Another Orange Morning, September 3, 2026. Read the update.
Credit: Casey Hawkins, on Revert Single Properties in History Table — Another Orange Morning, May 26, 2026. Read the update.
Credit: Chris Carolan, on Customer Agent now generates knowledge from your ticket history — Another Orange Morning, September 2, 2026. Read the update.
Credit: Casey Hawkins, on Conditional Property Logic When Editing Records on Android — Another Orange Morning, July 16, 2026. Read the update.
Credit: Casey Hawkins, on Add internal HubSpot pages to your Dashboards — Another Orange Morning, August 11, 2026. Read the update.
Credit: Madelyn Donovan, on Smart Duplicate Handling in Multi-Object Imports — Another Orange Morning, August 28, 2026. Read the update.
Where to next
Where this comes from
- Chris Carolan on Cross-Object Filtering Quantifier Controls. Another Orange Morning, September 3, 2026.
- Casey Hawkins on Revert Single Properties in History Table. Another Orange Morning, May 26, 2026.
- Chris Carolan on Customer Agent now generates knowledge from your ticket history. Another Orange Morning, September 2, 2026.
- Casey Hawkins on Conditional Property Logic When Editing Records on Android. Another Orange Morning, July 16, 2026.
- Casey Hawkins on Add internal HubSpot pages to your Dashboards. Another Orange Morning, August 11, 2026.
- Madelyn Donovan on Smart Duplicate Handling in Multi-Object Imports. Another Orange Morning, August 28, 2026.
What we do not know yet
- Whether a revert erases or appends history is Casey Hawkins's own read, not confirmed by HubSpot: "My read — and it's a read, not confirmed by HubSpot — is that it has to add the old value back as a new history entry rather than erasing what came before it." Check your own portal's behavior before you rely on it for an audit answer.
- Whether every AI or MCP write path bypasses conditional property logic the same way, or just the one tested on air — the show's coverage is one example (Claude, through the MCP, setting a gated deal type), not a survey of every integration.
- Cross-Object Filtering's "select by label" step, named above as the likely next move, has not shipped. Don't sequence a build around a date for it.