Skip to content
The Workflow Library
Get the full library

Submission chase and escalation when a client gives no feedback

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.

Deal16 stepsUpdated for HubSpot seat pricing
OutcomeA candidate sent to a client is chased on a schedule instead of on memory, and after two silent rounds the account owner is told, so a submission either moves or is closed on purpose.
Workflow maprecruiting-002
Deal stage Submitted and pipeline type placement leads to Stamp submission date, chases = 0. Stamp submission date, chases = 0 leads to Delay 3 business days. Delay 3 business days leads to Still in Submitted?. Still in Submitted? leads to No: End, client answered; Yes: Chase task to recruiter, chases = 1. Chase task to recruiter, chases = 1 leads to Delay 2 business days. Delay 2 business days leads to Still in Submitted?. Still in Submitted? leads to No: End, client answered; Yes: chases = 2, notify recruiter and account owner. chases = 2, notify recruiter and account owner leads to Call task to account owner. Call task to account owner leads to Delay 3 business days. Delay 3 business days leads to Still in Submitted?. Still in Submitted? leads to No: End, client answered; Yes: Notify manager, decision task, chases = 3. No Yes No Yes No Yes Deal stage Submitted and pipeline type placement Stamp submission date, chases = 0 Delay 3 business days Still in Submitted? Chase task to recruiter, chases = 1 Delay 2 business days Still in Submitted? chases = 2, notify recruiter and account owner Call task to account owner Delay 3 business days Still in Submitted? Notify manager, decision task, chases = 3 End, client answered
Deal stage Submitted and pipeline type placement leads to Stamp submission date, chases = 0. Stamp submission date, chases = 0 leads to Delay 3 business days. Delay 3 business days leads to Still in Submitted?. Still in Submitted? leads to No: End, client answered; Yes: Chase task to recruiter, chases = 1. Chase task to recruiter, chases = 1 leads to Delay 2 business days. Delay 2 business days leads to Still in Submitted?. Still in Submitted? leads to No: End, client answered; Yes: chases = 2, notify recruiter and account owner. chases = 2, notify recruiter and account owner leads to Call task to account owner. Call task to account owner leads to Delay 3 business days. Delay 3 business days leads to Still in Submitted?. Still in Submitted? leads to No: End, client answered; Yes: Notify manager, decision task, chases = 3. No Yes No Yes No Yes Deal stage Submitted and pipeline type placement Stamp submission date, chases = 0 Delay 3 business days Still in Submitted? Chase task to recruiter, chases = 1 Delay 2 business days Still in Submitted? chases = 2, notify recruiter and account owner Call task to account owner Delay 3 business days Still in Submitted? Notify manager, decision task, chases = 3 End, client answered

When to use it, when not to

Use it

  • Use it on the placement pipeline once a Submitted or Shortlist sent stage exists and a deal is created per candidate per vacancy.
  • Use it when the feedback window is written into the terms of business, or when you are ready to pick a default of five working days.
Read more on when to use itShow less

Skip it

  • Do not use it on the business development pipeline. A deal there is a mandate, not a candidate, and the enrollment filter on Pipeline type is what keeps the two apart.
  • Do not use it when one deal carries the whole vacancy and several candidates. The chase text and the counter both assume one candidate per deal, otherwise a single reply closes chases for people the client never saw.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 7 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 · 16 numbered actions

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

Known pitfalls · 6

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

Test plan and UAT script · 6 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.

Not the workflow you needed?

More in the Staffing and recruiting kit

43 specs in this kit

See the kit
Candidate assignment to the right recruiter by skill and availability, with a first-contact SLAContact24 steps Guarantee period end check and candidate redeploymentDeal14 steps Deal without an associated contact flagDeal7 steps Duplicate open-deal detection per companyDeal7 steps

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