Leads

Every form, call and chat is matched to a person. People are never merged and nothing is thrown away.

Lead flows

A lead flow is one kind of lead (say, quote requests) and what happens to each one. Its page has two parts, read left to right:

1. Lead sources: where these leads come from.
   • A form made for this lead flow. Put it on your pages, or paste it into your own site ("Copy code for your site"). It also shows on Pages, Forms. A form belongs to one lead flow.
   • A phone line or WhatsApp: a voice or WhatsApp agent for this lead flow answers.
   • Another tool: a web address that Zapier or a CRM sends leads to ("Copy its address"). Say which platform its leads are from: Platform, or if one tool sends several, From a field in the tool's data, with the field's name and what each of its values means ("fb" is Meta). Field with the Lead ID is the field holding the platform's own id for a lead on its own form. Change these later in the ⋯ menu, "Platform and Lead ID"; leads already in stay as they are. With nothing set, its leads say Unknown unless the tool passes a click id.
   • A Snapchat lead form: pick one of the lead forms on your Snapchat ad accounts (connect Snapchat first, in Connections). ScalingDeck asks Snapchat to send the form's leads here. "Read forms again" brings in a form you just made on Snapchat. A form sends its leads to one lead flow. + New Snapchat lead form makes a new one on the ad account you choose, and its leads come to this lead flow. A form always asks for first and last name, and needs an email or a phone number. Your own questions can have a short answer, a date, one choice or many choices. If Snapchat refuses the form, its reason is shown so you can change it.
   • Added by hand appears once you use "+ Add a lead" on Leads. It needs a real email address or phone number, with its country code.
2. Send to: where the leads go, and when each place gets them (when a form is sent, when a call ends and is rated Hot, after 5 minutes...). Click a "When" to change, pause or remove it; "+ When" adds another. A form is sent also covers leads from Snapchat forms, from other tools and leads added by hand.

A new lead flow walks you through it: Name, Lead sources, Send to, On. A lead flow that still has no lead source, or nowhere to send its leads, shows the next step at the top until it does. "Skip for now" shows the whole page.

A returning person. If the same person comes back after a number of days (90 unless you change it when you make the lead flow), they count as a new lead. Before that, what they do is added to their existing lead.

On or off. The switch on each lead source turns it on or off. What arrives through a lead source that is off goes to Needs review instead of becoming a lead; turn it on, then try again from Needs review.

A Snapchat lead form that is not connected says why, with "Try again":

• Another tool already gets this form's leads. Snapchat lets a form send its leads to one place. ScalingDeck never takes it over: remove the other tool from the form in Snapchat's Ads Manager, then try again.
• Your Snapchat login is not an Organization Admin of this ad account. Only an Organization Admin can connect a form. Connect Snapchat with such a login, then try again.
• Snapchat is not connected: connect it in Connections.

"Send a sample lead" in the ⋯ menu asks Snapchat to send its own sample lead, so you can see one arrive. A Snapchat form removed from its lead flow and added again comes back as the same lead source.

Test on a form checks that ScalingDeck receives what it sends. It makes no lead and goes to nobody. A form shows the button until it has had a test or a lead; after that the test is in the ⋯ menu. It does not check that the code is on your site: open your page and send the form for that.

The ⋯ menu has the rest: copy a form's code or another tool's address, edit the form, and Remove from this lead flow. Removing hides the lead source for good, but nothing is deleted: its leads keep their history, and a form stays on its pages (what it sends goes to Needs review). It also stays in Pages, Forms, marked "Not in a lead flow".

A voice or WhatsApp agent's lead sources belong to the agent: they come in when the agent is made, and have no switch or Remove here. To stop them, pause the agent; to send them to another lead flow, use "Change" next to the lead flow on the agent's page. Leads the agent already made stay where they are.

Send to

• Meta and TikTok are set up in Signals, not here: a signal sends your leads (and what happens to them later, like Won) to Meta or TikTok once for every ad. Places that sent to Meta or TikTok from a lead flow before were moved into signals and turned off here.
• Keys (an access token, a bot token, the key for another tool) are stored safely when you save them and are never shown again. Only the part of ScalingDeck that sends leads can use them. "Edit" replaces a key only when you type a new one.
• Send to is grouped by what sets it off, like "When a form is sent". Everything in a group goes out at the same time, unless it says "5 min later". A place with two triggers is in both groups.
• Send a test is in a place's Edit. It sends one made-up lead (Otto Sample, otto@scalingdeck.com) so you can see it arrive. Texts and calls are never tested, because they reach a real person.
• Ratings come from your voice or WhatsApp agent when a call or chat ends, so only those can be limited to a rating.
• LeadsPedia: type the buyer's campaign ID and campaign key (from Post Keys in LeadsPedia) and click Read posting instructions. If ScalingDeck has read that buyer's campaigns before, the link fills itself in; if not, paste the posting instructions link. Add opens Match fields.
• Match fields (LeadsPedia) puts each form side by side with the buyer's fields: your form on the left, LeadsPedia on the right. The ScalingDeck ID comes first, so the buyer can send updates back to the right lead. Lines marked "Matched automatically" were matched by ScalingDeck; change any of them. A question's answers can each be sent as the buyer's own word. Search finds a form by name; the forms that still miss a field the buyer requires come first. Until a form is matched, its leads wait for LeadsPedia (they still go everywhere else) and go out as soon as you save.
• Rejecting means the place refused at least one lead in the last 24 hours.
• One already set up: a place made for another lead flow in the same workspace can be used again; its key is not typed twice.
• Changing one place's "When" never changes another place's: a rule shared with other places is split first.
• Remove from this lead flow stops sending this lead flow's leads there. Other lead flows keep sending, and leads already sent stay sent.
• A "When" marked (all lead flows) applies to every lead flow in the workspace.

All leads

• Search finds a lead by anything on it: a name, an email, a phone number (any part, with or without spaces), an answer from the form, the lead's ids, the buyer's lead ID, or a campaign or ad name.
• + at the end of the column titles adds or removes columns. Each place your leads are sent to has three: its Status (Accepted, Rejected, Waiting...), its Reason (what the buyer said, word for word) and its Buyer lead ID. Your columns are kept for you, on any computer; teammates keep their own.
• Click a column title to sort by it; click again to reverse.
• 50 leads a page; Previous and Next move between pages.
• Export downloads every lead the filters and search find, with your columns, as a spreadsheet file (CSV). An answer that a spreadsheet would run as a formula starts with an apostrophe in the file, so it stays plain text.

What a place's status means:

A send that fails is tried again on its own; "Send again" on a lead's page retries one that was rejected, failed or expired.

Needs review

These arrived but could not be added as a lead. Nothing was thrown away: fix the reason, then pick them and press "Try again". A long list has pages, and sorting a column sorts all of them.

Spam

Every new lead is checked before it is sent. While it is checked its status is Checking; that takes a few seconds.

A lead is Spam when:

• its phone number is not real, or Trestle (the phone and email checking service) says the phone or the email is not real;
• its email is a throwaway address;
• its name is not a name (a web link, only numbers, "test");
• its name or answers have bad words, or are junk (random letters, joke names, nonsense);
• the same person sent more leads in a day than the lead flow's Spam limit (10 to start; change it on the lead flow page).

A spam lead is kept, says why, and is never sent anywhere, not to the places its lead flow sends to and not to Meta, TikTok or Snapchat.

• Not spam sends it now to everything its lead flow sends to.
• Mark as spam stops anything not sent yet. What already went out can't be taken back.
• Lead check on a lead's page shows what was found: whether the phone works, whether the email is real, whether the name matches the phone, how the answers read, and the contact grade (A is best, F is worst).
• Not checked for spam: the checks were down for 10 minutes, so the lead was sent without them.

Use the Status filter on All leads to see only spam.

Updates from buyers

When a buyer (LeadsPedia, Law Ruler, your CRM) tells you what happened to a lead, like "Sold" or "Case Accepted", ScalingDeck adds it to the lead's page and sends it back to the ad platform the lead came from.

• What buyers do: send the lead's ScalingDeck ID (the field they already fill, certus_token, works) and the status to https://inbound.scalingdeck.com/updates, as data, a form or a link. Any status, in their own words. A payout or value they send goes with it.
• What it's sent as: set on each signal, under Signals, Updates from buyers. A rule says what a status becomes ("Sold" as Purchase). Statuses without a rule are sent as they come, or not at all, as you choose. Snapchat takes only its own event names, so on Snapchat a status without a rule goes as Custom event 1; give it a rule to make it a proper Snapchat event.
• Buyers sent: the statuses that have arrived, with how many; click one to give it a rule.

Where a lead came from

Each lead keeps this from the moment it arrives. It never changes later, and it decides where its conversions are sent.

• Platform: Meta, TikTok, Snapchat or Unknown. A Snapchat form's leads are Snapchat's. On a landing page or form, it is the ad click that brought this visit: the link's own sd_src first, then ScCid, fbclid or ttclid in the address. A click-to-WhatsApp chat is Meta's. No click and nothing set: Unknown. Old browser cookies never decide it, they only help the platform match the person.
• Captured on: Snapchat form, Landing page, Other tool, Voice, WhatsApp or By hand.
• Campaign, Ad set, Ad: when known.
• Lead ID: the platform's own id, for a lead on its own form. A lead with one is not sent back as a new lead, since the platform already has it.

A lead's page

• Timeline: everything that happened to the lead, oldest first. Each send (to LeadsPedia, Meta, another tool, Telegram, a text or a call) is its own item with its status: Sent, Trying again, Rejected or Failed. A send shows the time it went out, or the time it was first tried.
• Possible duplicate: the email and the phone point to two different people. Nothing is merged.
• Edit contact: the old value stays on the timeline. If another lead already has the new email or phone, nothing changes: people are never merged.
• Won is sent on by any "When a lead is Won" rule. Not a fit stops follow-ups. Saving the outcome a lead already has changes nothing and sends nothing, and leaving the value empty keeps the value it has. Saving Won with a new value updates the value without sending the lead again.
• Ad click shows where the lead came from (source, campaign, ad set, the Meta, TikTok, Snapchat or Google click). It is kept for sending to Meta and TikTok. A call or a lead added by hand has no ad click.
• Lead reference (admins only): tools that send events back for this lead (say, a sale from your CRM) use it to put them on this lead.
• Saved, nothing sent: the update was recorded without starting any rule.