Blocked tasks and raising a blocker

The Blocked tasks hub (/blocked-tasks) aggregates every task flagged with an impediment across all active customer plans, providing customer success teams and managers with a centralized operational center to diagnose and resolve roadblocks.

The operational blocker metric cards

At the top of the Blocked tasks page, three operational metric cards provide immediate visibility into your portfolio's blocked deliverables:

1. Blocked tasks: The aggregate count of all tasks across all active plans currently flagged with the Blocked status.
2. Urgent · 5+ days blocked: The subset of blocked tasks that have remained unresolved for five or more days, highlighting prolonged stalls that threaten contract timelines.
3. Awaiting a customer message: Blocked tasks — of any blocker type — for which no blocker message has been sent yet.

Filtering the blocker queue

The filter strip allows CSMs to slice the queue across three operational dimensions:

• Account selector: Choose All accounts or narrow the list to a single customer organisation.
• Message status: Quick-toggle between Any message status, Message sent, and No message yet to prioritize accounts needing proactive follow-up.
• Blocker type: Filter by the underlying cause:
  • Awaiting Customer Input — Missing data, configurations, or responses from the client team.
  • Awaiting Internal Resource — Engineering, solutions architecture, or executive sponsorship required.
  • Technical Dependency — API rate limits, third-party integrations, or infrastructure provisioning.
  • Approval Pending — Security, legal, or procurement approvals awaiting sign-off.
  • Scheduling Conflict — Workshop, training, or kickoff rescheduling.
  • Other — Uncategorized external impediments.

The operational queue and health state

Below the filter strip, the task list displays all active impediments. When all customer plans are progressing according to schedule with no tasks flagged as blocked, the queue displays the clean operational state: No blocked tasks — all clear.

When blocked tasks are present, each row details:

• Task title and account link: Direct navigation to the task and parent account.
• Plan reference: The parent plan.
• Blocker badge: High-contrast badge indicating the specific blocker type.
• Duration: Days elapsed since the blocker was declared.
• Action triggers: Quick buttons to compose an update email or clear the blocker.

Raising a blocker from the plan detail page

CSMs can declare a blocker from any task row within an active plan at /plans/[id]:

1. Locate the stalled task in the plan's task table.
2. In the row's status dropdown, change the value from Pending or In Progress to Blocked.
3. ValueRamp immediately opens the Block this task modal dialog without changing the database status until confirmed.

The blocker dialog and customer messaging

The Block this task dialog standardizes obstacle reporting across the organization:

1. Blocker type (required): Select one of the six standardized categories from the dropdown.
2. Blocker reason (optional, required for Other): Provide specific context explaining what is missing, who is holding up progress, or what technical dependency is failing.
3. Action options:
   • Cancel: Closes the dialog and restores the task to its previous status.
   • Save: Confirms the blocked status internally without sending external communications.
   • Save & message customer: Saves the blocker and immediately launches the Blocker Composer, pre-filling an email draft to the customer sponsor explaining the obstacle and next steps needed.