Report Based Dialing in Salesforce Overview

✅ SUMMARY:
This video introduces a highly requested new feature: the ability to launch a PhoneBurner dial session directly from Salesforce reports. Previously, Salesforce’s limitations prevented this capability, but a new update now allows users to initiate a dial session from a visualforce page within the PhoneBurner app. Users can select from the 100 most recently edited reports and launch a session with up to 500 records—more than double the list view limit of 200.

Key enhancements include:

• Honoring the report’s sort order during dialing.
• Record targeting control: The system uses the first column in the report to determine which records to call (e.g., contact vs. account).
• Deduplication: Prevents duplicate calls if multiple contacts are tied to the same account.
• Optional exclusion of records with open opportunities, allowing focused outreach.
• Custom object support: Users can initiate sessions from reports based on custom or managed package objects by providing the API name and configuring field mappings for phone numbers.

The video concludes by directing users to additional training for setting up custom configurations and custom phone number mappings.

🏷 TAGS:
Salesforce integration, power dialing, dial session, report-based dialing, contact management, mass dialing, visualforce page, Salesforce reports, custom objects, record sorting, opportunity filtering, field mapping, custom phone fields, PhoneBurner for Salesforce, dialing efficiency, CRM automation

📝 CLEANED-UP TRANSCRIPT:

Over the years, we’ve had a lot of people request the ability to launch a PhoneBurner power dialing session directly from Salesforce reports. The issue has always been that Salesforce doesn’t allow buttons within the report section to initiate mass actions—like selecting records and starting a dial session.

But I want to share a recent update we’ve launched that gives you and your team the ability to launch a PhoneBurner dial session from records in a report.

First, make sure you have the latest version of our PhoneBurner app installed. Once it’s installed, you’ll have the option to add the Report Dial Session tab to any app within Salesforce. Clicking that tab takes you to a custom Visualforce page with step-by-step instructions.

On this page, you’ll see a dropdown menu listing your 100 most recently edited reports (with the most recently edited one at the top). For example, if I want to initiate a dial session from my "Leads Added - November 4th, 2025" report, I select it, and it will show me that the report contains 89 records. If that looks right, I can go ahead and click the button to start the dial session.

From there, the experience is just like launching a dial session from a list view.

A few key enhancements with report-based dialing:

1. Increased record limits: In list view, Salesforce only supports mass actions on 200 records, which limits us to 200 records per dial session. With report-based dialing, that limit increases to 500 records per session.
2. Maintaining report order: PhoneBurner now honors the order in which the records appear in the report. So if you want to call them in a specific order—say, by "Last Attempt Date"—you just sort your report accordingly, save it, and launch your dial session. The contacts will be dialed in that order unless some are skipped due to time restrictions (e.g., too early or late to call).
3. Handling reports with multiple objects: For example, in a report showing both accounts and their associated contacts, you can control which records are called by ensuring the first column contains the appropriate Record ID. If the first column is Account ID, the session will dial accounts. If you move Contact ID to the first column, you’ll be dialing contacts.
4. Duplicate scrubbing: If multiple contacts in the report are linked to the same account, but you're dialing accounts, only one instance of each account will be dialed—even if the report shows several entries tied to that account.
5. Opportunity filtering: There’s a checkbox labeled "Exclude records with open opportunities." If selected, the system will scan the report and exclude any accounts or contacts with active opportunities. For instance, if your report has 89 records but 3 of them have open opportunities, only 86 will be added to your dial session.
6. Support for custom objects: You can also start dial sessions from reports based on custom objects, whether they were created by you or part of a managed package. To do this, you'll need to supply the API name of the object. You can find this by going to Setup → Object Manager and selecting the object (e.g., “Vendor”), then copying the API name into the dial session interface.

If you're dialing from a custom object:

• You’ll need to create a configuration in the PhoneBurner app.
• You must also add custom phone number field mappings in the PhoneBurner integration settings for Salesforce. Without these, the system won’t detect phone numbers and the dial session will have zero contacts.

We have separate training content that walks you through adding these custom mappings and creating configurations.

That wraps up this overview of the PhoneBurner report-based dialing feature. We hope this helps you and your organization get more done in less time using the power of PhoneBurner. Thanks again—and happy dialing!