What are automatic rules in HubSpot?
They are conditions checked on their own against CRM records. Some come with HubSpot and others are added by a tool such as HubCoach. What matters is knowing who acts when the rule is met.
| Type | What it does | Who acts |
|---|---|---|
| Required property in a stage | Asks for a field when the deal moves to that stage | The person, when changing stage |
| HubSpot workflow | Runs actions when a record meets conditions, depending on your subscription | HubSpot |
| HubCoach check | Flags a situation on native data, such as an overdue date | The person, who decides and saves |
| HubCoach team rule | Shows the team’s criterion when your conditions are met | The person, with the example in view |
Which baseline can your team start with?
HubCoach, a Revenue Hub Latam product, includes 42 checks across deals, contacts, companies, tickets, activities, marketing and aggregates. They start on. An administrator can switch off individual checks, categories or the whole library, and save exceptions for a portal.
An overdue close date gives the rep something concrete to review, but the signal does not decide a new date: the person confirms the customer’s situation and saves the change in HubSpot. Checks depend on the data and permissions available.
When should your team add a rule of its own?
When the criterion is yours rather than HubSpot’s: what a deal in Proposal sent must have, what to check before passing a lead or what to confirm before closing a ticket. For example, requiring the company’s tax ID before quoting in Chile, or the tender number on public sector deals in Latin America.
- Choose the object and the conditionFor example, deals with an empty Next step.
- Write the notice with an exampleWhat is missing, why it matters and what good looks like.
- Choose the audienceJust you, a pilot group or the whole team.
- Test before publishingCheck the notice on a real record.
- Useful notice
“The next step is missing. Write the action, the owner and the date agreed with the customer. Example: send the proposal on Thursday.”
- Could be better
“Fill in the field.” It does not say why or how.
Why do a rep and a leader need different help?
A rep may keep a personal rule for their own follow-up. An administrator publishes shared criteria to a defined audience. They are different things, and each has its place.
Language, density and surfaces are saved for each person; organization policies still govern the shared experience. Explain the reason for each signal and the next useful action so the help feels relevant.
How do you move from noticing an issue to resolving it?
On supported records, lists and boards, signals highlight pending work. The Side Panel brings the explanation, knowledge and assigned steps to the record. Supported actions open native HubSpot controls; the person reviews and saves.
Leaders can revisit saved views and assigned plans with the team. Review a few real records to understand what improved and what is still hard. A read or a completed step measures activity; it does not guarantee a commercial result.
How do you start with a first group?
Choose a small group, one concrete process and the checks that help it act. It is how we recommend teams in Chile and Latin America get started. When your organization receives access, that group starts with a 7-day trial.
Current seats are full: apply to the waitlist. We review applications every 15 days, and no payment is collected during this early access stage.
What should you review this week?
- Choose one team and one frequent decision.
- Review the checks and switch off the ones that do not apply to your portal.
- Publish the shared rules to the right audience.
- Let each person adjust their personal rules and preferences.
- Review records and exceptions together after the pilot.