How to Connect Dispatch Scout
By connecting Dispatch Scout to LaunchSMS, you can create Dispatch Scout jobs from LaunchSMS forms and use Dispatch Scout webhook events for automations, customer follow-up, and Local Content Engine workflows.
How to enable this feature?
Log into the LaunchSMS admin dashboard and go to Integrations and select Dispatch Scout.
Click Connect Dispatch Scout Account to begin the OAuth connection flow.
After you authorize the account, LaunchSMS will save your Dispatch Scout connection and generate a unique webhook key for your company.
Configure Dispatch Scout settings
Once the account is connected, return to the Dispatch Scout integration page in LaunchSMS.
You can save optional company defaults such as:
- Default Job Type ID
- Default Lead Source ID
- Webhook Secret
The webhook secret should match the secret used in Dispatch Scout if you are signing webhook requests.
Add the Dispatch Scout webhook
Use your LaunchSMS Dispatch Scout webhook endpoint when configuring webhooks in Dispatch Scout.
If your account uses signed webhooks, paste the same webhook secret into LaunchSMS so incoming signatures can be verified.
Dispatch Scout webhook events can then be routed into LaunchSMS automations and downstream workflows.
What LaunchSMS sends to Dispatch Scout
When a LaunchSMS form is configured to send submissions to Dispatch Scout, LaunchSMS can create a job using mapped booking, customer, and property details.
Common mappings include:
- Job type ID
- Lead source ID
- Client ID
- Property ID
- First name
- Last name
- Phone
- Street
- City
- State
- ZIP code
- Booking date
- Booking time
- Instructions
If the form does not provide a mapped job type or lead source, LaunchSMS can use the default values saved on the Dispatch Scout integration page.
Form Builder setup
Open your LaunchSMS form in Form Builder and enable Send Submissions to Dispatch Scout.
Then map the Dispatch Scout fields you want to send with the submission.
LaunchSMS also supports Dispatch Scout-specific booking helpers in forms, including:
- Customer lookup by phone or email
- ZIP or postal coverage lookup
- Job-type-aware availability lookup
- Time slot selection from Dispatch Scout availability
How it works
After the integration is connected:
- A customer submits a LaunchSMS form.
- LaunchSMS creates the Dispatch Scout job using the mapped fields and any saved defaults.
- Dispatch Scout sends webhook events back to LaunchSMS.
- LaunchSMS can use those events for automations, CRM updates, and Local Content Engine processing.
Supported webhook-driven workflows currently include events such as:
- Job completed
- Invoice created
- Invoice paid
- Estimate created
- Estimate approved
- Estimate converted
- Payment created
- Client updated
Troubleshooting
If Dispatch Scout is not connecting or syncing correctly, check the following:
- The OAuth connection completed successfully
- The integration page shows Dispatch Scout as connected
- The LaunchSMS webhook endpoint was added in Dispatch Scout
- The webhook secret matches on both sides if signatures are enabled
- Your form has Send Submissions to Dispatch Scout enabled
- Required customer and property fields are mapped in Form Builder
- Default Job Type ID and Lead Source ID are set if you are not mapping them directly
Related guides
- Dispatch Scout Integration Features
- How to Setup Local Content Engine with DispatchScout