More HubSpot Record Customization Goodness: Part 2

Episode Overview

This episode explores how record customization transforms from a technical feature into a human-centered experience. George B. Thomas, Max Cohen, and Chad Hohn discuss conditional logic, workflow buttons, agents, and customization strategies, emphasizing that better record design helps teams move faster and feel more comfortable within HubSpot.

Key Learning Points

• Record customization works best when built around human needs, not admin preferences
• Workflow buttons become more useful when renamed using plain language
• Conditional logic displays relevant information at the right time
• Logging in as a user helps you see what your team actually experiences
• Over-engineering records creates confusion rather than value
• Record customization is becoming increasingly flexible and powerful

HubSpot Updates Covered

The team digs into two exciting updates: agents in CRM cards that display agent outputs directly within records, and customized workflow names for the "Enroll in Workflow" CRM card. This lets admins keep technical internal names while displaying user-friendly button labels.

Workflow Buttons and Customization

Technical workflow names like "B2B_Forum_Offer_Nurture_Campaign_v2" confuse end users. The new feature lets buttons display clear language such as "Assign Sales Rep" or "Launch Nurture" while preserving backend naming conventions. This small change makes a massive difference in adoption.

Conditional Logic Strategy

Cards and buttons should appear contextually. For example, a handoff workflow only appears after a deal reaches the appropriate stage. This reduces clutter and improves the user experience. The key: show what matters, hide what doesn't.

Multi-Team Views Consideration

Chad raises a practical concern: multiple team-based views can create inconsistency. Humans sharing record links may see different layouts. The hosts recommend using conditional logic centered on the record lifecycle stage rather than team assignments.

Login as User Feature

Chad stresses the importance of using the "log in as user" feature to verify how records display under different permission sets. Admins often miss visibility issues and access problems that affect end users. This is your secret weapon for building records that actually work.

Practical Next Steps

1. Ask three team members what they love, hate, or wish to change on frequently-used records
2. Review workflow buttons and rename them to explain outcomes clearly
3. Audit record layouts and eliminate noise
4. Add conditional logic where relevant information should appear at specific stages
5. Test records using the log-in-as-user feature across different roles
6. Simplify team-based views where possible
7. Before adding anything new, ask: "Does this help the human using it?"

Core Philosophy

"Stop building records only for the admin brain." Instead, focus on what sales reps, service representatives, and marketers actually need. Good customization means doing what matters, not doing more.

The hosts emphasize empathy as an operational tool. Better adoption and fewer support questions follow when record design reflects actual user workflows.

Bottom line: "Just because you can doesn't mean you should." Talk to your humans, build what's needed, show what matters, hide what doesn't, and avoid over-engineering your HubSpot portal.