Skip to main content

Sending one lead to several places at once

3 min read

Telegram for the salesperson, a sheet for the manager, the CRM for the department — one lead can go to all three, and you decide which lead goes where.

One form, up to five destinations

A single lead form in Facebook can be connected to as many as five integrations at once. When a lead arrives it goes to all of them together: a message in the Telegram group, a new row in Google Sheets, a new card in the CRM.

The destinations do not depend on each other. If one fails — say the CRM does not answer — the rest carry on their way, and the one that fell over goes onto the retry ladder.

Duplicate control is kept separately per integration, so five destinations do not get one lead five times: each of them gets it once.

Not every lead belongs at every destination

Sending every lead everywhere is usually unnecessary: leads from one region to one salesperson, leads from another to someone else; a lead asking about an expensive product is easier to work in a group of its own.

For that you put a condition on the integration. Conditions are written over the data that came in with the lead: if the condition holds the lead goes to that destination, if it does not the lead stays away, and the other destinations are unaffected.

The result is that one form splits into several streams and each salesperson only gets the leads that concern them.

Fourteen operators and two kinds of logic

There are fourteen operators for writing conditions — you do not type them, you pick them from a list. Each condition is one field, one operator and one value.

Several conditions can be joined in two ways: all of them hold, or one of them holds. The first narrows the filter, the second widens it — most mistakes come from swapping those two.

One integration can hold up to fifty conditions. In practice three or four are enough, but it is better to know the limit.

Test it on history before saving

You can check that the condition you wrote works before you save it: the system takes that integration's leads from the last 90 days and shows which of them pass.

This is not dry theory. If the condition let through not a single lead over the past three months, the field name or the value is probably wrong. If it lets every one of them through, the condition is not actually filtering anything.

The test runs on that integration's own history, so the result rests on your real leads and nobody else's.

Where it is easiest to start

The simplest order: first one reliable destination — a Telegram group, say — with every lead going to it. Once you are sure it works, add the second destination, write a condition for it and test it on history.

Switching on five destinations at once and then hunting for “where did that lead go” takes longer than adding them one at a time.

Related pages

Read next

Do not keep your leads waiting

Sign up and turn on your first integration. No code needed, and up to 1000 leads a month are free.