Do I need Service Hub to refer tickets to sales?
Tickets exist in every tier, but ticket-based workflows require Service Hub Professional or Enterprise. Without them, the referral is manual from the ticket's Deals card.
Guide · Service Hub and sales
How to connect customer service with sales in HubSpot?
Make the referred ticket create a deal in the right pipeline, associated with the same contact and company, with an association label and a property that attributes the origin to service. That way the management of a company in Chile or Latin America sees how much the support team sells, and sales does not lose the opportunities born in a complaint or a question.
- 7 minute read
- Ticket-based workflows
- Association labels
- Chile and Latin America
From the ticket to the deal with a trace
- Ticket in the support pipeline
The agent spots an opportunity: expansion, renewal or a new product.
- Property "Refer to sales" set to Yes
A ticket field triggers the workflow; the agent never leaves the screen.
- The workflow creates the deal
Create record action: a deal in the right pipeline, associated with the ticket, the contact and the company.
- Attribution to service
Deal origin property set to Service and association label "Referred from ticket".
Why do opportunities born in support get lost?
Because the handoff lives in a chat message. The agent notices a customer wants to expand, tells a rep over WhatsApp and the ticket gets closed. Nobody created a deal or associated it with the ticket, and a month later nobody knows how much service sold.
In HubSpot, tickets and deals live in the same CRM and share contacts and companies. What is missing is a rule that says what gets referred, to which pipeline and with which data, and a workflow that executes it the same way every time. The trace between ticket and deal is what later lets you measure.
Which objects and properties are involved?
On the ticket side, the default properties Source, the channel it came through; Ticket owner; Ticket status, the stage of the support pipeline, by default New, Waiting on contact, Waiting on us and Closed; Pipeline; and Category. To that you add two custom properties: Refer to sales and Referral reason.
On the deal side, HubSpot has no default property that says which area it was born in: Record source says a workflow created it and Original Traffic Source mirrors the contact's web traffic. That is why you need a custom Deal origin property with values like Service, Marketing, Sales and Referral.
Manual or automatic?
Manual works for low volumes: from the ticket, in the Deals card, Add deal > Create new, you choose contact and company, and the Add timeline activity checkbox copies calls, emails and notes from the last 30 days. The association label is set afterwards. The risk is that it depends on the agent remembering.
Automatic requires Service Hub Professional or Enterprise for ticket-based workflows. The trigger is Refer to sales set to Yes; the Create record action creates a deal with name, pipeline and stage, associated by default with the enrolled ticket; with Add another association you link it to the contact and the company and apply the label. Make sure the new deal does not meet the trigger.
How do you measure what service sells?
With the custom report builder: primary source deals, filter Deal origin equals Service, grouped by close month and by ticket owner through the association label. A second report crosses tickets and deals to see which referral reasons end in sales.
The loop closes back: a deal-based workflow sends an internal email to the ticket owner when the deal is won or lost. In companies across Chile and Latin America, that data is what lets you recognize service as a sales channel.
Step by step in HubSpot
How to build the referral in HubSpot
Six steps: four of configuration and two of operation.
- 01
Define what gets referred and to which pipeline
With service and sales at the table: which requests are opportunities, which pipeline they go to, who owns them and in which stage the deal is born.
- 02
Create the properties
On the ticket, Refer to sales as a checkbox and Referral reason as a dropdown. On the deal, Deal origin with Service, Marketing, Sales and Referral.
- 03
Create the association label
Data Management > Data Model > Edit Data Model, tickets and deals, View all > Create association label: "Referred from ticket". Requires a super admin.
- 04
Build the ticket workflow
Trigger: Refer to sales is equal to Yes. Actions: Create record > Deal with pipeline and stage, Deal origin set to Service, associations with the label and an internal email to the owner.
- 05
Close the loop back to service
Deal-based workflow: when the labeled deal reaches Closed won or lost, internal email to the ticket owner and an update to a ticket property.
- 06
Report by origin
Custom deals report with Deal origin equal to Service, by month and by ticket owner, on the management dashboard.
What it looks like done right
What changes when service and sales share the trace
- Every opportunity spotted in support exists as a deal, with a pipeline and an owner.
- Management sees how much service sells, by month and by agent.
- The agent who referred it knows whether the deal was won, and why.
- Nobody depends on a chat message to hand over a customer.
Common mistakes
What we see most often in portals across Chile and Latin America
The handoff happens over WhatsApp and the ticket closes without creating any deal.
The deal gets created but not associated with the ticket, so nobody can measure the origin.
Original Traffic Source is used as if it were the commercial origin: it says web traffic, not that it came from service.
A workflow that creates deals and re-enrolls with the new deal, duplicating records.
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 Rescue: the service-to-sales trace, redesigned and tested
We design the referral rule with your teams, create properties, labels and workflows, test with real cases and leave the reports by origin on the management dashboard. Everything stays documented and in your name, and the reconciliation of those numbers continues in the operations plan.
HubSpot Rescue
We redesign the customer service to sales trace together with pipelines, workflows and permissions.
See the serviceReports that reconcile
Service-origin deals with definition and source, on the same dashboard as marketing and sales.
See the serviceHubSpot support and operations
Referral workflows are maintained, tested and documented every month with written response times.
See operations plans
The guarantees that apply
- It’s yours.
Workflows, integrations, code and keys documented and in your name. If you change partners, you lose nothing.
- Reconciles.
We check the numbers your management uses against the records, with definitions and sources documented.
We put them in writing because they are what we control.
Straight answers
Frequently asked questions
What does the Create record action do?
It creates a deal, contact, company, ticket or another object from the workflow, associated by default with the enrolled record. For a deal it requires name, pipeline and stage; with Add another association you link it to the contact and the company.
What is the association label for?
To tell that link apart from any other: "Referred from ticket" lets you filter lists, trigger workflows and build reports only with the deals born in service. It is created from the data model and requires Professional or Enterprise.
Does HubSpot have a deal origin property?
Not one that names the commercial area. Record source indicates the tool that created the deal and Original Traffic Source mirrors the contact's web traffic. You need a custom Deal origin property.
How do I keep the workflow from creating duplicate deals?
With a trigger the new deal does not meet, a condition that checks the ticket does not already have an associated deal with the label, and the Refer to sales property cleared after the record is created.
Can I measure how much service sells?
Yes, with a custom deals report filtered by Deal origin equal to Service, by close month and by ticket owner. It is a number we reconcile every month in portals across Chile and Latin America.
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.