Speed to lead is the first automation most agencies build and the one they want running in every client account. Here is what the workflow is made of, and how to save it once and deploy it everywhere with its trigger rewired to the destination.
Speed to lead is the simplest lever an agency has. Reply to a new enquiry in seconds and you connect far more often than if you let it sit for minutes or hours, so the speed-to-lead workflow — the automation that sends an instant reply the moment a lead lands — is the one you want running in every client account. GoHighLevel will happily run that workflow; what it will not do is give you a clean way to move the one you have perfected into the next client's account. This guide covers what the workflow is made of, why each account needs its own copy, and how to clone it so the instant reply fires correctly in the destination.
A speed-to-lead workflow watches for a new lead and responds instantly. The lead can arrive in several ways — a form submission, a Facebook or Instagram lead ad, a landing-page opt-in, an inbound call, or a chat widget — and within seconds the workflow sends the first touch. That is normally an SMS, often an email as well, so it reaches the lead while they still remember the form.
The value is entirely in response time: a lead answered in the first minute is far more likely to pick up than one chased an hour later.
Underneath, a speed-to-lead workflow is a trigger plus an ordered set of actions. A typical build looks like this:
Every one of those steps points at something account-specific — the particular form, the tag name, the assigned user, the pipeline and stage, maybe the calendar — which is what makes it powerful at home and fragile the moment you move it.
You cannot run one central speed-to-lead workflow across many accounts. Each client's leads live in their own sub-account and must be answered from that account's number, tagged with that account's tags, and routed to that account's rep. The pattern is the same proven workflow, copied into each account and wired to its own pieces.
This is where GoHighLevel's native tools run out. Its built-in duplicate only copies a workflow inside the sub-account you are already in, so it cannot carry your build to a client. Snapshots move a whole-account template — the wrong size of tool when the account is already live and you only want to drop in one automation. The common fallback, rebuilding by hand in each account, is slow, easy to get subtly wrong, and a speed-to-lead flow wired wrong fails silently.
ExportGHL Workflows treats the move as three steps — save, check, then deploy — so the same build can be reused across every account you manage.
Because the workflow sits in your library, putting it into the next client account is just another deploy — save once, deploy into each account as you onboard. The end-to-end move is covered in copy a workflow between accounts.
The trigger is the part that most needs attention. A trigger filtered on "when this specific form is submitted" carries an id that only exists in the source account. Drop it into a client account and it points at nothing, so the workflow never fires — a build that looks fine in the editor but is quietly dead.
On a cross-account deploy, cross-account remap runs automatically: ExportGHL matches each account-scoped reference by name against the destination — the form, the tag, the assigned user, the pipeline and stage, custom fields, the calendar — and rewrites the ids to the ones that live there, so a destination form with the same name is paired up and the trigger fires. Anything it cannot match is flagged, and the workflow is deployed as a draft rather than published, so the trigger is never left pointing at nothing. The id rewriting is explained in depth in cross-account workflow remap, and a workflow not triggering after a copy walks through the fix when a trigger stays silent.
Never trust a speed-to-lead workflow until you have seen it fire — a broken instant reply costs you the exact leads it was meant to catch. Before switching it on:
Only once a test lead reaches your phone, from the right sender, should you turn the workflow on for live traffic. You can move your first workflow on the free trial with no card, then run on credits that never expire or a one-time Toolkit licence — see pricing for both.
No credit card. Save your instant-reply workflow once and deploy it into every client account, with its trigger remapped for you.
Start free
ExportGHL