Installing the PhoneBurner Connected App

📌 Summary

In this video, the speaker explains how Salesforce administrators can enable all users—particularly those with standard profiles—to successfully initiate dial sessions using PhoneBurner. During a user's first dial session, Salesforce prompts for access permission. However, standard users will encounter an OAuth error unless the admin has installed PhoneBurner as a connected app within Salesforce.

The process includes:

1. Admins performing a test dial session to trigger PhoneBurner’s appearance in the "Connected Apps OAuth Usage" section.

2. Navigating to Setup > Quick Find > "Connected Apps OAuth Usage".

3. Clicking "Install" next to PhoneBurner.

4. Ensuring the appropriate security settings are reviewed with your team.

Once installed, all users, including those with standard profiles, will be able to grant PhoneBurner access and start dial sessions successfully.

🏷 Tags

Salesforce setup, OAuth error, connected apps, Salesforce admin, standard user access, PhoneBurner integration, dial session setup, Salesforce permissions, user profile setup, test dial session

✍️ Cleaned-Up Transcript

Now that you've installed PhoneBurner and completed your first test dial session, there's another important setting we need to discuss. I want to walk through the details with you now.

If you think back to your first test dial session, you selected some records—contacts, leads, or something similar and clicked the button to begin the dial session. During that process, you were prompted to either allow or deny PhoneBurner access to your Salesforce account.

To continue with the dial session, you would have clicked “Allow.” At that point, PhoneBurner was granted access to your Salesforce account. That process is necessary to initiate dial sessions.

However, standard users and other profile types won’t be able to grant access like this on their own. They’ll encounter an OAuth error -- "We Can't authorize you because of an OAuth error. For more information, contact your Salesforce Administrator.1 OAUTH_APPROVAL_ERROR_GENERIC: An Unexpected error has occurred during authentication. Please try again"-- because they don’t have permission from the admin to connect PhoneBurner to Salesforce.

Let me show you what a standard user would see. When they attempt this action, they'll hit an OAuth error. That happens because, as the admin, you haven’t yet made it possible for them to authorize PhoneBurner to connect to Salesforce.

To fix this, go to your admin account. Click the gear icon in the upper right and go to Setup. On the left-hand side, use the Quick Find search bar and type in "connected" or "connect" to locate Connected Apps OAuth Usage.

When you get there, you'll see PhoneBurner listed, and you’ll notice a user count of one—that’s you, the admin. If other admins on your team have also done test dial sessions, that count may be higher. But until someone completes that initial test dial session, PhoneBurner won’t appear in this section.

Once it’s listed, click the Install button next to PhoneBurner. I recommend keeping all the default settings, but consult your security team to ensure those settings align with your organization’s policies.

After installation, your standard users will be able to start a dial session and successfully authorize access. You’ll see that they can now click "Allow" and proceed without error.

To recap: As a Salesforce admin, you need to log in with an admin profile and run a test dial session. That makes PhoneBurner appear in the Connected Apps OAuth Usage section. From there, install PhoneBurner as a connected app. Once installed, standard users will be able to grant permission and begin their own dial sessions.

As shown in my example, I now have a user count of two—one for the admin and one for the standard user.

That’s a quick overview of how to make sure all of your users can authorize PhoneBurner and use it for their dial sessions. Thanks for watching, and happy dialing!