RefQuest · Sports technology
How RefQuest moved support to HubSpot and connected it to sales, billing and renewals.
RefQuest came to us to move its support operation from Zendesk into HubSpot Help Desk without losing how the team already worked. The same project connected the rest of the customer lifecycle: two sales pipelines, automated renewals, QuickBooks invoices tied back to deals, a customer health score and an executive dashboard, all in one portal and documented end to end.

- 7
- support channels routed into one help desk: five inboxes, a phone line and a support form
- 5
- teams working from one portal: support, sales, finance, account management, leadership
- 4 → 1
- team dashboards rolled up into one executive view
The challenge
The core of the project was a migration, and a migration is only as good as what survives it. Support lived in Zendesk, and the team had built up ways of working there that needed to carry across.
- Support had to move without starting from scratch. Ticket stages, five shared inboxes, a support form and a phone line all needed a home in HubSpot Help Desk.
- Years of Zendesk logic had to be preserved. Macros, keyword triggers that assigned owners and tags, and agent aliases used in sign-offs all shaped how tickets were handled day to day.
- Service levels and feedback needed to be measurable. The team wanted response and close targets enforced in the tool, and a CSAT survey that captured why a customer was unhappy, not just a score.
- The commercial side needed the same rigour. Renewals, invoices and account health all connect to the same customer, and each needed a defined, automated path in the same portal.
What we built
We started with the help desk, then connected it to the rest of the customer lifecycle, so each part hands over to the next through shared properties and workflows rather than manual steps.
-
01
Support
Tickets arrive by email, phone and a support form, and are routed, worked and closed against defined service levels.
- HubSpot
-
02
Win
A New Business pipeline moves deals from first contact to close, with a forecast category at every stage and agreement details captured at Closed Won.
- HubSpot
-
03
Invoice
QuickBooks invoices sync into HubSpot and attach themselves to the right deal.
- QuickBooks
- HubSpot
-
04
Renew
Closing a deal creates the next renewal in an Existing Business pipeline that counts down to contract expiry.
- HubSpot
- LinePilot
-
05
Score
A health score for each active customer combines engagement, CSM sentiment and invoice status.
- HubSpot
-
06
Report
Dashboards for sales, finance, support and account management roll up into one executive view.
- HubSpot
From there, HubSpot rolls up what has been invoiced, paid and is outstanding on each deal, and shows how far each one has been paid.
We built on HubSpot’s native objects (tickets, deals, invoices, workflows, segments and surveys), so the team works where it already does and RefQuest’s own admins can see and edit every rule. Where a native feature fell short, we filled the gap precisely: a custom survey where the CSAT needed a link and a reason for an unhappy rating, and LinePilot to copy line items onto renewal deals.
The details that made it work
Zendesk behaviour carried across
Zendesk stages were mapped to a five-stage HubSpot pipeline: New, Waiting on us, Waiting on them, Solved and Closed. Macros, with their text and images, became HubSpot message templates. Zendesk triggers were rebuilt as a routing workflow that assigns the owner and tags from keywords in the ticket, then emails the customer to say who has picked it up. A snippet lets agents keep signing off with their Zendesk alias. Service level timers pause while a ticket is waiting on the customer, so slow replies don’t count against the team.
A CSAT survey that explains the score
HubSpot’s standard CSAT couldn’t be linked from the closed-ticket email and couldn’t capture why a customer rated unhappy. We built a custom survey, then added workflows that copy the rating, reason and date onto the latest ticket, so the results land where the support reports need them.
Renewals that create themselves
HubSpot won’t let a deal enrol in the workflow that created it, so a single renewal workflow would stop after one cycle. We built a pair of workflows that hand over to each other, so each renewal creates the next. LinePilot copies the line items across, and each renewal carries the previous deal’s value, which makes net and gross revenue retention measurable. Every renewal is typed automatically as Expansion, Flat, Contraction or Churn.
How we delivered it, and keep it running
- MigrateZendesk stages, macros, triggers, channels and the support form rebuilt in HubSpot Help Desk
- ConnectNew Business and Existing Business pipelines, automated renewals and the QuickBooks invoice sync
- MeasureService levels, the custom CSAT survey, the health score and dashboards for every team
- DocumentOne reference covering every pipeline, property, workflow, survey, report and scoring rule
Ready for the team to own
- Each element is documented by purpose, behaviour and where to find it in the portal, for training and ongoing reference.
- Required properties at Closed Won and Closed Lost keep the data behind forecasting, renewals and retention consistent.
- Custom Help Desk views, message templates and snippets mean agents start from familiar tools.
- A chatflow and Customer Agent are configured and ready to switch on when RefQuest chooses.
The results
RefQuest now runs support, sales, billing and renewals from one connected HubSpot portal, with the logic documented and owned by the team.
- Support
- Works in HubSpot Help Desk with the routing, templates, aliases and service levels it relied on in Zendesk, and sees the reason behind every unhappy rating.
- Sales
- Works one pipeline for new business and one for existing business, with forecast categories and prompts six, three and one month before a renewal.
- Finance
- Gets QuickBooks invoices attached to the right deal automatically, with invoiced, paid and outstanding amounts on the deal.
- Account management
- Sees a health score and status for every active customer, alongside forecast categories and at-risk accounts.
- Leadership
- Has one executive dashboard across sales, finance, account management and support.
More of our work
Fortis Payment Systems · Embedded payments and merchant services (US)
How Fortis moved a sales team off Salesforce and runs merchant boarding from HubSpot.
Fortis Payment Systems is a US embedded payments provider. After it acquired Serve First Solutions, whose sales team ran on a heavily customised Salesforce, we migrated that team’s active data into Fortis’s HubSpot and ran the cutover over a single weekend, so reps were back in HubSpot on Monday morning with their full history. We also built a custom two-way integration with Fortis’s Partner API, so reps pick an office and agent and submit merchant boarding applications from the deal. Salesforce is retired, and every closed-won deal carries an office ID and an agent ID.
Read the case studyPrevent Biometrics · Sports technology and manufacturing
How Prevent Biometrics runs orders, shipping and invoicing from HubSpot.
Impact-sensing mouthguards made for teams and governing bodies such as World Rugby. We connected HubSpot to their inventory, shipping and invoicing tools, so every order runs from signed deal to sent invoice in one place.
Read the case study