Loading tutorials…
Loading tutorials…
Tasks are how HubSpot enforces sales discipline. Set them up right and reps work a tight daily list. Set them up wrong — too many tasks, vague descriptions, no queues — and tasks become noise reps ignore. Here is the discipline that holds up.
Who this is forSales managers, RevOps leads, and founders running sales who need consistent rep activity. If your reps say 'I'm too busy to log calls' or your task list shows 200 overdue tasks per rep, this tutorial is for you.
What you'll need
Step 1
Tasks are for actions with a specific deadline that, if missed, has cost. Not for "follow up sometime" wishes.
Good task candidates: 'Call back contact X by EOD tomorrow,' 'Send proposal to deal Y by Friday,' 'Follow up on demo with Z within 48h.'
Bad task candidates: 'Check in with everyone in pipeline,' 'Reach out to old leads' — these are activities, not tasks. They belong in saved-list filters, not the task list.
Rule of thumb: a task should have one clear action + one specific date. If you cannot write "DO X BY Y," it is not a task.
Bad task design = 200+ overdue tasks per rep within 60 days. At that point, reps stop trusting the list and the system collapses.
Step 2
Sales tools → Tasks → Task queues. A queue is a saved list of tasks reps work through in order. Used heavily by SDRs.
Open Sales tools menu → Tasks → click "Manage queues."
Create queues by workflow: "Cold Calling — Today," "Demo Follow-up," "Renewal Outreach," "Re-engagement."
Set queue criteria: filters that determine which tasks land in the queue. Example: 'Task type = Call AND Task owner = me AND Task due date = today.'
Reps work a queue by clicking "Start queue" — HubSpot opens the first task, lets them complete it (log call, send email), then auto-advances to the next.
Queues are the difference between "I have 47 tasks today" and "I work through these 12 calls in this order in the next 90 minutes." The cognitive load drop is enormous.
Step 3
Workflows can create tasks based on triggers. New deal in stage X → create call task. New form submission → create follow-up task. Manual task creation is the slow path.
Open Automation → Workflows → Create workflow → Contact-based or Deal-based depending on trigger.
Example 1 — Demo Follow-up: trigger = deal stage changes to "Demo Completed." Action = create task: type = Call, title = "Demo follow-up call: {{deal.dealname}}," due in 1 business day, owner = deal owner.
Example 2 — Form submission follow-up: trigger = contact submits "Request a Demo" form. Action = create task: type = Email, title = "Schedule demo with {{contact.firstname}}," due in 4 hours, owner = round-robin SDR.
Example 3 — Stalled deal recovery: trigger = deal in "Proposal Sent" stage for 14 days with no activity. Action = create task: type = Call, title = "Check in: proposal sent 2 weeks ago," due today, owner = deal owner.
Set re-enrollment OFF on these workflows. Otherwise a single deal can spawn 5 duplicate follow-up tasks.
Step 4
A task without an SLA is a suggestion. Define how long reps have to complete tasks of each type, and what happens when they miss.
Common SLAs: Inbound demo request → respond within 4 business hours. Cold call task → complete within 24 business hours. Demo follow-up → complete within 1 business day.
Build an "Overdue task" workflow: trigger = task overdue by more than X hours. Action = notify task owner AND notify their manager.
For inbound leads, build a faster escalation: task overdue > 4 hours → reassign to backup rep automatically.
Track task-completion rate per rep in a Custom Report (Sales Hub Pro+). Reps consistently under 70% need coaching, not more tasks.
The point of SLAs is not punishment; it is making activity visible. Reps with bad SLA performance often have bad task lists they cannot realistically complete.
Step 5
Default HubSpot notifications fire on every task creation, mention, and update. Tune them or reps will mute HubSpot entirely.
Settings (gear icon) → Notifications. Configure per user (or set a default that users can override).
Recommended defaults: in-app notification for task created (yes), email notification for task overdue (yes), email for task created (NO — too noisy), push notification for task assigned (yes for mobile users).
For task summaries: enable daily digest emails (Settings → Notifications → Email digest) — reps get one daily summary instead of 30 individual notifications.
Slack integration: route task overdue alerts to a sales-ops Slack channel, not individual DMs. Visibility creates social pressure to complete.
Step 6
Reports → Custom report builder → Tasks. Track completion rate, overdue count, and tasks-per-rep by week.
Reports → Reports → Custom report builder (Sales Hub Pro+). For free / Starter, use the predefined Task report.
Build a report: "Tasks completed in last 7 days by owner" with task type, due date, and completion timestamp.
Pin this to your sales-ops dashboard. Review weekly: who is at <70% completion, who has 50+ overdue tasks, which task types are getting skipped.
If a rep has 100+ overdue tasks, do not push them to "catch up" — clear the backlog and rebuild the task system. Overdue piles are a system signal, not a rep signal.
Look at task type breakdowns: if 'Call' tasks have 90% completion but 'Email' tasks have 40%, the issue is task design (emails should probably be in sequences, not tasks).
Step 7
A Playbook attaches a structured script + fields to a task. Used for discovery calls, demos, qualifying conversations.
Sales tools → Playbooks → Create playbook (Sales Hub Pro+).
Build the script: structured sections (Intro, Discovery questions, Pain points, Next steps), each with note-taking fields that map to deal/contact properties.
Associate the playbook with task types: when a rep starts a "Discovery Call" task, the playbook surfaces in-line, they take notes as they go, and the data writes back to the deal record automatically.
Playbooks lift consistency (every discovery call follows the same structure) and data hygiene (key fields get populated mid-call instead of forgotten).
Common playbooks worth building: Discovery Call (15-25 fields), Demo Recap (5-10 fields), Qualification Decision (Go/No-go criteria), Closing Call.
Common mistakes
Creating tasks for everything reps should do
What goes wrong: Reps get 80+ tasks per week. 60 are 'follow up someday' style. 20 are real. The signal-to-noise ratio collapses. Reps mark everything done without doing it, or ignore the task list entirely.
How to avoid: Tasks = specific action + specific date. For "follow up sometime" needs, use a saved list filter or a workflow with delays, not a task.
No task queues, every rep manages their own task list ad-hoc
What goes wrong: SDRs cherry-pick easy tasks and ignore hard ones. Daily call counts drop. Manager cannot see who is working what. 1:1s become 'what did you do this week?' instead of accountability.
How to avoid: Build queues for repetitive workflows (Cold Calling, Demo Follow-up, Renewal Outreach). Reps work the queue in order. Queue start/stop times are visible to managers.
Manually creating every task instead of automating from workflows
What goes wrong: Reps forget to set follow-up tasks. Half of deals lose follow-up cadence. Pipeline coverage drops because tasks that should auto-fire on stage change never get created.
How to avoid: Every stage transition that needs a follow-up gets an automation. Workflows → trigger on stage change → create task with type, owner, due date, and clear title.
Re-enrollment ON for task-creating workflows
What goes wrong: Workflow that creates 'Follow up' task fires every time the deal updates. One deal generates 6 duplicate tasks. Rep is confused which is current. Task list becomes a duplicate-stew.
How to avoid: Re-enrollment OFF on task-creating workflows. If the deal genuinely needs another follow-up later, the next stage transition creates a new task.
No SLA tracking on tasks
What goes wrong: Inbound leads get tasks created but reps complete them whenever. A demo request that should be responded to in 4 hours sits for 3 days. Lead converts to a competitor. The task system 'worked' but the SLA didn't exist.
How to avoid: Define SLAs per task type. Build overdue-task workflows that notify and escalate. Track SLA compliance per rep in a weekly report.
Notification firehose burns reps out
What goes wrong: Reps get 80 HubSpot notifications per day. They turn off all HubSpot notifications. Now real escalations (overdue task, urgent assignment) are invisible. The system is muted.
How to avoid: Tune notifications: in-app for creations, email only for overdues, daily digest for summaries. Route ops escalations to a Slack channel instead of personal DMs.
Recap
Done — what's next
How to set up HubSpot sales sequences without burning your sender reputation
Read the next tutorial
Hand it off
A working task system is the difference between a CRM that drives rep behavior and one that just stores it. Specialists who have built task discipline for 30+ teams know which triggers to automate, which SLAs to enforce, and how to design queues reps actually run. EverestX HubSpot specialists run $400-1,200/mo at $14-16/hr.
See specialist rates
An activity is a record of something that happened (logged call, sent email, meeting held). A task is a planned action to take. Tasks become activities when completed. Both show up on contact / deal record timelines. Use tasks for 'must do' items; activities are the historical record.
Yes — Sales Hub Pro+. Settings → Users & Teams → Teams → enable round-robin assignment. In a workflow, set task action → "Owner = round-robin from [Team]." HubSpot distributes new tasks evenly across the team. Useful for distributing inbound leads or follow-up tasks across an SDR pod.
HubSpot tasks show up in your Today view inside HubSpot, but they do not natively sync to Google Calendar / Outlook Calendar (HubSpot meetings do, tasks do not). For task-to-calendar sync, use the Zapier HubSpot connector or third-party tools like Sequel or Akin. Many reps just use Today view as their daily task plan.
For sales-rep tasks (call this lead, follow up on this deal), use HubSpot — tasks are tied to records and roll up into pipeline reports. For project-management tasks (build a website, launch a campaign), use a dedicated PM tool. Mixing the two confuses reps about where to look.
Yes (2026 feature). Breeze Copilot can suggest tasks based on deal activity ('this deal has not had activity in 14 days, suggest follow-up call'), draft task descriptions, and prioritize the task queue based on deal value + recency. Available on Sales Hub Pro+. Treat its suggestions as a starting point, not a substitute for rep judgment.
HubSpot CRM
Sequences are the most-loved Sales Hub feature and the one most teams break in the first month. Too many tokens, too aggressive a cadence, no exit criteria — and you have a churning sequence that buries your inbox in bounces. Here is the discipline that earns meetings.
HubSpot CRM
A HubSpot pipeline is the single most-referenced screen in the CRM. Set up wrong, the forecast number is fiction and reps stop trusting it. Set up right, the CRO walks into Monday with a real number. Here is the discipline that holds up.
HubSpot CRM
Snippets and templates are the difference between a sales team that types every email from scratch and one that operates at 3x velocity. Most teams build a chaotic library of 80 templates in month one and abandon it by month three. Here is the discipline that keeps the library alive.
HubSpot CRM
DIY HubSpot CRM is a great idea — until it isn't. This is the honest framework for when the cost of self-managing exceeds the cost of hiring help, and how to tell which side you are on.