You already paid for those MQLs. They sit in HubSpot with phone numbers, lifecycle stages, and campaign history. Nobody called. This playbook shows how to reactivate a stale segment with context-rich voice, a short SMS recap, and a rep brief that lands back in CRM.
This is not a dialer tutorial. Nudgy is a context layer on top of HubSpot: pick a segment, reach each contact with CRM-aware voice, capture what happened, and give your rep a handoff they can act on without rereading six tabs.
If you run demand gen or RevOps on HubSpot, use this as a working spec. Filters, property maps, note templates, and metrics are included so you can pilot on 10 to 50 contacts before you scale.
Who this playbook is for
- RevOps and sales ops who own MQL definitions, routing, and CRM hygiene.
- Demand gen leads who built the campaigns that sourced the list and need meetings, not more email touches.
- HubSpot admins who can create active lists, custom properties, and note templates.
- Agencies running voice as a per-portal add-on for clients (see agency motion).
What is a stale MQL?
Definition
A stale MQL is a HubSpot contact whose lifecycle stage is Marketing Qualified Lead (or equivalent), who has a reachable phone number, who has not booked or attended a sales meeting, and whose last meaningful activity (email reply, form fill, call, or meeting) is older than your SLA window (often 14 to 30 days).
Stale does not mean bad. It usually means bandwidth. Marketing sourced intent. Sales never had time, or the record never had enough context for a confident dial. The fix is not another batch email. It is a fast, personalized touch that enriches the record before a human takes over.
The Reactivation Loop
Nudgy names the full motion the Reactivation Loop. It is the end-to-end workflow this playbook implements: not a product button, but the six steps your team runs for every stale segment.
Read the diagram once, then follow Steps 1 through 5 later in this article for the HubSpot specifics (filters, fields, scripts, and writeback).
Playbook overview
Six steps from HubSpot list to rep-ready CRM record
- 1
List
Build a HubSpot active list (stale MQLs with phone numbers).
- 2
Context
Pull name, company, lifecycle, and campaign into the call script.
- 3
Voice
Outbound call with a clear goal: book a meeting or capture blockers.
- 4
Recap
Short SMS to the lead confirming what you discussed.
- 5
Brief
Internal email to the HubSpot owner with signals and next step.
- 6
Note
Timeline note (and optional properties) on the contact record.
- List: Active list or static segment in HubSpot with filters you can explain to legal and sales.
- Context: Selected properties injected into the voice motion (name, company, lifecycle, last activity, campaign, owner).
- Voice: Outbound call with a defined goal (confirm interest, book meeting, capture blocker).
- Recap: Short SMS to the lead summarizing the call and next step.
- Brief: Internal email to the HubSpot owner with structured signals and recommended follow-up.
- Note: HubSpot timeline note (and optional custom properties) so the touch is auditable in CRM.
Lead briefs alone are not the entry point for cold CRM rows. Briefs assume a conversation happened. This loop creates that conversation first, then briefs the rep.
Why HubSpot sequences stall on stale MQLs
Sequences and workflows excel at repeatable email and task steps. They struggle when the missing ingredient is first-person context: timing, blockers, budget language, and tone. A stale MQL row often has score and campaign name but no answer to "why now?"
| Channel | What it captures | Gap on stale MQLs |
|---|---|---|
| Email sequence | Opens, clicks, replies | No urgency or objection language when they do not reply |
| SDR manual dial | Rich when connected | Slow at scale; rep dials blind without fresh context |
| Voice + CRM context | Intent, blockers, meeting readiness, verbatim buyer language | Requires consent discipline and writeback habit |
Industry benchmarks vary by segment, but B2B studies consistently show that response rates drop sharply after the first hour without contact. Voice reactivation is how teams close that gap when SDR headcount does not.
Step 1: Build your HubSpot reactivation list
Start with one narrow segment. Prove the loop on 10 to 50 contacts with mobile numbers before you expand.
Example active list filters
Lifecycle stage is any of: Marketing Qualified Lead AND Last activity date is more than 30 days ago AND Phone number is known AND Mobile phone number is known (optional, stricter) AND Marketing contact status is Marketing contact AND NOT Lead status is any of: Unqualified, Bad timing AND NOT Associated deal exists in Open stage (optional)
Segment variants that work well
- Demo requested, no meeting held: form or calendar intent without completion.
- Event or webinar MQLs 14+ days idle: attended or registered but no opp.
- Content download MQLs with score threshold: high fit on paper, no talk track in CRM.
Export a preview row before you dial: first name, company, lifecycle, last activity date, original source, latest campaign, owner. If those fields are empty for most of the list, fix data before you add voice. For enrollment paths, QA checklists, and pacing, see the HubSpot list to outbound voice guide.
Step 2: Map HubSpot properties into call context
The call should never open with "Hi, I'm calling from a company." The opener references what HubSpot already knows. Map a small set of fields once and reuse them on every reactivation motion.
| HubSpot property | Use in voice motion |
|---|---|
| firstname | Personalized greeting |
| company | Account reference and role context |
| lifecyclestage | Qualification framing (MQL vs SQL) |
| hs_lastmodifieddate / notes_last_contacted | Recency language ("it has been a few weeks") |
| hs_analytics_source / latest source | Why they entered your world |
| hs_latest_source_data_1 | Campaign or content name |
| hubspot_owner_id | Route brief and task to the right rep |
| phone / mobilephone | Dial priority (prefer mobile for connect rates) |
Optional custom properties to add later: nudgy_last_touch_date, nudgy_reactivation_outcome, nudgy_meeting_ready. Start with a timeline note only if you want the smallest viable writeback.
Step 3: Design the voice motion
One motion, one goal. For stale MQL reactivation, the default goal is confirm interest and book a meeting, with a fallback of capture blocker and timeline when they are not ready.
Motion template (internal spec)
Opener: Reference company and how they engaged (campaign or content from HubSpot). Ask if now is still a good time to talk about [topic].
Discovery (max 2 questions): What prompted their interest? What would need to be true to take a next step this quarter?
Close: Offer a 20-minute meeting with the HubSpot owner, or agree on a follow-up date and blocker summary.
Guardrails: No pricing commitments. Escalate legal or security questions to the rep. Respect do-not-call requests immediately.
Consent and jurisdiction matter. For US B2B outbound to business contacts who raised their hand, document your basis (inbound lead, event opt-in, etc.) and honor opt-outs in HubSpot before you launch. When in doubt, scope with counsel.
Step 4: Send the SMS recap to the lead
After a connected call, a short SMS recap beats a long email. It confirms what was discussed and gives one clear next action.
Keep it under 320 characters when possible. Match the regional sender your team already uses for transactional SMS. Log the send against the contact in HubSpot (note or activity).
Step 5: Lead brief and HubSpot note
The rep handoff is where Nudgy differs from dialers. The internal brief merges HubSpot fields with conversation signals: intent, urgency, objections, and recommended next step.
Sample HubSpot timeline note
[Nudgy reactivation | 2026-05-05] Outcome: Connected · Meeting interest: High Summary: VP Ops at Acme Corp. Still evaluating workflow tools after Q1 budget freeze lifted. Wants comparison on HubSpot writeback and security doc before booking. Blocker: Needs SOC 2 summary sent before scheduling. Recommended next step: Owner sends security pack + books 20 min with solutions engineer. CRM context used: MQL from webinar "RevOps 2026", last activity 34 days ago.
Do not paste raw transcripts into CRM by default. Reps want decisions, not noise. Store full recordings and transcripts in your conversation system; write structured outcomes to HubSpot. For the full lead brief email template, property map, and maturity tiers, see the lead brief and writeback standard.
Metrics for your first pilot
| Metric | What good looks like (pilot) |
|---|---|
| Dial attempt rate | 90%+ of approved list |
| Connect rate | Varies by segment; track mobile vs office |
| Meeting or qualified follow-up | At least one booked meeting from 10 to 20 dials |
| Time to first touch | Minutes to hours, not days |
| CRM note coverage | 100% of connected calls get a note or property update |
FAQ
How is this different from an AI dialer?
Dialers optimize connect volume. Nudgy optimizes context: HubSpot fields in the motion, structured extraction after the call, SMS recap, internal brief, and CRM note. The unit of value is a rep-ready record, not an answered phone badge.
Do we need Nudgy line history before we can run this?
No. Reactivation uses CRM context first. Lead briefs that merge prior Nudgy calls help on contacts you already touched through Nudgy; cold HubSpot rows start with HubSpot properties and the conversation you just had.
HubSpot only, or Salesforce too?
This playbook is HubSpot-first. The same loop applies to Salesforce lists once field mapping is scoped. Prove one CRM before you parallelize.
What list size for a first pilot?
10 to 50 contacts with mobile numbers and clean owner assignment. Learn connect rates and note quality before you run hundreds.
Can we use workflows to trigger calls automatically?
Yes, once list rules and consent are documented. Many teams start with a manual approved list, then automate enrollment when writeback and governance are stable.
What should we write back first: note or custom properties?
Start with a timeline note. Add custom properties when RevOps wants reporting on reactivation outcomes in dashboards.
Where does Nudgy fit in our stack?
HubSpot remains system of record. Nudgy is the voice and SMS execution layer with writeback. n8n handles automation behind the scenes for many deployments.
Run this playbook on your stack
Submit your work email and mobile. You will get a short demo call framed like a stale MQL reactivation touch, plus a recap.
Describe your HubSpot segment. Nudgy will call you with the same motion your reps would get after a reactivation campaign.
Sources and further reading
- HubSpot for Voice: A New Category
- First-Person Data: From First-Party to First-Person
- RevOps: stale MQL and inbound gap motions
- HubSpot Academy and demand gen benchmarks on lead response time (search "HubSpot lead response study" for current editions).