Skip to content

Cross-department kickoff briefing notification

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Sales Hub Professional.

Deal3 stepsUpdated for HubSpot seat pricing
OutcomeAt kickoff, customer success, support, and billing all get the same consolidated briefing in one notification, instead of three separate department-specific alerts each missing context the others have.
Workflow mapcustomer-onboarding-050
Deal stage = Closed Won, briefing not yet sent leads to Send consolidated notification to CS, support, billing. Send consolidated notification to CS, support, billing leads to Create matching note on deal timeline. Create matching note on deal timeline leads to Set Kickoff Briefing Sent Date. Deal stage = Closed Won, briefing not yet sent Send consolidated notification to CS, support, billing Create matching note on deal timeline Set Kickoff Briefing Sent Date
Deal stage = Closed Won, briefing not yet sent leads to Send consolidated notification to CS, support, billing. Send consolidated notification to CS, support, billing leads to Create matching note on deal timeline. Create matching note on deal timeline leads to Set Kickoff Briefing Sent Date. Deal stage = Closed Won, briefing not yet sent Send consolidated notification to CS, support, billing Create matching note on deal timeline Set Kickoff Briefing Sent Date

When to use it, when not to

Use it

  • Use it when a new customer genuinely needs more than one department aware at kickoff, and today each department either finds out separately (see customer-onboarding-001 for CS, customer-onboarding-030 for finance, customer-onboarding-022 for delivery) or does not find out at all.
  • Use it as the consolidated version of those single-department fiches, not a replacement for them, some teams want both a targeted alert and a shared briefing.
Read more on when to use itShow less

Skip it

  • Do not use it if only one department actually needs to know at this point, use the specific fiche for that department instead (customer-onboarding-001, 022, or 030), a briefing to everyone when only one team needs to act creates noise.
  • Do not use it for deals below a certain size if the extra visibility is not worth the notification volume, add an amount filter to the enrollment criteria if that is the case.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 6 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 3 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 2 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Customer onboarding spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library