Skip to content
Blog

· Natrajan

How to define a lead conversion outcome with alternative success events

Learn to set up an outcome that counts either a demo booking or a signed contract as success, track each lead, and get deadline alerts.

Business professional analyzing bar chart on tablet in office setting, highlighting data insights.
Photo by Jakub Zerdzicki on Pexels

Hook – One outcome, many ways to win

You’ve spent time building a lead-generation form, an inbound email address, and a Stripe checkout page. Now you need to know whether each lead actually converted – but conversion can happen in more than one way. A prospect might book a product demo, or they might sign a contract directly after reading the proposal. If you treat only one of those actions as “success,” you’ll miss half the wins and waste time chasing false negatives.

In this guide we’ll show you how to create a single outcome that treats either a demo booking or a signed contract as a successful conversion. You’ll learn to:

  • Define the outcome with start, success, and failure events, plus a deadline.
  • Pull contacts into the outcome from any entry point (form, email, CSV, API, or signed webhook).
  • Configure per-step retry policies and idempotency keys so ambiguous failures don’t create duplicate messages.
  • Set up deadline alerts that warn you before a lead falls through the cracks.

By the end you’ll have a reliable, measurable conversion funnel that works across multiple channels without double-counting or missed deadlines.


1. Why an outcome with alternative success paths matters

Most automation tools stop measuring at the run level: “the workflow finished, so we’re done.” That approach hides the real business question – did the lead actually convert?

When a lead can convert in more than one way, you need a single source of truth that says “conversion achieved” regardless of the path taken. OutcomeOS lets you define an outcome with multiple success events. The outcome is marked achieved only when a trusted event arrives:

  • A signed webhook from your scheduling tool confirming a demo was booked.
  • An authenticated API call or signed webhook from your contract-signing platform confirming a contract was signed.

Both events satisfy the same outcome, so you can report a single conversion metric while still preserving the details of how the conversion happened.


2. Define the outcome: start, success, failure, deadline

2.1 Start event – the moment the lead enters the funnel

Pick a single event that marks the beginning of the conversion journey. Common choices:

SourceExample start event
Web form“Contact form submitted” (HTTP request)
Inbound email“Email received at sales@yourcompany.com” (signed webhook)
CSV import“Row added to contacts CSV” (API call)
API“Lead created via API” (authenticated request)
Stripe webhook“Payment intent created” (signed webhook)

Create a start rule in OutcomeOS that captures the contact’s unique identifier (email, phone, or internal ID). This identifier will be used to track the contact through the rest of the outcome.

2.2 Success events – the alternative paths

Add two success conditions:

Success pathTrusted event typeExample payload
Demo bookedSigned webhook from scheduling tool{ "event":"meeting.booked", "lead_email":"john@example.com", "meeting_id":"abc123" }
Contract signedSigned webhook or authenticated API call from contract platform{ "event":"contract.signed", "lead_email":"john@example.com", "contract_id":"def456" }

OutcomeOS treats the outcome as achieved as soon as it receives either event for the same contact. You can still see which path was taken in the contact’s timeline.

2.3 Failure events – when the funnel closes without conversion

Define a failure condition that fires when the deadline passes without any success event:

  • Failure event: “Deadline reached” (automatically generated by OutcomeOS).
  • Deadline: Choose a realistic window – e.g., 7 days after the start event.

If the deadline triggers, the outcome is marked missed and the contact appears in the “missed” section of the dashboard.

2.4 Deadline alerts – stay ahead of missed conversions

OutcomeOS can send:

  • Email alerts when a contact is still pending and the deadline is near.
  • SMS alerts via Twilio under the same condition (useful for on-call sales reps).
  • Daily digest summarising all pending contacts and upcoming deadlines.

3. Bring contacts in from every entry point

Your leads may arrive through any of the supported channels. Set up a single contact ingestion pipeline that normalises the identifier and attaches the start event.

Entry pointHow to ingest
Form linkHTTP request to OutcomeOS endpoint (include email, source).
Inbound emailForward the email to a signed webhook that posts the sender’s address.
CSV importCall the OutcomeOS API with each row’s email and any extra fields.
APIDirectly POST a JSON payload to the OutcomeOS endpoint.
Signed webhook (e.g., Stripe)Configure the provider to send a signed webhook to OutcomeOS; OutcomeOS validates the signature and creates the contact.

Because the start event is the same for all channels, you can later filter the dashboard by source if you need to compare performance.


4. Configure retries and idempotency per step

Automation steps that interact with external services can fail for many reasons (network hiccups, provider throttling, etc.). OutcomeOS lets you set a retry policy and an idempotency key for each step:

  1. Choose an idempotency key – usually the contact’s email combined with the step name (e.g., john@example.com-demo-email).
  2. Set retry count – e.g., 3 attempts with exponential back-off.
  3. Define failure handling – for non-idempotent steps (e.g., sending a one-time SMS), configure the step to go to “Requires attention” if the response is ambiguous. This prevents duplicate messages.

When a step finally succeeds, OutcomeOS records the output. If the workflow later fails, a replay starts from the failed step but re-uses the outputs of all earlier successful steps, so you never resend a demo-booking email or a contract reminder by accident.


5. Set up alerts that keep you on schedule

With the outcome defined, you’ll want to know when a lead is about to miss the deadline. Here’s a minimal alert configuration:

Alert typeTrigger conditionDelivery
Email reminderDeadline is near and outcome still pendingEmail to sales manager
SMS reminderDeadline is near and outcome still pendingTwilio SMS to on-call rep
Daily digestEnd of day, list of all pending contactsEmail to team inbox

OutcomeOS sends the alerts automatically; you only need to provide the recipient addresses and phone numbers. The alerts include the contact’s email, the time left until the deadline, and a link to the contact’s timeline for quick action.


6. Concrete example – numbers that make sense (hypothetical)

Scenario: A SaaS agency generates 150 leads per month via a web form and inbound email. They want to treat a demo booking or a signed contract as a conversion within 7 days.

MetricValue
Leads per month150
Demo bookings (first 30 days)45
Signed contracts (first 30 days)30
Total conversions (either path)75
Conversion rate50 %
Missed deadlines75 leads (no demo, no contract)
Alerts sent (email)75 (one per missed lead)
Alerts sent (SMS)30 (high-priority leads)

Step-by-step flow:

  1. Start – A lead submits the form; OutcomeOS creates a contact with email alice@example.com.
  2. Step A – Send a welcome email via Gmail (idempotency key alice@example.com-welcome). Retry up to 2 times if Gmail returns a 5xx error.
  3. Step B – Wait for either a demo-booking webhook (meeting.booked) or a contract-signed webhook (contract.signed). Both are trusted events.
  4. Success – Alice books a demo on day 3; OutcomeOS records the demo webhook and marks the outcome achieved. No further alerts.
  5. Failure – Bob does not respond; as the deadline approaches, the email reminder fires; when the deadline passes, the outcome is marked missed and a final SMS is sent to the sales rep.

Because the outcome only marks achieved after a trusted event, the agency can confidently report a 50 % conversion rate and focus follow-up effort on the leads still pending.


7. Quick checklist – set up your multi-path outcome in minutes

  • Identify the start event (form, email, API, etc.) and ensure it includes a unique identifier.
  • Choose two success events (e.g., demo-booking webhook, contract-signed webhook).
  • Define a deadline (e.g., 7 days) and configure the automatic failure event.
  • Connect all entry points to OutcomeOS (HTTP request, signed webhook, API call).
  • For each automation step, set an idempotency key and a retry policy that matches the step’s idempotency.
  • Enable email and SMS deadline alerts with the appropriate recipient list.
  • Test the flow with a few dummy contacts to verify that the outcome is marked achieved on either success event.
  • Review the daily digest for pending contacts and adjust the deadline or alert timing if needed.

8. How OutcomeOS makes it painless

OutcomeOS lets you define an outcome once and reuse it for every lead, no matter how the lead entered your system. By treating a demo booking or a signed contract as the same success event, you get a single conversion metric, per-contact visibility, and automated deadline alerts that keep your team focused on the leads that need attention.

Ready to build a reliable, outcome-driven conversion funnel? Sign up for a free account or compare plans to see which fits your business at the pricing page.

One short letter when we ship something worth switching for.

Double opt-in. Unsubscribe from any issue in one click.