Recovery Workflow Guide

Last updated: 2026-03-30

This page explains how the GoHighLevel Marketplace edition of CallStallion works without requiring direct SMS sending from CallStallion itself.

Business & Contact

Business Name: LeadStallion LLC
Product Name: CallStallion
Business Address: 525 Crowe Road, Murphy, NC 28906

Core model

CallStallion acts as a missed-call detection and trigger engine. When a missed call is detected, it sends a structured event into GoHighLevel so the customer's own workflow can handle the follow-up.

Recommended flow

Missed call -> CallStallion -> GHL inbound webhook -> customer 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 GHL setup.

Why this avoids A2P dependency

  • CallStallion does not need to send SMS directly to deliver value.
  • The app's core promise is workflow-triggered lead recovery, not telecom delivery.
  • If a customer chooses SMS in their own workflow, that channel is configured and governed in their own GoHighLevel environment.

Fallback behavior

If no workflow inbound webhook is configured, CallStallion can still create a Task and Note on the contact in GoHighLevel so the missed call is not lost.

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 in GHL

  • 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.

Legal