A workflow that's powerful but finally clear: trigger → action → controls, plus routing by call outcome.

A created agent does nothing until it's put into a workflow — the path that tells it who to call, or how to handle inbound calls to its number. The old builder was both limited and rigid: you could add an optional trigger, pick an agent, and set a drip (how many calls go out at a time) — and that was about it.

Pacing leaned on blunt delays, and exit criteria like "booked a meeting," "transferred to a human," or "asked not to be contacted" were bolted onto the workflow itself to pull people out. The capability was there; the clarity and flexibility weren't.

I framed the whole thing as one sequence a user moves through — who enters, what happens, and how it behaves.

The key insight: most of the old complexity came from reacting to what happened on a call (delays, exit criteria) being scattered across the workflow. Pull that into one place and the rest gets simple.

A clear path: (1) an optional trigger to start the workflow, or enroll contacts added manually or imported from a CSV; (2) the action to take — today an AI call, with room for more; (3) the flow controls — delays, unenrollment settings, and a new call-outcome router.

The router is the unlock: because the workflow now knows what happened on the previous call, it can branch intelligently instead of firing blind delays, and it absorbs the old exit criteria (booked, transferred, opted out) into one clear control. Drip is also handled more cleanly across multiple workflows.

The whole builder now reads as one clear path instead of a pile of settings, and the call-outcome router is the standout unlock — workflows can adapt to what actually happened on a call instead of running blind.

Hard numbers can be added once cleared.