LeadBlitz on a Networked Account

✅ Summary:
This training walks you through setting up a Lead Blitz LeadStream in a networked account, where your team shares a single database but still benefits from real-time lead claiming. A Lead Blitz LeadStream sends in-app notifications to all assigned users when a new lead enters the stream. The first rep to claim the lead gets ownership and is immediately connected for a call—maximizing speed-to-lead and team efficiency.

Key Highlights:

• Lead Blitz notifies all users in real time when a new lead enters the stream.
• The fastest rep to claim the lead gets it and is immediately connected (unless you request otherwise).
• Setup includes:
  • Creating a distribution folder (where new leads are placed).
  • Defining a receiving folder (where claimed leads go).
  • No recycling in this example, since claimed leads are owned by the rep.
  • Optional: Set per-rep receiving folders and daily claim limits.
• In-app notifications must be manually enabled per rep.
• Leads can be imported manually, fed via API, or synced through tools like Zapier.
• Reps can disposition leads post-call (e.g., follow-up, appointment set), which moves the lead to the appropriate folder and applies rep-specific tags.
• Admins can configure whether a rep is auto-connected or manually reviews the lead post-claim.

This setup is ideal for collaborative teams managing shared data who want to maximize speed and control while reducing data collisions.

🏷️ Tags:
lead blitz, shared database, worked account, team collaboration, real-time lead notifications, lead claiming, speed-to-lead, folder-based CRM, rep limits, lead routing, dialer automation, contact ownership, rep flexibility

📝 Cleaned-Up Transcript:

Are you looking to take advantage of the Lead Blitz LeadStream setup but work in a collaborative environment with a shared database? Great news—you can absolutely use Lead Blitz in a networked account, even though it’s more common in standalone setups.

Let’s walk through how to build it.

What is a Lead Blitz LeadStream?

A Lead Blitz:

• Notifies every team member when a new lead enters the stream.
• The first rep to claim the lead gets it.
• That rep is immediately connected (unless configured otherwise).
• Ideal for fast-moving teams with real-time lead flow.

Worked accounts share one central database, so you'll be collaborating across one pool of data—unlike standalone setups where each rep has their own data.

Step 1: Accessing LeadStream in a Networked Account

In networked accounts, the LeadStream option is hidden by default.
To access it:

• Go to: phone.com/rotater/index
• Save it as a quick link for future use

Now click Add LeadStream.

Step 2: Create the LeadStream

Enable it and name it:
Network Lead Blitz

Add a short description (optional).

Choose Lead Blitz as the type.

Step 3: Set Up Folders

Distribution Folder:

• Create one named Network Lead Blitz.
  This is where new leads will be placed.

Receiving Folder:

• Set to Network Lead Blitz RCV
  This is where leads go after a rep claims them.

You can choose to lock the receiving folder or leave it flexible. Since this is a collaborative team, we're keeping it unlocked to give reps control.

Recycling:
Not necessary in this example. Once a lead is claimed, that rep owns and works it.
(However, you could recycle into an aged or nurture lead stream in other use cases.)

Skip sorting by custom field and hiding lead totals—because with Lead Blitz, the goal is for new leads to be claimed immediately.

Step 4: Add Recipients (Your Team)

Add team members one at a time to customize:

• Receiving Folder per rep (e.g., Heather’s Leads, Cassie’s Leads)
• Daily Lead Limit per rep
  Example:
  • Heather: 1 lead/day
  • Cassie: 5 leads/day

This helps prevent one person from claiming all the fresh leads.

You can also pause users or edit their settings anytime.

Step 5: Turn On Notifications

Go into each team member’s account:

• Navigate to the Leads tab
• Select the Lead Blitz stream
• Enable in-app notifications

This ensures they’ll get alerted when a new lead enters the stream.

Step 6: Add a Test Lead

To simulate real-time usage:

• Move a contact into the Network Lead Blitz distribution folder

(Leads would usually be added via API, Zapier, or lead vendors.)

Once the lead is added:

• Every assigned rep gets a notification.
• It includes the LeadStream name, state, and vendor (if available).
• The first rep to click “Claim” gets the lead.
• By default, they’re immediately connected to the lead for a call.

Step 7: Dispositioning & Follow-Up

Once the call ends:

• The rep selects a disposition, like Follow-Up or Appointment Set.
• The system moves the lead to the appropriate folder.
• The lead is tagged to the rep, granting them ownership and visibility.

Example:

• Lead gets moved from "Jeff Leads" to "Follow-Ups"
• Tag Jeff is added to the lead automatically

Extra Customization Options

• Reps can manually tag, move, or update the contact record after claiming it
• You can configure the system to not auto-call upon claiming if you prefer to review the lead first. Just contact support.

Why Use Lead Blitz in a Networked Account?

If your team shares a database and:

• Leads come in sporadically
• Team members are multitasking
• You want real-time alerts for new leads

Then Lead Blitz is ideal. It helps ensure leads are claimed and contacted immediately—even if people aren’t constantly staring at their lead list.

Thanks for watching this training. Let us know how we can help you tailor PhoneBurner to your workflow—and as always, happy dialing!