Track every Plivo number porting request to completion
Every morning, WebRun opens the Plivo console, checks the status of every number porting request in progress, holds the expected completion date on the ops team's Google Calendar, and sends an internal WhatsApp alert the moment a port actually completes so the number can be put into use right away.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I track my Plivo number porting requests?
WebRun checks the Plivo console every morning for number porting requests in progress, holds the expected completion date on Google Calendar, and sends ops an internal WhatsApp alert the moment a port actually completes, so a newly ported number gets put into use the same day instead of sitting unnoticed.
- Porting status is checked every morning without a manual login
- Ops is alerted the same day a port actually completes
- Delayed ports stay flagged instead of getting lost
Built for telecom admins · CPaaS developers · IT teams · VoIP resellers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
console.plivo.comin a real browser with your saved login - no setup, no API keys. -
1
Plivo - check porting status
WebRun opens Plivo to check porting status. - Open the Plivo console and list porting requests in progress
- Note the current status and expected completion date for each
- Flag any request past its expected date
Done when Every in progress porting request's status is known.
-
2
Google Calendar - hold the expected completion date
WebRun opens Google Calendar to hold the expected completion date. - Add or update a calendar hold for each request's expected completion
- Include the number being ported
- Move overdue requests to a flagged date
Done when Every porting request has a calendar hold on its expected date.
- 3
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does WebRun submit or approve the porting request?
No. It only tracks the status of a porting request your team already submitted through Plivo and reports on it. Submitting or approving the port is still done by your team.
How is a completed port confirmed?
By the status change in the Plivo console itself, which is the same status your team would see checking manually, WebRun just checks it every morning so you do not have to.
What happens if a port runs past its expected date?
It stays flagged on the calendar and in the tracker until it either completes or a new expected date is set, so a delayed port never quietly disappears.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.