The decline is part of the product experience
Demo requests arrive mixed: real buyers, students writing a thesis, competitors looking at the product, and people who need a different product entirely. Treating them identically spends the rep's week on the wrong third of the list.
Declining badly is the more expensive mistake. The person who needed a different product talks to others, and an honest redirect costs one sentence while silence costs whatever they say about you.
Prioritizing is the easier half and is still usually undone: ordering qualified requests by fit means the best one gets the first slot rather than the one that arrived at nine in the morning.
Keeping a person on the decline branch for the first few weeks is not caution for its own sake. Reading fifty decisions is how you find out the criteria were wrong.
How the ActionFlow runs on the canvas
Every demo request is triggered by a Webhook from the form.
An HTTP Request node enriches the company's data before any judgment is made, because a work email alone rarely supports a qualification decision.
A Generate Object node qualifies against your criteria and returns a fit level, a reason, and (for anything below the bar) a suggested alternative product or resource. Generating the redirect in the same call as the decline is what makes the decline useful rather than polite.
A Switch node splits three ways. Qualified requests go to a Slack node for the rep, and a Sort node orders the day's queue by fit. Borderline ones go to a Human in the Loop node. Declines route to a Generate Text node that writes the redirect message.
Every declined message passes through Human in the Loop before sending, at least until you have read enough to trust the judgment. Resend or Email delivers.
A Google Sheets node logs all three outcomes and their reasons. Reviewing declines monthly is the only way to catch a criterion quietly rejecting a segment you wanted.
Nodes this ActionFlow uses
- Webhook (Trigger): fires on the demo request form.
- HTTP Request (Util): enriches the company before any qualification decision.
- Generate Object (AI Core): returns fit level, reason, and a suggested alternative for declines.
- Switch (Control): splits qualified, borderline, and declined.
- Sort (Data): orders the qualified queue by fit rather than arrival time.
- Slack (Human in the Loop): holds borderline requests and every decline for review.
- Resend (Communication): sends the approved redirect. Email fits the same slot.
- Google Sheets (Integration): logs all three outcomes with reasons for monthly review.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.