Skip to main content
Intempt
Coming soon

Daily SDR task queue

Build a prioritized report of each SDR's open tasks, ranked by signal strength and recency.

Authored by Sid Chaudhary

Founder & CEO at Intempt

Agentic workflow

Coming soon

4 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.

  1. 1

    Rank every task by signal

    Coming soon

    Blu builds a step

  2. 2

    Cut it to 25 a day

    Coming soon

    Blu builds a step

  3. 3

    Deliver it at 8am

    Coming soon

    Blu builds a step

  4. 4

    Check the ranking is right

    Coming soon

    Blu builds a step

About this recipe

When to use it

Working leads in the order they arrived means the highest-value signal of the day might sit untouched until the afternoon. This ranks the queue by signal strength every morning instead.

What it delivers

Every morning, builds each SDR a prioritized daily task queue ranked by signal strength (PQL, PQA, pricing-page intent, target-account match) and recency, capped at a manageable daily volume.

How you prompt this

Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.

Tell Blu Agent what you want

“Build a prioritized report of each SDR's open tasks, ranked by signal strength and recency.”

recipe.md preview

Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.

Sign up to read the full recipe.md and run it with Blu Agent.

Sign up to see the full recipe

Inputs & outputs

What the recipe needs before it runs, and what it leaves in your workspace.

Inputs

  1. Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.

Outputs

    How the recipe runs

    Blu follows the steps in order and shows you each one before anything goes live.

    1. 01Rank every task by signalCreate an AI-derived attribute 'task_priority_score' on the Task object. Composite: (a) signal source weight: PQA: 50, PQL: 40, pricing-intent: 35, named-account-touch: 30, generic-inbound: 20, cold-outbound-followup: 10; (b) recency multiplier (fresh signal (<24hr) × 1.5, day-2 × 1.0, day-3-7 × 0.7, day-8+ × 0.4; (c) ICP fit boost) ideal-tier accounts × 1.3, viable × 1.0, marginal × 0.5; (d) account size weight: enterprise tier × 1.5. Output: 0-150 score for ranking.
    2. 02Cut it to 25 a dayBuild a report 'SDR daily queue snapshot' computing, per SDR, their top 25 open tasks ranked by task_priority_score, with each task showing: signal source (PQL / PQA / intent), account name, ICP tier, days since signal fired, suggested first-touch angle (based on signal type and account context). Caps queue at 25 because SDR daily-touch capacity is realistically 20-25 outreaches. Use the result of "Rank every task by signal".
    3. 03Deliver it at 8amCreate a scheduled workflow firing every business day at 8am local time per SDR (timezone-aware). Step sequence: (1) refresh task_priority_score across all open SDR tasks (catches new signals from overnight); (2) generate each SDR's top-25 queue; (3) deliver via Slack DM to the SDR with the prioritized list and one-click links to each task; (4) post a team-level summary to the SDR manager: queue-size distribution (any SDR with <10 tasks = underfed, >50 = backlog), top signal sources today, ICP-tier mix. Skip on weekends and holidays. Use the result of "Rank every task by signal", "Cut it to 25 a day".
    4. 04Check the ranking is rightCompose an SDR productivity dashboard: daily-queue delivery rate (% of SDRs receiving their queue daily: operational health), tasks worked per SDR per day vs. queue-size delivered (working-rate), top-of-queue conversion (% of #1-#5 priority tasks that converted to meeting vs. lower-ranked), and rep-leaderboard on signal-to-meeting velocity. Surfaces whether the prioritization model is actually directing SDRs to the right targets. Use the result of "Rank every task by signal", "Cut it to 25 a day", "Deliver it at 8am".

    Install Intempt and run it

    1. 1

      Sign up

      Create a free Intempt workspace.

    2. 2

      Connect your data

      Add the sources this recipe reads from.

    3. 3

      Ask Blu

      Type /daily-sdr-task-queue in Blu once this recipe is live there.

    4. 4

      Review and approve

      Blu builds each step and waits for your OK before anything goes live.

    Related recipes

    Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    More recipes by Sid Chaudhary

    Discovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Post demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Return rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    Got a play worth sharing?

    Publish it to the Intempt Collective Marketplace and earn when other teams run it.

    Submit a recipe