PhoneBurner Sync Settings in Salesforce

1. Summary

This training walks Salesforce admins through setting up PhoneBurner Sync Settings in the Salesforce package. It explains how to confirm the latest package is installed, assign the correct PhoneBurner permission sets, configure Salesforce Named Credentials, generate and apply a PhoneBurner personal access token, and test the API connection. The video then shows how to select a Salesforce object, map required and optional fields, create sync rules that move records into the correct PhoneBurner folders, and build Salesforce record-triggered flows for newly created and updated records. It also demonstrates testing the sync with a sample contact, configuring LeadStream dialing settings in PhoneBurner, enabling the Salesforce iframe during dialing, and confirming that call activity logs back to Salesforce.

2. Tags

Salesforce integration, sync settings, named credentials, permission sets, personal access token, field mapping, sync rules, Salesforce flows, record-triggered flow, LeadStream, contact sync, folder management, Salesforce iframe, call activity logging, admin setup, Salesforce package, custom objects

3. Cleaned-Up Transcript

Hello there. This is Jeff Osness, the Principal Evangelist here at PhoneBurner. In this training, I want to walk you through how you can start taking advantage of the PhoneBurner Sync Settings that are available within the PhoneBurner package in Salesforce.

The idea behind this specific option within the package is to allow you, as an admin, to define specific fields that we will monitor and send those records over to PhoneBurner so your team can power through those calls and potentially share a list in PhoneBurner and take advantage of LeadStream.

With that being said, let's talk about how you can take advantage of this feature.

First, you need to make sure that you have the latest version of the PhoneBurner package installed in Salesforce. Once you have that installed, you should see the PhoneBurner Lightning App in your Salesforce account. Within that, you should see a PhoneBurner Sync Settings tab.

If you are not seeing that, the fastest way to solve the problem is to go to the Setup section in Salesforce and add the PhoneBurner Admin permission set to your profile. Let me show you how to do that real quick.

We are going to type “permission” in the Quick Find on the Home tab of the Setup section, and then we are going to click on Permission Sets.

From there, we will scroll down until we find the PhoneBurner option. You should see PhoneBurner Admin listed there. Let's click on that, and then click Manage Assignments.

Click Add Assignment and then find your specific user. I am going to go ahead and find Jeff. Then click Next and Assign.

Now, you should not have to do that, but I do recommend that you assign that permission set to your user profile, or to the profiles of all the users who will be taking advantage of PhoneBurner. We have two different profiles: the admin profile and the user profile. Assign the appropriate one to the appropriate users.

Now, let's jump back over here.

Now that you know how to assign that profile, that just gets you to this tab if you did not already have it. But what do we do here?

The first thing we need to do is connect to PhoneBurner. We cannot send data from Salesforce to PhoneBurner without making a connection. We need permissions.

The first thing we need to do to enable this is set up Named Credentials. We need to do some configuration within the Named Credentials feature in Salesforce. We are just going to walk through these steps together.

Step one is to open Salesforce Setup - Named Credentials. To make this easy for you, we have made a link, so you can just click on that. That will take you directly to the page that you need to access.

Here we are on the Named Credentials page. Let's go back to our instructions because there are some important pieces here.

We need to click the External Credentials tab. Going back over here, we will see External Credentials. When we click on that, we will see PhoneBurner Sync, and that is what we are looking for.

Let's click on PhoneBurner Sync.

Once we have that open, the next thing we need to do is go to the Principals section and click New, then fill in the details.

We are going to go back to that tab, click New, and start filling out these details. The best thing to do is to copy and paste this name because the name is important. It has to be exact.

We are going to copy that and paste it here. Now, Sequence Number and Identity Type do not need any changes. But we do need to add an authentication parameter.

So, we are going to click Add. Going back to our instructions, we will see that we are doing everything according to the instructions.

The name of the authentication parameter is Access Token. Again, this is a copy and paste. It has to be exact. We will copy and paste that Access Token field or value and put it in there.

For the Value field, we are going to go back to our instructions. This is a value that we have to get from PhoneBurner. This is our personal access token from PhoneBurner.

I am going to click Generate a Personal Access Token.

If you are already signed into PhoneBurner, it will take you directly to the page where you need to generate that token. If you are not signed into PhoneBurner, it will take you to the homepage. You will have to sign in, and then you can go back and click the link again.

Or you can click on your initials in the upper-right portion of the page, go down to the Integrations link under Settings, and then click Personal Access Tokens on the left-hand side. That will get you to the same place.

Then we are going to click Generate New Token. That will give us a new token in our account. We will highlight that token and copy and paste it. We do not want to get anything wrong here, so let's copy and paste.

Where do we need to put that? We need to put it into the Value field of the Named Credential parameter. So, we will paste that in there and save.

Once we save, we should be done with that step. Let's jump back over here to Salesforce and take a look.

That is step two. Step three is Save.

Now, step four is to create a new permission set to grant credential access. We need a permission set to assign to ourselves so that we can take advantage of this personal access token.

Again, in this step, you will see a link to open the Permission Sets. We can go straight there by clicking on it.

Of course, we already had that open in another tab because we were working with it earlier, but we are going to follow the instructions here.

We are going to click New.

Let's double-check here. Once we click that, we click New. So, we are going to click New.

Now we are going to create a new permission set. The name is not as critical here. It does not have to be exact, but again, I recommend copying and pasting it.

We will copy that and paste it in here. The API name will auto-generate. We do not need to put a description in here, but you can add a description so future you will remember what you created this for.

Then we have Session Activation Required. For License, we do not need to check this. We do confirm that you do not need to set the license. Just leave it set to None so it can be used for all licenses. Then click Save.

Once we save that, we need to go in and get the External Credential Principal Access set up.

Here, on the new permission set, scroll to External Credential Principal Access. We are going to scroll down here. You will see External Credential Principal Access. We will click on that and then click Edit.

If we go back here, we should see Edit. We should see the PhoneBurner LeadStream option listed there. We are going to select that and add it.

Let's double-check our instructions. External Credential Principal Access - Edit - move PhoneBurner Sync PhoneBurner LeadStream Admin to Enabled and save.

PhoneBurner LeadStream has been moved over to Enabled, and we are going to save.

All right. We have now saved that here.

What is the next thing we need to do? Manage Assignments.

We are going to click Manage Assignments and Add Assignments. Just like we did before with the PhoneBurner built-in permission set, we are going to add this to our user.

Let's go ahead and add our user. Hit Next, then Assign.

There we go. We are now done with that.

Now that we have done that, let's click Test Connection. There we go. We are now successfully connected to PhoneBurner. That made a real API call to the PhoneBurner system to verify the connection. We are good to move forward.

What is next? How do we move this forward?

Let's scroll down. Actually, before we scroll down, let's talk about this page a little bit more.

We have done the connection, which is step one. Now we are going to move on to step two, which is choosing the object.

Which object do we want to connect to PhoneBurner? What type of records are we going to send over to PhoneBurner?

It is important to understand that right now, PhoneBurner supports one object at a time. You can do leads, contacts, accounts, or custom objects. That is fine, but you have to choose one at a time.

While there is no limitation on what you can sync to PhoneBurner, when you are actually making calls using PhoneBurner, PhoneBurner has to know the specific object that you are connected to, or the specific object that those records belong to.

We will get into that. I will show you how to ensure that your PhoneBurner account knows what object you are linked to.

Step two is choosing the object.

We are going to scroll down here. Actually, I am already scrolled down. Down here at the bottom, you will see Object Type.

We are going to click on this and start typing. Let's say we want to do contacts. So we type in “contact” and find that.

Once we choose that object, you will see that step two is now complete. We can move on to step three, which is to map fields.

Now there are going to be some new options down below Object Type. The first one is Field Mapping.

The primary thing, and the most important thing, is that we need to choose which phone number from Salesforce is going to be the primary phone number that your team, or you, call when calling these specific contact records.

Here, we will see all the fields that the system thinks could be phone number fields. Keep in mind that we are trying to use a little bit of magic here so you do not have to look through every specific field that exists in your object.

We are not limited to just fields that have a phone type, because some of you store phone numbers in text fields, which is fine. Just know that we are going to try to find the right fields here for you to choose from.

Now it is up to you to decide which field will be the primary field. Are we doing the business phone, that primary phone field? Maybe you want the home phone. Maybe you want a mobile phone. Maybe you have customized your system and have a specific custom field that has the phone number you want to call first when dialing through PhoneBurner.

That is fine. Just choose that phone number field.

After you have made that selection, there are a few other options you can use. You do not have to use them. They are all optional.

First name is highly recommended to bring over. So we go down here and find First Name. It is going to be in here somewhere. There we go.

Then Last Name. Let's find Last Name. There it is.

Email, address, and I think this is not really called Address. It is something like Mailing Address. You have different addresses, so you get to choose what you want to map here. It is totally up to you how you do that.

I am going to go ahead and map the mailing address information: mailing street, city, state, and zip.

So, mailing street. Then city, state, and zip. Mailing zip. And there we are.

Okay. We have all that mapped.

Now we can go down to the next option, which is Additional Fields. This one will be closed by default. It will not be expanded.

It is up to you if you want to add additional fields. You just click that expansion, and you will be able to start choosing from these fields.

Maybe up here we did mobile phone, but we still want the business phone to come over, and we want the home phone to come over if we have it. Maybe they do not all have mobile phones, so we still want to bring over other phone numbers just in case.

We are just choosing what will be the primary. If there is no primary, these phone numbers will still come over, and you will still be able to call those records.

The next one is Custom Fields to Send. Let's expand this.

This one is an interesting one. I am not going to read through all of this, but do take some time to read through the field-level security details that we have in there.

I want to talk about the fields here.

In most cases, I do not recommend that you map a lot of fields from Salesforce to PhoneBurner. You do not want to spread your data all over the place.

But we do want to give you the option to sync a field from Salesforce, or even a couple of fields, depending on what you want to do.

Again, I do not recommend that you sync a lot of these because you do not want your data spread all over the place.

You can take advantage of this field for sorting contacts in PhoneBurner. You can also take advantage of this field for prioritizing the order a contact is called in a LeadStream.

You might have a specific field, like a priority field. Maybe this is a high-priority contact, this is a low-priority contact, or whatever that might be. You may want to sync that specific field over to PhoneBurner.

I am just going to grab one here, something like Created Date, so that we have something to show you that comes over to PhoneBurner. Everybody is going to do something different here, so it does not really matter what I show you. I just want you to understand the concept.

My recommendation is that you do not sync a bunch of data over to PhoneBurner.

Also, keep in mind that this is not a true two-way sync. This is just to send data over to PhoneBurner. Changes that you make to this field in PhoneBurner will not be reflected in Salesforce, so keep that in mind.

All right. Now we have done that.

Let's go down to the next section, which is Sync Rules. This is an important piece because this is how you determine which records should be sent over to PhoneBurner and when.

Let's click Add Sync Rule.

Essentially, you are going to define a specific field in Salesforce and a value in that field. When a record has that value in that field, we want to send that record over to PhoneBurner and put it into a specific folder on the PhoneBurner side.

I have a field. Let's go over here to this tab. I am going to jump over to a different tab. Let's take a look at one of my contacts.

We will grab a contact. Here we are. We are going to the Contact object. Let's go to Adam, then Details.

Here we have a Contact Status field. It has New. You might have Working. You might have all kinds of different values in here.

This might be you. I do not know what kind of fields you have in your organization or how you organize your data over in Salesforce, but I recommend having a Contact Status field.

I think the Lead object has a Lead Status field automatically, but every organization works a little bit differently.

Creating or having a specific field that your system will monitor in order to decide when a contact should be sent over to PhoneBurner and where it gets placed is useful.

For example, you might want to have all contacts that get set to a Contact Status of New sent over to PhoneBurner and put into a LeadStream.

However, a contact that has a status of Working, Closed Won, or Closed Lost might need to be taken out of a LeadStream so you are not continuing to chase that lead or contact after you have already connected with them.

These values are important.

Let's jump back over here.

For the field, we are going to use Contact Status. I cannot remember if it is Contact Status or just Status. What did we call that field?

You are probably seeing it.

Okay, let's go back over here. It is Contact Status.

There it is. My goodness gracious. If it were any closer, it would have bitten me. It is right there staring me in the face.

So, Contact Status value equals New. Remember, we have to do these exactly. Type them in exactly as you see them here.

We are going to move that contact. We are going to place that contact into a specific folder.

You will see this Action dropdown has two options: Move to Folder and Transfer and Move to Folder.

Anytime you have a sync rule that is going to put a contact into a LeadStream, where you know you want them to start being called, I recommend choosing the Transfer and Move to Folder option.

Why should you do that?

The reason I recommend doing that is because if, for whatever reason, that contact or record already exists in PhoneBurner, this will force that contact to be moved to the admin account, to your admin account, and placed into that folder so it can be called through that LeadStream.

If we leave it set to just Move to Folder, and if that record had already been called using PhoneBurner through some other user, or maybe you had already synced it over at some point in the past and now you want to put it into a new LeadStream, that contact would move into that folder.

But if it has been called by somebody else, it might not actually be owned by you, the admin, in which case it would not actually be placed in the LeadStream.

Anytime you are configuring a sync rule that is going to place a contact into the distribution folder of a LeadStream, I recommend choosing the Transfer and Move to Folder option.

Once you have chosen that action, we go to Folder and choose the folder where we want to put the records.

In here, you can see that I have all of my folders from PhoneBurner, and I have a folder called Salesforce Contact. I could put it in there and say, “Okay, everything that is a new contact in Salesforce goes over to my Salesforce Contacts folder, and I am going to build my LeadStream off of that.”

Then I need to set up other sync rules. Remember, this is just one sync rule that gets the record over there so we can start smiling and dialing.

But if we connect with somebody and their status changes to Working, we might want to move them into a different folder.

Let's add another sync rule. In this case, I am going to do it again based on Contact Status.

Now that I have seen it once, I am going to find it easily. We are going to choose Working as the value we are looking for.

Then we are going to move it to another folder because we do not want to put that record into another LeadStream.

Finally, we need to choose what folder we want to put them into. In here, I might not have a specific folder I want to put them into. Maybe I just want to stop calling them, so I click the Stop Calling folder.

Or maybe I create a folder called Working, and all of my contacts, once I start working them, get moved into that folder.

Now, let's add another sync rule. In this particular case, we are again going to choose Contact Status. Let's do Closed Won. Move to Folder. We have Closed Won, and we will choose that.

Okay. I think you get the idea with the sync rules. You can create as many of those as you want, and then we need to save this.

Let's scroll down to the bottom. You will notice that Save is all the way at the bottom.

Then we have this critical step. This is step six. We will come to that here in a minute, but we are going to save our settings right now.

Once we save that, if we scroll up to the top, we will see that we are essentially done with most of these steps.

It may take a second for this to complete, and then we will see if Save Settings is done. We are essentially done with steps one through five.

We now need to complete step six. This is a really important step because, while the sync rules tell the system and the payload from Salesforce to PhoneBurner what to send and where to put it, we still need a trigger.

We need something to tell Salesforce that this stuff needs to happen. So, we need to create some flows.

I recommend that you create two flows.

Flow number one is for new records. That way, if you import contacts into your Salesforce Contact object and set them all to New, like in my case where I have a status of New, all those records being created in the system with a value of New will be triggered and sent over to PhoneBurner.

We need to create a flow that will capture those specific records and get them over to PhoneBurner.

The second flow we need to create is one that will trigger off updates. That way, as a record is updated on the Salesforce side, we then move that record into the appropriate folder in PhoneBurner.

We need to go to Setup - Flows - New Flow - Record-Triggered Flow.

I think everybody here should be pretty familiar with this. Hopefully, this is a Salesforce thing, not a PhoneBurner thing.

I am going to walk you through both of these. We are going to do flow one and flow two.

We already have Setup opened in another tab, so I am going to click on that. We are going to use Quick Find and go to Flows, and then we are going to create a new flow.

Click New Flow. It is going to be a record-triggered flow.

We go back here: Record-Triggered Flow. Select the same object you configured above. That will be our Contact object.

Right here, we are going to do Contact because it is the same object we selected above. This is the “above” we are talking about in step two.

Okay. We have selected Contact.

Now we need to set the trigger and entry conditions for flows one and two.

For flow one, the trigger is “A record is created.” The entry condition is Trigger Field equals Trigger Value.

Go back to our flow. This will be “A record is created.” Entry field is “All Conditions Are Met.” The field, in my case, is Contact Status.

Yours will be whatever field you have selected. This is the point where you cannot copy me 100%. But the concept should be clear.

We are choosing the field equals that value. In this particular case, we did New. So, equals New.

When a contact is created, if it has a Contact Status of New, this flow will engage.

Let's jump back over here.

We want it to run immediately and add an action. Search for Sync Record to PhoneBurner.

What does that mean?

Let's go back over here. We are going to run immediately. We will click this little plus and go down to Action. We are going to choose Action.

Under Action, what are we looking for? Sync Record to PhoneBurner. So search for Sync Record to PhoneBurner.

The label can be whatever you want it to be. In this particular case, I am going to name this one Sync New Contacts to PB.

All right. That is that.

What is the next thing we need to do?

Toggle on Record IDs. What does that mean? Right here, under Set Input Values, toggle on Record IDs.

Now what do we need to do?

Going back here, it says: Toggle on Record IDs. Click into the field, select Triggering Object, then choose the ID field. Use Object ID for standard objects and Record ID for custom objects.

We selected the Contact object, so we are looking for Contact ID. If you had a custom object, it would just be Record ID.

Let's go back over here. We are going to click in here, go to Triggering Contact, and then we should be able to find Contact ID in here somewhere.

Where are you?

There it is. Contact ID.

So, Triggering Contact - Contact ID.

Let's double-check and make sure we have everything here.

Save and activate.

We are going to click Save. I am going to call this one Contact Sync New Contact, and then we will save it.

Okay. We have our first flow created, but we have to do two of them.

Let's jump back over to Flows. We are going to click New Flow. Again, we are going to do Record-Triggered Flow.

We are going to choose the Contact object. This will not be a record-created flow. It will be a record-updated flow.

So, only when it is updated. If I can click on the right thing: A record is updated.

Set the entry condition. This will be “All Conditions Are Met,” and we are monitoring, in my case, the Contact Status field.

Again, it is totally up to you what you choose here. It will be based on whatever field you have configured in your sync settings.

In this particular case, I do not want to do “field equals value.” I am looking for Is Changed equals True.

We are going to go back over here. That is not the one I want. I want this one.

Contact Status - Is Changed - True.

Anytime that Contact Status field is changed, I want this flow to be invoked. I want this to run.

So we are good there.

What is the next thing we need to do? Run immediately, click the plus, and go to Actions.

Looking back at our instructions: Run immediately - Action - Sync Record to PhoneBurner.

We will go back here and choose our Sync Record to PhoneBurner action.

We are going to label this something like Contacts Updated.

Under Set Input Values, we are going to go to Record IDs and toggle that on.

Enter Value or Search Resources. Again, this is Triggering Contact, and I am looking for the Contact ID.

Again, this is a standard object, so it is Contact ID or Lead ID, depending on which one. If it is a custom object, it is just Record ID.

Once we have found that and applied it, we can hit Save. This is going to be Contact Update.

Give it a name, save it, and activate.

Did I activate the other one? I did not activate the other one. Do not forget to activate them. If you do not activate them, they will not do anything.

Now that we have that done, it is important to note that step six will never show as completed here. It just does not ever show as completed because there is no way for me to use automation to see if you created a flow that does what you need it to do.

It will always show as not completed for step six, but that is fine.

Now that we have turned that on, let's see if it will work.

I already have contacts in my PhoneBurner account. What was it? We did the Salesforce Contacts folder, right?

I have 352 contacts in here. We want to be able to see our contact move.

Actually, who are we looking at? Let's go back to Adam.

Adam is currently set to New. So let's actually look at a different folder. Rather than looking at the folder where the new contacts will go, because he already has New and we are going to edit him and change that, let's go to Closed Won.

There are only four contacts in my Closed Won folder. Let's go ahead and change him to Closed Won.

Before I save that, let's double-check our sync settings. We have Closed Won. Uh-oh. I do not think that is an exact match.

Closed space dash Won. I might need to update that. Closed space dash Won.

Make sure it matches on case as well, just to confirm that it is correct.

That is going into the Closed Won folder. Let's resave our sync rules.

Now, let's scroll back up to the top. You will see it says the sync rule deployment started, and it has a job number.

If there is an error or an issue, you can always go to your Deployment Status and see what may have errored out.

As long as everything went smoothly, we should be able to refresh this page.

There we go. After refreshing, that message is gone. That means the deployment worked appropriately, and we should be good to go.

If we look down here, everything is still set, saved, and ready to go.

Let's give this a test.

Let's jump back over to our sample contact, Adam Warlock, and make a change to see if everything updates.

We are going to set it to Closed Won and click Save.

Now he is officially set to Closed Won in Salesforce.

Here, we are back in PhoneBurner looking at our Closed Won folder. If we refresh this, there we go. We have Adam Warlock here in our Closed Won folder.

You will notice that he does not have the word New next to him because I have actually already synced him over to the system at one point in the past. So now he is just updated.

In here, let's look. It looks like I may have messed something up with my sync settings. Look at the address.

You know what? I know what I did. I think I did not choose Mailing Street Address. I chose Mailing Address, and I think that is why this is all incorrect like that.

But if we go down here, we will see that Created Date is there.

Let's double-check our sync settings here.

We have Additional Fields. No, not Additional Fields. It is a standard field here.

Mailing Address. I think this is where I made the mistake. I chose Mailing Address, which I believe is the full address, but what we really want is the street address so that we can send just that over.

Let's save those settings.

This will actually be good. It will give us a chance to test moving him into a different folder.

Let's go back to Adam. We can see he is Closed Won. Let's change him to Working. Then update him and save.

Let's go back to Contacts. Let's go back to Adam over here on the PhoneBurner side. Let's refresh.

It fixed our address, and he is now in the Stop Calling folder.

There you go. We are now syncing the contact from Salesforce over to PhoneBurner so that contacts are going into the appropriate folder where they need to be, so we can have our team calling through these contacts, primarily, in my opinion and most likely, through LeadStream.

That way, you can have a shared pool of data that your team is calling through. Obviously, you do not have to use LeadStream with this.

Now that we have contacts syncing over to PhoneBurner, and we have shown how we can sync contacts over to PhoneBurner, how do we take advantage of this on the PhoneBurner side?

Obviously, you could just start calling them, but we want to make sure we are taking full advantage of this Salesforce integration.

Let's talk about that.

In the upper-right portion of the page, I am going to click on my initials and go down to Integrations.

From Integrations, I am going to click on the Salesforce option and scroll down to the section where you will see Dialing via PhoneBurner LeadStream.

This allows you to define whether you want to enable and take advantage of this specific feature. By default, this will be turned off. It will be set to No.

Let's switch that to Yes.

Now we need to define the specific object that we want to be dialing from the PhoneBurner side.

Obviously, if we are starting from Salesforce, we know the object based on where you start that dial session from. But when you are syncing data over to PhoneBurner, you are always starting from PhoneBurner. We do not have that object-specific information.

In my particular case, I set this up to sync records from the Contact object, so I am going to update that to Contact.

Then there is one other question here: Do I want to see the Salesforce iframe?

When I am dialing, do I want to see the full record as it is on the Salesforce side? I highly recommend that. That way, you do not have to sync as much data over to PhoneBurner.

There are certainly reasons why you might want to sync a limited amount of information over to PhoneBurner and use the PhoneBurner UI instead of the iframe, but I am going to set this to Yes.

I cannot remember if it was Yes or No when I got here because I have been playing around with settings all over the place.

Anyway, I am going to have that set to Yes, and I am going to save settings.

Now, if everything is working properly, I should be able to go back to, what was that? Was that Closed Won? No. Where did we move him? It was Stop Calling.

There it is.

We have Adam here. We know we just brought him over as a contact. Let's begin a single-contact dial session to Adam.

Here we go. Grant mic access. Start dialing.

Here we are. When dialing, we should see the iframe. There it is. It just took a minute to load for whatever reason.

We see the iframe with the contact details as they are on the Salesforce side. I can edit this record here if I want to edit it.

Just remember, if you edit it, you want to save those settings, and that will save directly in Salesforce. PhoneBurner will not see that change because this is all happening directly on a Salesforce page.

I am going to disposition Adam. Let's go ahead and mark it as Live Answer, end the call, and mark him as Set Appointment.

That ends our dial session because that was our only contact, and we set an appointment, so there is no reason to call him on other lines.

Now we should see an activity log over here in Salesforce shortly. Let's refresh.

There it is: Call with PhoneBurner - Set Appointment.

Going back to PhoneBurner, let's jump back over to our Salesforce integration and go down here to the Dial via PhoneBurner LeadStream section.

There are a couple of things I want to mention here.

For that iframe, if you want to see the iframe show up and you are dialing records from a custom object, you do need to configure it. You need to create a configuration for that custom object.

I have a little note here, and I direct you to the Salesforce training because we do talk about it there. I am not going to go into the details here.

But if we go back here, Create Configuration. In the PhoneBurner Lightning App, you will see this Create Configuration option, where you can choose that object and go through all those steps.

Again, I am not going to bore you with that part in this specific video because I already have training for that, and this video is already long enough.

I did want to point out that you can dial from custom objects, or dial records in a custom object. But if you want that iframe to show up, we need you to complete that configuration.

Anyway, I know this has been a longer training. I hope this helps you and your organization continue to get the most out of PhoneBurner so your organization can close more deals, write more business, and connect with more people using the power of PhoneBurner.

Thanks again, and happy dialing.