Design the sales-to-service handoff

The moment a deal closes is the moment most teams drop the ball. Sales celebrates, the rep moves on to the next prospect, and the new customer sits in silence wondering what happens next. If you don't have a structured handoff from sales to service, that silence is where churn starts.

A sales-to-service handoff is the process of moving new customers into your post-sale programme: onboarding, customer success, account management, whatever you call it. The structure we build here uses five components: deals, workflows, tickets, messaging, and surveys. A closed deal triggers a workflow. The workflow creates a ticket in your onboarding pipeline, assigns it to a team member, sends internal and external notifications, and queues up a feedback survey at the end.

This matters because the first 30 to 90 days of a customer relationship are critical. A poor onboarding experience can cause businesses to lose up to 80% of customers within the first week. And 61% of customers say they'd switch brands after just one bad experience. You want their first experience as a customer to be structured, personal, and fast.

Use the closed deal as your trigger

The handoff starts with deals. Deals aren't technically part of Service Hub, but they're the trigger for everything that follows. When a deal moves to "Closed won", that milestone kicks off your post-sale process.

There's a practical reason to use this specific moment: HubSpot has built-in automation that sets all associated contact and company records to the "Customer" lifecycle stage when the deal becomes closed won. Your data is already updated before the service team even gets involved.

Before you build anything, go to CRM > Deals, find your sales pipeline, and confirm the exact name of your closed-won stage. That's all you need from deals. If you don't have access to edit pipeline settings, that's fine. You just need to know what your team calls it.

Create the deal-based workflow

Navigate to Automations > Workflows and create a new workflow from scratch. Choose "Deal-based" as the type. This has to be deal-based because the deal closing is what triggers the ticket creation.

Set the enrollment trigger to: Deal property > Deal stage > is any of > [your pipeline] > Closed won.

For your first version, keep it simple. All closed deals in your sales pipeline flow into this one process. Later, you can add branches for different products, company sizes, or teams. But right now, you want the basic structure working.

The first action in this workflow is "Create record" (under CRM actions). Select "Ticket" as the record type.

Configure the ticket creation

When configuring the new ticket, you need to decide three things: who owns it, what it's called, and where it goes.

Ticket owner. You have three options. First, "Existing owner of the deal" works if you have a service rep listed on the deal record, but that's uncommon. Second, "Specific user" works if you have one person who handles all onboarding, or a manager who manually assigns new clients to the team. Third, leave it blank and handle assignment in a separate ticket-based workflow (more on that in Part 2).

Ticket name. Use a naming convention that makes sense for your business. You can pull in deal properties like company name, so something like "Onboarding for [Company name]" works well.

Pipeline and status. Set this to your onboarding pipeline, first status (typically "New").

Before you save, check the association settings. Associate the ticket with the deal (required), the company (essential for B2B), and contacts (recommended in most cases). Also tick "Add timeline activity" so the ticket inherits activity history from the deal.

Build the assignment workflow

If you left ticket assignment blank in the deal workflow, you need a second workflow to handle it. Create a new workflow from scratch, this time ticket-based.

Set the enrollment trigger to: Ticket property > Status > is "New" in your onboarding pipeline, AND Ticket owner > is unknown.

For assignment, you have two main paths:

Rotation is the most common approach (roughly 90% of HubSpot customers use this). Under CRM actions, choose "Rotate record to owner" and add the users or team you want tickets distributed across. First ticket goes to Alex, second to Lindsay, third to Patrick, then back to Alex.

Branch-based assignment gives you more control. Use an if/then branch based on a property (product type, region, company size) to route tickets to specific reps. This works well when certain reps specialise in certain products or account types.

Add initial outreach and tasks

Once the ticket is assigned, the workflow should prompt immediate action. Add a "Create task" action (under CRM actions) assigned to the ticket owner with a title like "New onboarding ticket assigned: reach out immediately." Set it to high priority.

You can also build your entire onboarding task sequence into this workflow. Add delays between tasks to space them out: a 29-day delay followed by a "30-day check-in" task, then another delay for a midpoint check-in. Each task gets assigned to the ticket owner automatically.

For external communication, you have several options depending on your subscription:

Marketing emails (Marketing Hub Professional or Enterprise): create an automated email and send it to contacts on the ticket through the workflow. This is powerful for welcome emails.

Sequences (Sales Hub Enterprise): enroll the contact in a pre-built sequence of emails and tasks. Good for structured welcome flows.

Templates: pre-written one-to-one emails your reps can send manually from the ticket record. The simplest option if you don't have the subscriptions above.

Use status-based automation

Beyond workflows, you can automate actions at specific ticket statuses. Go to Settings > Data Management > Objects > Tickets > Pipelines, select your onboarding pipeline, and click the "Automate" tab.

Here you can trigger actions when a ticket reaches any status: send a follow-up email after kickoff, create a task when onboarding hits 50%, notify a manager when the handoff call is completed. This keeps your main workflow cleaner and ties automations directly to pipeline milestones.

The handoff you've built here is a starting point. It handles the critical path: deal closes, ticket gets created, rep gets assigned, customer gets notified, and feedback is collected at the end. That alone puts you ahead of most teams who rely on Slack messages and memory.

As your post-sale process matures, you can layer in complexity: different workflows for different products, SLA-based escalation for tickets that go stale, renewal ticket automation, and more sophisticated survey triggers. The foundation you've built supports all of that without restructuring.

The key principle: every closed deal should produce a ticket, every ticket should have an owner, and every customer should hear from you before they have to chase you.