Automated ServiceNow Change Approval Chasing
Every morning, WebRun opens ServiceNow, reads the change requests still awaiting approval, compares each planned start date against the approvals still outstanding, names the approver and assignment group holding each one, sends the change manager a Telegram list, and queues a Twilio text for high risk changes that will miss their window.
How do I stop change requests missing their approval window?
WebRun reads the ServiceNow change queue every morning and compares each planned start date against the approvals still outstanding. It sends the change manager a Telegram list naming the approver and assignment group holding each request, and queues a Twilio text for high risk changes about to miss their window.
- The board meeting starts from a clean, current list
- Every at-risk change names the approver holding it
- High risk slippage gets its own alert instead of hiding in the queue
Built for change managers · ITSM teams · IT operations · service delivery leads · managed service providers
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
signon.service-now.comin a real browser with your saved login - no setup, no API keys. -
1
ServiceNow - read pending change approvals
servicenow.com
WebRun opens ServiceNow to read pending change approvals. - Open ServiceNow and filter the change table to requests still in an assess or authorise state
- For each change, read the planned start date, the risk, the assignment group and the approvals outstanding
- Work out which changes will reach their planned start date before every approval is in
- Name the approver each request is waiting on and how long it has been sitting with them
Done when Every pending change carries its planned start date, its risk and the approver holding it.
-
2
Telegram - send the change manager the list
telegram.org
WebRun opens Telegram to send the change manager the list. - Send the change manager a Telegram list of what is pending this morning
- Put changes that will miss their planned start date first, with the number, the risk and the approver
- Group the rest by assignment group so the board meeting can work through them in order
- Note any change that has slipped its planned start date more than once
Done when The change manager has today's queue with the at-risk changes at the top.
-
3
Twilio - queue a text for high risk changes
twilio.com
WebRun opens Twilio to queue a text for high risk changes. - Queue a short Twilio text for high risk changes that will miss their window without an approval today
- Name the change number, the planned start and the approver in the message
- Leave the text queued for a human to release. WebRun never sends a text on its own
- Skip the queue on mornings where no high risk change is at risk
Done when High risk changes have an alert queued and waiting for a person to release.
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
Will it approve a change request?
No. WebRun reads the change table and reports what is waiting and on whom. Approving, rejecting or rescheduling a change stays a human action inside ServiceNow.
Does it text approvers by itself?
No. High risk alerts are queued in Twilio and wait for a person to release them. Only the internal Telegram list is sent on its own.
Does it touch incidents?
No. This template reads the change table only. Incidents, their SLA clocks and their assignment stay entirely untouched.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.