Does HubSpot support not cover this?
It covers the product: usage questions and platform failures. It does not run your portal or repair your integrations or workflows; for that you need an in-house administrator or partner support.
Guide · Support and operations
What should a monthly HubSpot support plan include?
Written response times, incident diagnosis included, alerts when an integration stops bringing in data, hours visible every week and documentation in your name. Without those five pieces, monthly support is a bucket of hours that gets spent without you knowing on what. In Chile and Latin America it pays to ask for them in the contract, not only in the sales proposal, and to check every quarter that they are met.
- 7 minute read
- Written response times
- Visible hours
- Chile and Latin America
What to ask for in writing
| Piece | What to ask for | Sign it is missing |
|---|---|---|
| Response times | Critical in business hours; normal by the next day | "We will look at it as soon as we can" |
| Diagnosis | Included in the plan, without a quote | You get a quote to look into an error |
| Alerts | A notice if a source stops bringing data | You find out when sales drop |
| Hours | Balance and log every week | A total at the end of the month |
| Documentation | Inventory, code and keys in your name | Nobody can explain certain workflows |
What does HubSpot support cover and what does it not?
HubSpot support answers product questions and platform failures: on Starter through chat and email, and on Professional and Enterprise also by phone. Chat and email are available in Spanish; phone, for now, only in English. In accounts created since March 2024, whoever asks for help needs a Core, Sales or Service seat.
What HubSpot does not do is run your portal: it does not check why a workflow stopped enrolling, repair the integration with your ERP or organize your reports. That is what a partner's monthly support covers, and that is why it should be defined in as much detail as a project.
Which response times should you ask for?
First, what is critical: something that stops sales or service, such as a form that does not create contacts, a broken integration or users without access. Critical issues are measured in business hours; normal ones, in days. Ask for two separate times, first response and resolution or plan, and the hours during which they run.
A response time without a log cannot be enforced. Ask that every request records the time it was made, the first response and the close, and that you receive that log every month. In Chile and Latin America, many contracts say "best effort": that is not a response time.
What should be included without a quote?
Diagnosing an incident: understanding what broke and why. If every review starts with a quote, the incentive is not to look. Minor changes, such as a field, a filter or a notification, should also fit in the plan without a purchase order.
What does not fit is quoted with a fixed scope and price: a new integration, a pipeline redesign or a migration. The line between the two should be written down before signing, with examples, so it is not argued over with every request.
How do you know how the hours are used and whether the numbers reconcile?
With a weekly balance, a log per request and a notice before the plan runs out. A closing note every Friday, with what was solved, what is pending and the hours used, is worth more than a monthly report nobody reads.
Also ask the support team to check, every so often, the numbers your management uses, such as new deals or sales by source, against the records, and to keep the inventory of workflows, integrations and properties up to date. That way, if you change providers tomorrow, you lose nothing.
Step by step in HubSpot
How to evaluate your current support or a new one
Six steps with what has already happened in your portal.
- 01
Review the last three months
List every incident and request: when it was made, when you got a response, when it was solved and whether it had to be quoted.
- 02
Write down what is critical
Concrete examples from your operation: the quote form, the ERP integration, sales reps' access. That list goes into the contract.
- 03
Ask for times by severity
First response and resolution or plan for critical and normal issues, with hours and channel. Without written times, any delay is acceptable.
- 04
Require diagnosis to be included
Understanding why something fails should not need a purchase order. What does get quoted are projects with a fixed scope.
- 05
Turn on alerts on your data sources
Every integration and form that brings records daily needs a notice if it spends 24 hours at zero, with someone responsible for checking it.
- 06
Secure the exit
A living inventory, code, keys and manuals in your company's name, and at least one Super Admin of your own. That is what lets you change providers without losing anything.
What it looks like done right
What changes when support is well defined
- You know how long a response can take before you ask.
- An error gets reviewed without waiting for a quote.
- You hear about a broken integration from a notice, not from sales.
- Every Friday you see how the hours were used.
Common mistakes
What we see most often in portals across Chile and Latin America
Contracts with "best effort" and no response time that can be measured.
A quote to diagnose every error, even in what the same provider built.
Hours reported as a total at the end of the month, with no detail per request.
Integrations and keys in the provider's name, with no documentation and no Super Admin of your own.
Want to know if this applies to your case?
Book a 30-minute diagnostic30 minutes with Roberto. No demo and no access to your CRM.
How we solve it at Revenue Hub Latam
HubSpot support with written response times
In Managed and Dedicated HubSpot, critical issues get a response within 2 business hours and incident diagnosis is included. An alert warns you if a source stops bringing data, you see the hours balance every Friday, we reconcile your management's key numbers and everything is documented in your name.
Support and operations
Hours package, Managed HubSpot or Dedicated HubSpot, with written response times and visible hours.
Compare plansDedicated HubSpot
A named specialist with backup, every day, with same-business-day response.
See Dedicated HubSpotSwitch partners
If your current support lacks these pieces, an orderly handover in 30 days without stopping your operation.
See the handover
The guarantees that apply
- Responds.
Signed response times: 2 business hours for critical issues and incident diagnosis included.
- Alerts.
An automatic alert tells you if an integration or form stops bringing in data. You hear it from us first.
- Reconciles.
We check the numbers your management uses against the records, with definitions and sources documented.
- It’s yours.
Workflows, integrations, code and keys documented and in your name. If you change partners, you lose nothing.
We put them in writing because they are what we control.
Straight answers
Frequently asked questions
What counts as a critical incident?
Something that stops sales or service: forms that do not create contacts, a broken integration, users without access or a workflow sending emails by mistake. Write your own examples into the contract.
What is an SLA?
A service level agreement: the response and resolution times the provider commits to, by severity and during which hours. It is only useful if it is logged and reviewed.
Do unused hours roll over?
It depends on the contract; in many, they do not. What matters is seeing them every week so you use them in time, and adjusting the plan every quarter if there are too many or too few.
How much does monthly HubSpot support cost?
In Chile and Latin America it is charged as an hours package or a fixed monthly plan, based on how many people use HubSpot, how many brands or departments you have and which integrations exist. Compare what each proposal includes, not just the hourly rate.
How often should support be reviewed?
Every quarter: response times met, hours used, repeat incidents and documentation up to date. If something is not met, it is time to renegotiate or to change.
Who writesRoberto Guerra
Designs the CRM architecture, integrations and operation of each account. He writes these guides from what he sees every week in HubSpot portals of B2B companies across Chile and Latin America.
Meet the team30 minutes with Roberto.
We review one concrete problem, its impact and your starting point. No demo and no access to your CRM.