A
voice application could be triggered to make an outbound call by an
event
such as a seat becoming available on a flight. The voice application
then
follows a sequence like this:
- The application makes a telephone call, for example to a passenger
who
is on the waiting list for a flight, and whose telephone number is
stored
in a database.
- If Blueworx Voice Response makes
the call (using state tables, Java or CCXML), it can determine
whether the call is answered or if the line is busy.
- Blueworx Voice Response plays
a recorded or text-to-speech greeting, which might start
by asking the called person to confirm that they are the person for
whom the
information is intended. The application can ask for, and check, a
password
or personal identification number. The application then speaks the
information
to the called party. It can then prompt the called party to say what
to do
next.
- After the initial greeting, an outbound call follows
much the same sequence
as an inbound call. The called party should have the opportunity to
ask for
other actions to be taken. Depending on your business requirements
you can
offer a range of actions in your application.
- As with an
inbound call, either the called party or the Blueworx Voice Response application
can end the interaction. The called party may either hang up, or tell
the
application not to take any further action, in which event the application
must disconnect.