Demo request fast path
Enriches a demo request the moment it lands, puts a same day task on the right AE, and posts it to Slack, aiming for first contact inside an hour.
Authored by Intempt Technologies
Recipe curators
Agentic workflow
Coming soon4 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Find recent demo requests
Coming soonBlu builds a step
- 2
Write the triage card
Coming soonBlu builds a step
- 3
Route it inside the hour
Coming soonBlu builds a step
- 4
Hold the response time
Coming soonBlu builds a step
About this recipe
When to use it
Demo requests are high-intent by definition, but a slow follow-up wastes that intent. This fires enrichment and an AE task the moment the form lands, instead of waiting for a queue to catch up.
What it delivers
When a prospect submits a demo form, fires instant account enrichment, creates a high-priority AE task, and pings Slack - moving from request to AE outreach in under an hour.
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
“Enriches a demo request the moment it lands, puts a same day task on the right AE, and posts it to Slack, aiming for first contact inside an hour.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- 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.
- 01Find recent demo requestsBuild a segment 'Demo Requesters - last 7 days' capturing users with Form submitted event where form_type = demo_request in the last 7 days. Used by the routing workflow to identify which users should hit the fast-path and excluded from standard nurture journeys for the duration of the fast-path window.
- 02Write the triage cardGenerate Slack alert content for the #demo-requests channel. Include: requester name, account name, employee count, industry, deal-size estimate (if available), prior touch history (last engagement, ICP fit score), and a direct link to the user record. Tone: terse, scannable: this is a triage card, not a marketing message. Use the result of "Find recent demo requests".
- 03Route it inside the hourCreate a workflow firing on Form submitted where form_type = demo_request. Step sequence: (1) enrich account via firmographic lookup if not already enriched; (2) compute ICP fit score and store as user attribute; (3) for high-fit ICPs (score >= 70), create a high-priority AE task due same-day with the prospect's contact info, account context, and form responses pre-attached; (4) post the alert content to Slack #demo-requests. For low-fit ICPs, drop into self-serve nurture journey instead. Use the result of "Find recent demo requests", "Write the triage card".
- 04Hold the response timeCompose a dashboard tracking the demo-request response funnel: Form submitted to task_created to Task completed to Meeting scheduled. Surface median + p75 time from Form submitted to AE first-touch (SLA metric: target: under 60 minutes during business hours). Break down by ICP fit tier (high/med/low) and by AE owner. Add a card flagging any demo request open >2 hours without a task completion. Use the result of "Find recent demo requests", "Write the triage card", "Route it inside the hour".
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /demo-request-fast-path in Blu once this recipe is live there.
- 4
Review and approve
Blu builds each step and waits for your OK before anything goes live.
