We’ve all heard it. “This call may be recorded for quality assurance purposes.” These recordings are used by Customer Service Managers to improve quality of service and coach agents they care for. If you’ve built a Twilio-powered contact center, chances are you are recording these calls. Your service works great, business is booming, and one day you look at your Twilio account and you see this:
It turns out you’ve been recording every single call over months of service and you haven’t cleaned it up! To optimize your operations and lower cost, you want to delete the ones you don’t need. In this blog post we’ll use Twilio’s Recordings API and some of Python’s built-in library to delete your recordings quickly and efficiently.
What We’ll Need
Let’s walk through how to create a recording deletion script with Python. You need ...
Communications technology is deeply embedded in our daily lives. Sending a text, making a call, or reaching out to a customer is so instantaneous it feels like second nature. Proper security measures preserve that sense of second nature, and that sense of trust, so there’s no pause before you fire off that text.
At Twilio, security is always on our mind. To keep you in the loop of what we do to keep your workflows secure, here’s a rundown of the security measures we’ve shipped in the past year, and what’s coming next.
We understand that many of you have internal security frameworks, and we have structured the whitepaper to match up some of the ones that are common amongst our users. This will make it easier for you to find what you are looking for. We recommend that you check the Security Whitepaper out.