How Dispatch works.
Three steps, one queue that carries forward from step to step. Here's the whole chain, and what to connect before you start.
01 · Find Leads
Enter a business type and a city — Dispatch queries Google Places directly from your browser using your own API key, so nothing passes through a Dispatch server. Results with a phone number can be sent straight into the Cold Calling queue.
Needs: a Google Places API key, connected on the Integrations page.
02 · Cold Calling
Leads carried over from Find Leads sit in a call queue. Confirm consent, then hit Dial All — this browser tab becomes a softphone and rings each lead in turn through Twilio, so you talk to them yourself, live. It waits for one call to actually end before dialing the next.
Needs: a Twilio account, a caller ID number connected on the Integrations page, and a small backend you run yourself exposing /voice-token — an endpoint that signs a short-lived Twilio Voice access token using your Account SID, API Key/Secret, and TwiML App SID (these stay server-side, never in the browser). Only call people who've already agreed to it.
03 · Book Appointment
Book a meeting yourself right after a call — fill in the lead's name, their email, and a time, and Dispatch creates a Google Calendar event with a Google Meet link and emails the invite for you. Meetings your backend already knows about (if connected) show up in the same list below it.
Needs: Google Calendar connected on the Integrations page. That connection is a one-hour session — if booking fails with a connection error, just reconnect it there.