Multiple Call End Webhooks in PhoneBurner

Summary:

This video provides a detailed walkthrough on how to configure multiple web hooks for the “Call End” (or “Call Done”) trigger in the PhoneBurner system. The “Call End” web hook activates when a disposition is clicked at the end of a call. Previously, users relied on Zapier to handle multiple destinations using comma-separated IDs. Now, PhoneBurner natively supports sending the call end payload to multiple endpoints by separating each web hook URL with a comma (no spaces). This can be configured either at the account level or per disposition. The video demonstrates how to set this up and validate it by showing the call data logged in a Google Sheet via Zapier. This enhancement allows for greater flexibility in integrating PhoneBurner with multiple external systems simultaneously.

Tags:

web hooks, call end trigger, PhoneBurner integration, Zapier, CRM automation, outbound calling, disposition settings, automation tools, Google Sheets, multi-endpoint data

Cleaned-up Transcript:

Hopefully, you’ve been watching all of my web hook training. I mean, why wouldn’t you? I’m super entertaining, right?

Anyway, the web hook training module is designed to help you understand all the options available for triggering web hooks within the PhoneBurner system. One key trigger is what we refer to as “Call End” or “Call Done”—we use both terms interchangeably here at PhoneBurner.

This particular web hook is triggered upon disposition. So let’s jump into PhoneBurner. Go to Dial Sessions, then Dispositions. Click on any dialing set—it doesn’t matter which one.

Every time you select a disposition, you’re indicating that the call to that specific number has ended. Since contacts can have multiple numbers, this is tied to the specific number just called. You can apply a “Call End” web hook either globally across your account or at the individual disposition level. If you set it at the disposition level, that will override the account-level setting.

Now, one common question I get is: Can I send the Call End payload to multiple destinations?

In a previous video, I showed how to do this using Zapier by entering multiple web hook IDs, separated by commas, into a single URL field. That worked because Zapier could route them accordingly.

But we’ve since updated PhoneBurner to natively support sending the Call End data to multiple web hooks. Let me show you how easy this is.

Let’s take our “Booked Appointment” disposition as an example. Imagine Zapier didn’t support multiple IDs—you’re using a different system or want to send data to two different places, like Zapier and another endpoint. Here’s how to do it:

1. Go to the disposition in PhoneBurner.
2. Add the first web hook URL (e.g., Zapier).
3. Without adding any spaces, type a comma.
4. Paste your second web hook URL.
5. Click “Save Changes.”

You can keep adding more URLs using commas (no spaces) between them. This setup works both at the disposition level and on the Web Hooks page at the account level.

Currently, this feature is only available for “Call End” or “Call Done” web hooks. If there's demand, we may expand it to other triggers like “Call Begin” or “Contact Displayed.”

Now let’s test this. I’ll go to Contacts and make a few calls.

Calling “The Flash”... Let’s say The Flash answers and we book an appointment. I might add some notes and update custom fields. Then I click on “Booked Appointment,” which moves me to the next call.

Now let’s check our Google Sheet. Within a few moments, we should see that data logged in the “Call End” tab—and there it is. The system has sent the data to both endpoints, just as expected.

And that’s it! That’s how simple it is to set up multiple web hooks for the Call End event in PhoneBurner.

I hope this helps your organization get even more value from PhoneBurner. Thanks again, and happy dialing!