Automated Call-Out
From PCSAR
(Difference between revisions)
(→Options) |
(→Options) |
||
| Line 79: | Line 79: | ||
| Response, How long before I'm there || no || yes | | Response, How long before I'm there || no || yes | ||
|} | |} | ||
| + | == Deployment == | ||
| + | * (done) set up Rapid Notify subaccount | ||
| + | * (done) automate updating from call-out list | ||
| + | * set up logins for call-out personnel, managers | ||
| + | * train call-out personnel, managers in use of system | ||
| + | * have call-out personnel, managers take Rapid Notify course | ||
| + | * develop standard message text | ||
| + | * distribute info to members on what to expect, how to use | ||
| + | * test with each member; identify numbers that should not be called by automated system | ||
Revision as of 11:30, 20 February 2013
PCSAR is planning on implementing an automated call-out system, where a computer simultaneously dials the members and plays a message alerting them to the event.
Options
Two offers to piggy-back on existing systems have been made.
As part of the H2S Protocol, Shell has offered use of their system.
The Pincher Creek Community Emergency Management Agency (PCCEMA) is rolling out a system of their own to notify residents of major emergencies.
There was also a commercial option that Eric Bruder was looking at. Unfortunately, I don't have the details on which system that was.
| Feature | Shell | PCCEMA |
|---|---|---|
| Terms | ||
| Cost | free | one free usage per month; thereafter US$.15/call (about CA$20 for a full call-out) |
| Advantage to partner | tests their system; practice | tests their system; PCSAR callers could be asked to help with PCCEMA incident |
| Future | long term | PCCEMA is renegotiating with its supplier RapidFire in one year; expect to be able to continue offer to PCSAR |
| Initiation | ||
| By phone | yes - call Shell | yes - call 24hr Customer Service, provide password |
| By computer | no | yes |
| Who is Contacted | ||
| Predefined lists | one | unlimited; e.g. each type of call |
| Select from within list | no | no |
| Merge lists | no | yes, but duplicates called multiple times |
| Call only those that haven't already been called on another list | no | no |
| Try again - call those that didn't answer | no | yes |
| Phone numbers per contact (list entry) | 2 (but multiple entries) | 3 (but multiple entries) |
| Dial an extension | no | no |
| Play person's name - who is being asked for? | no | no |
| Messages | ||
| Prerecorded messages | 1+test | unlimited |
| Record on the fly | no | yes |
| Caller ID displayed | Shell's phone number | Any phone number; Call Back # |
| Send text message | no | yes |
| Send email | no, but PCSAR provides | yes |
| Reports | ||
| verbal | no | no |
| no | yes | |
| online | no | yes |
| who was called | no | yes |
| which numbers answered | no | yes |
| Response, I can come | no | yes |
| Response, How long before I'm there | no | yes |
Deployment
- (done) set up Rapid Notify subaccount
- (done) automate updating from call-out list
- set up logins for call-out personnel, managers
- train call-out personnel, managers in use of system
- have call-out personnel, managers take Rapid Notify course
- develop standard message text
- distribute info to members on what to expect, how to use
- test with each member; identify numbers that should not be called by automated system
