Voice campaigns fail in the handoff. Marketing sees dials. Sales opens HubSpot and finds a blank task, a 40-minute transcript, or a note that says "connected, follow up." RevOps gets blamed. The fix is not more calls. It is a written standard for lead briefs and HubSpot writeback every motion must follow.
This document is the RevOps spec Nudgy customers use before they scale reactivation, speed-to-lead, or webinar follow-up. Copy the templates, approve the field map, and enforce one outcome format across every voice touch.
A lead brief is an internal email to the HubSpot owner. It merges CRM fields with conversation signals. It is not a cold outreach email to the prospect and it is not a substitute for making the call first.
Who this standard is for
- RevOps and sales ops defining what voice must write back before SDRs dial at scale.
- HubSpot admins creating custom properties, note templates, and workflow triggers.
- SDR and AE managers who need consistent handoffs, not ad hoc call summaries.
- Marketing ops proving campaign attribution survives the voice layer.
What is the lead brief + writeback standard?
Definition
The lead brief and HubSpot writeback standard is a fixed set of sections for internal rep handoffs (lead brief email), timeline notes, optional custom properties, and optional owner tasks. Every voice or SMS motion in the Reactivation Loop uses the same structure so reporting and rep behavior stay predictable.
The writeback stack
The Reactivation Loop ends with Brief and Note. This diagram adds Extract, Properties, and Task so RevOps can see the full stack:
Writeback standard
From conversation to rep-ready HubSpot record
- 1
Conversation
Voice or SMS touch with CRM context in the motion.
- 2
Extract
Structured signals: outcome, intent, blockers, next step.
- 3
Brief
Internal email to hubspot_owner with merged CRM + call data.
- 4
Note
Timeline note on the contact (auditable, searchable).
- 5
Properties
Optional custom fields for dashboards and routing.
- 6
Task
Optional owner task when human action is required.
Full loop context (List through Note):
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.
Why inconsistent writeback kills voice ROI
| Handoff style | What sales sees | Result |
|---|---|---|
| Raw transcript in CRM | Wall of text, no next step | Rep skips or re-dials blind |
| Dialer disposition only | Connected / no answer badge | No intent or blocker data |
| Unstructured rep notes | Varies by rep | Unreportable, untrainable |
| Standard brief + note | Outcome, summary, blocker, next step | Rep acts; RevOps reports |
Step 1: Know the four artifacts
| Artifact | Audience | Purpose |
|---|---|---|
| Lead brief (email) | HubSpot owner / SDR | Actionable handoff in inbox with CRM link |
| Timeline note | Anyone on the contact record | Auditable history, search, compliance |
| Custom properties | RevOps dashboards | Filter, route, report at scale |
| Owner task | Rep queue | Explicit human action with due date |
Rule: lead briefs assume a conversation happened. Do not send a brief for a cold HubSpot row with no call or SMS outcome.
Step 2: Lead brief email standard (copy this)
Subject line pattern: [Nudgy] {motion_name} · {company} · {outcome}
Contact: {firstname} {lastname} · {company}
HubSpot: {contact_record_url}
Owner: {owner_name}
Motion: {motion_name} · {motion_date}
OUTCOME
{connected | no_answer | voicemail | opt_out}
Meeting interest: {high | medium | low | n/a}
SUMMARY (2-4 sentences)
{What they said in their words: intent, urgency, role, evaluation status}
BLOCKER
{Single clearest blocker, or "None stated"}
RECOMMENDED NEXT STEP
{One action: book meeting, send asset, nurture, suppress}
CRM CONTEXT USED
{lifecycle}, {source/campaign}, {last_activity}, {list_or_form}
RECORDING
{link to conversation system, not pasted in CRM}Step 3: HubSpot timeline note standard
Notes must mirror the brief sections so timeline search matches inbox handoffs. Use a prefix tag for filtering:
[Nudgy {motion_slug} | {YYYY-MM-DD}]
Outcome: {Connected | No answer | Voicemail | Opt out} · Meeting interest: {High | Medium | Low}
Summary: {2-3 sentences, buyer language}
Blocker: {one line}
Recommended next step: {one line}
CRM context used: {source, lifecycle, list or form}
Follow-up permission: {Yes | No | Not asked}Filled example
[Nudgy reactivation | 2026-05-26] Outcome: Connected · Meeting interest: High Summary: VP Ops at Acme Corp. Still evaluating workflow tools after Q1 budget freeze lifted. Wants HubSpot writeback comparison and security doc before booking. Blocker: Needs SOC 2 summary 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. Follow-up permission: Yes
Do not paste full transcripts into HubSpot by default. Link to your conversation system; write structured outcomes to CRM.
Step 4: Recommended HubSpot custom properties
Start with notes only for week one. Add properties when RevOps needs dashboards or workflow branches.
| Property | Type | Use |
|---|---|---|
| nudgy_last_touch_date | Date | Suppression: do not re-dial within N days |
| nudgy_last_outcome | Dropdown | Connected, no answer, voicemail, opt out |
| nudgy_meeting_interest | Dropdown | High, medium, low |
| nudgy_last_motion | Single-line text | Which playbook ran (reactivation, speed-to-lead, etc.) |
| nudgy_follow_up_permission | Dropdown | Yes, no, not asked |
| nudgy_primary_blocker | Single-line text | Top blocker for reporting |
| nudgy_recommended_next_step | Single-line text | Machine-readable next action |
Step 5: Writeback maturity tiers
| Tier | Includes | When |
|---|---|---|
| Tier 1 (MVP) | Timeline note only | First 10 to 50 contact pilot |
| Tier 2 (Standard) | Note + lead brief email | Sales confirms note quality |
| Tier 3 (Scaled) | Note + brief + core properties | RevOps needs reporting |
| Tier 4 (Automated) | Tier 3 + tasks + workflow branches | Multiple motions in production |
Step 6: RevOps approval checklist (before scale)
- Field map signed off (HubSpot properties in, writeback properties out)
- Note template pasted in internal wiki and linked from motion docs
- Lead brief routes to hubspot_owner_id, not a shared inbox
- Suppression property set (nudgy_last_touch_date or equivalent)
- Opt-out path documented and honored in HubSpot within 24 hours
- Sandbox or scoped pilot list tested before production enrollment
- Sales manager reviewed 5 sample notes and confirmed next steps are actionable
Step 7: When to create an owner task
| Scenario | Task? | Task title pattern |
|---|---|---|
| High meeting interest + follow-up yes | Yes | Book meeting: {company} (Nudgy voice) |
| Requested security/pricing pack | Yes | Send asset: {blocker} for {company} |
| No answer / voicemail | No | Note only; retry policy handles re-dial |
| Nurture only, 90+ day timeline | No | Note + lifecycle tag; no SDR task |
| Opt out | No | Suppress + note; no task |
What not to write back
- Full call transcripts in the timeline note (link out instead)
- AI confidence scores or internal model metadata sales cannot act on
- Duplicate notes on every retry attempt (one note per meaningful outcome)
- Lifecycle stage changes without RevOps-approved rules
- Pricing quotes or commitments the voice motion is not authorized to make
Metrics for writeback quality
| Metric | Target |
|---|---|
| Note coverage (connected calls) | 100% |
| Notes with all required sections | 95%+ in pilot review |
| Brief delivered to correct owner | 100% |
| Rep-reported handoff quality (sample survey) | 4/5 or higher before Tier 3 |
| Time from call end to note in HubSpot | Under 5 minutes median |
FAQ
Lead brief vs timeline note: do we need both?
Tier 2 and above: yes. The brief gets immediate attention in the owner inbox. The note is the durable audit trail on the contact record.
Can we skip the lead brief and only write notes?
Yes for Tier 1 pilots. Add briefs when sales says they miss handoffs in email or Slack.
How does this connect to the stale MQL playbook?
Every motion playbook ends with the same writeback shape. This article is the canonical template those playbooks reference.
Salesforce instead of HubSpot?
Same section structure applies. Map to Salesforce tasks, activity history, and custom fields. Prove HubSpot first if that is your primary CRM.
Who owns the standard?
RevOps owns the field map and note template. Marketing owns motion names and campaign attribution lines. Sales signs off on next-step language.
What if writeback fails?
Queue failed writes, alert ops, and replay after mapping fix. Never silently drop outcomes; reps will re-dial and erode trust.
When do we add custom properties?
When you need filters or dashboards on outcomes (meeting interest, blockers, motion type). Notes alone are enough for the first pilot.
See structured writeback on your stack
Work email and mobile required. Demo call plus recap, framed like a post-conversation lead brief handoff.
Describe your writeback gap. Nudgy will call you and show what a structured handoff looks like after a voice touch.