VoiceCast operates similarly to an auto dialler service. It allows users to send robotic calls to telephones using a simple and intuitive interface.
As a large amount of the complexity is hidden to the end user, this section is designed to inform the average user on how we handle their calls, allowing them to make better decisions when creating VoiceCasts.
From the Call Recipient's Perspective
When a call is made using the VoiceCast system, the call will appear on a recipients telephone or mobile phone in the same way all other telephone calls do. They will see an incoming call and their phone will begin ringing.
By default, we set the Caller ID on VoiceCast calls to "Private". This will show on the recipients telephone as "Private Number", "Number Withheld", "Blocked" or another variation depending on their telephone supplier. We can display a custom Caller ID to represent your business if you prefer.
Once the call has been answered, we allow the recipient a few moments to answer the call. Normally, when answering the phone, a recipient will begin the call with "Hello". Once this initial "Hello" has been detected, VoiceCast will begin playing your main voice message. Should the VoiceCast system not detect this initial "Hello", it will wait a few moments then begin playing your message. Should a "Hello" be detected after play has begun, it will halt the message, then restart from the beginning.
If we have detected that the call has been answered by an answering machine, the VoiceCast system will cease playing the main voice message and begin playing your Answerphone message (if no Answerphone message has been set, the main message will begin playing again).
For a simple VoiceCast call without a keypad option, the voice message will play through once, then hang up.
If you have specified a keypad option, the VoiceCast system will wait a moment for the recipient to press a telephone button. If nothing is pressed, the message will play through a second time (allowing the recipient to press a keypad button at any time). If no keypad button is pressed, the call will end.
If the recipient presses a keypad button, the VoiceCast system will move to the next option, as specified by your configuration. The VoiceCast engine will then include the keypad buttons that were pressed in the final report that you will receive.
From the Telephone Network's Perspective
When the VoiceCast engine creates a call, it appears on the telephone network just the same as any normal telephone call. This allows the VoiceCast system to be compatible with almost every telephone network worldwide.
Should the call recipient be on the telephone, VoiceCast will understand this and queue the call for retry later.
Should the telephone number be invalid, VoiceCast will understand this and mark the call as a failure.
For the initial voice versus answerphone detection to operate reliably, VoiceCast keeps both ends of the call live for audio analysis. This allows for options such as DTMF Keypad Buttons to be pressed, voice messages to be recorded, etc.
VoiceCast will usually keep a recording of every successful call, however this is usually accessible by Technical Engineers only for debugging and not released to clients or users.
From the User's Perspective
As a user, we want your experience to be just as fluid and professional as you want the call recipient's to be.
Should you need any further information or details on the call, assistance in setting up a call or a complex survey, additional instructions on how to operate VoiceCast, or anything else, don't hestitate to get into contact with one of our staff.