How to Setup Local Content Engine with DispatchScout

This guide explains how to use Dispatch Scout with Local Content Engine.

What Dispatch Scout Can Drive

When Dispatch Scout is connected and sending qualifying events, Local Content Engine can use that activity to:

• Create mini jobs
• Generate AI titles and summaries
• Feed websites and automations
• Generate images and video recaps if enabled

Prerequisites

Before setup, make sure you have:

• A connected Dispatch Scout integration in LaunchSMS
• Access to Dispatch Scout webhook setup
• A saved webhook secret if signature verification is used
• Local Content Engine enabled in LaunchSMS

Step 1: Connect Dispatch Scout

1. Go to Settings > Integrations
2. Open Dispatch Scout
3. Connect the account
4. Save any company defaults you want to use, such as:

• Default Job Type
• Default Lead Source
• Webhook Secret

Step 2: Configure the Dispatch Scout Webhook

In the LaunchSMS Dispatch Scout integration, copy the webhook endpoint shown on the page.

Use that endpoint in Dispatch Scout webhook configuration.

If you are signing webhooks, store the matching secret in LaunchSMS so the platform can verify incoming payloads.

Step 3: Enable Dispatch Scout in Local Content Engine

1. Open Local Content Engine
2. Turn on Enable Local Content Engine
3. Turn on Use Queue Processing
4. Turn on the Dispatch Scout provider toggle

Optional:

• Enable AI image creation
• Enable AI video creation
• Enable automation triggering
• Add a WordPress sync webhook URL

Step 4: Add Brand Assets

For branded media generation, configure:

• Primary Logo Attachment
• Secondary Reference Attachment

Step 5: Run a Completed Job Test

Create or complete a Dispatch Scout job and verify that the completed-job event is sent into LaunchSMS.

Then confirm:

• A mini job was created
• The city and service type are correct
• The summary is usable
• Optional media generation completed
• Any automations ran as expected

Best Practices

To improve Dispatch Scout content quality:

• Keep job type names clean and consistent
• Use strong completion notes
• Make sure the property address is accurate
• Include media when your workflow supports it

Troubleshooting

If Dispatch Scout jobs are not generating mini jobs, check:

• Dispatch Scout is connected
• The webhook endpoint is configured correctly
• The webhook secret matches
• Local Content Engine is enabled
• The Dispatch Scout provider toggle is on
• Queue workers are running if queue mode is enabled

Related Guides

• How to setup Local Content Engine
• How to setup Local Content Engine in WordPress websites
• Dispatch Scout integration docs