Workflow-First Reference

Recovery Workflow Guide

This guide explains how the marketplace edition of CallStallion detects missed calls, routes a structured event into your workflow, and avoids relying on direct SMS sending to deliver value.

Last updated: 2026-03-30
Core model
Detection and trigger engine
Missed calls become structured events that your own workflow can act on.
Fallback
Task + Note support
If no workflow webhook is configured, the app can still log follow-up inside the account.
Stage 1 Missed call detected by CallStallion
Stage 2 Structured event sent into your workflow
Stage 3 Your workflow handles follow-up actions
Fallback Task + Note created if no workflow webhook is set

Business and product details

Reference details used in reviewer-facing documentation and support context.

1

Business name

LeadStallion LLC

2

Product name

CallStallion

3

Support email

support@callstallion.com

Why this design matters

Built around workflow-triggered recovery

The marketplace edition is positioned around workflow-triggered lead recovery. Customers can still use SMS in their own workflow if they choose, but CallStallion itself does not need to be the direct sender to deliver core value.

  • CallStallion does not need to send SMS directly to solve the missed-call problem.
  • The app's main promise is workflow-triggered follow-up, not telecom delivery.
  • If a customer chooses SMS in their own workflow, that downstream channel is configured and governed in their own environment.

Implementation reference

These are the practical pieces customers or reviewers should understand about the workflow setup.

Recommended flow

Missed call -> CallStallion -> inbound webhook -> workflow actions
Typical downstream actions can include sending email, creating tasks, adding tags, moving pipeline stages, notifying staff, assigning contacts, or sending SMS through the customer's own approved setup.

Example payload fields

  • locationId / location_id
  • callId / call_id
  • phone / from_number
  • to_number
  • isMissed / is_missed
  • missedReason / missed_reason
  • occurredAt / occurred_at

What customers should build

  • Create a workflow with an Inbound Webhook trigger.
  • Map the incoming phone and missed-call fields.
  • Add the follow-up actions that make sense for the business.
  • Test the workflow with CallStallion's test event or a real missed call.

Need legal or onboarding links?

Use these pages for marketplace review, user setup support, or internal submission reference.

Email support@callstallion.com
Getting Started The shorter onboarding path for new installs and first-run setup. Privacy Policy Marketplace and data-handling details for CallStallion. Terms of Service Service terms for the marketplace edition.