It seems that we can in fact change the divert number as well as the primary recipient. I don't know how long this has been the case but I found it whilst digging around their web site today.
This has already been tested and is a minor variation on what we already have in place. The example on their web site shows changing both values in the same call but I can't see that we need to always do that. I have successfully changed the divert without affecting the primary routing using this method.
There might be a need to track calls we've sent, in order that we can read them back and compare them. For instance, if Geoff's on the calendar, he shouldn't have the divert. He self-manages this at the moment but, if procedure could be agreed, it could equally be automated. As a starter to the discussion, either tomorrow night's controller or next week's controller could be used.
It seems that we can in fact change the divert number as well as the primary recipient. I don't know how long this has been the case but I found it whilst digging around their web site today.
The API URL is https://www.flextel.ltd.uk/cgi-bin/reroute.sh?alt=simple&mode=divert&flextel=SERV_NOW_Number&pin=PIN_Goes_Here to which you can append either or both of:
This has already been tested and is a minor variation on what we already have in place. The example on their web site shows changing both values in the same call but I can't see that we need to always do that. I have successfully changed the divert without affecting the primary routing using this method.
There might be a need to track calls we've sent, in order that we can read them back and compare them. For instance, if Geoff's on the calendar, he shouldn't have the divert. He self-manages this at the moment but, if procedure could be agreed, it could equally be automated. As a starter to the discussion, either tomorrow night's controller or next week's controller could be used.