next up previous contents
Next: Dialout Up: IVR Applications Description Neda Previous: Private Applications   Contents

Subsections

POTS Access to Neda's Messaging Services (IVRMSG)

Introduction

Using an Interactive Voice Response (IVR) capability, calllers will be able to communicate with two-way subscribers through PSTN/POTS.

Using the IVR functionality, the callers will be able to:

Also, using the IVR functionality, the subscribers should have access to the MC stored messages.

Objectives

The major marketing objectives aroe to:

Description

IVR provides capability for a caller to originate message and to check message status. Several services may use IVR capability. These services may include human interaction (e.g. operator services) to originate messages, or they may be restricted to equipment interactions between a WES to acknowledge the network the receipt of a message. This IVR capability description includes capabilities related to the user interface and interaction between different network elements.

The callers, subscribers or non-subscribers, should be able to get access to all of the following options via a single number:

The subscriber should have access to the MC stored messages using text-to-speech translation.

IVR requires caller information be sent from the caller to the network. Data which must be sent includes destinations address, message type, message content, and origination address. The message type provides information about the purpose of the message, such as if it is a system acknowledgement, user acknowledgement, numeric paging, alpha message, or response to a message. The message content provides the information that is displayed or used by the receiving equipment or subscriber (e.g. call back number or free text entered by an operator). The origination address provides the identity of the caller that is originating the message. An optional urgency indicator is also available for message originators who wish to attach an urgency level to the message (the urgency level is an annotation only and does not speed delivery through the network).

Interactive Voice Response Menu

The caller's interface should allow an experienced caler to bypass system prompts. Independent of the access method, after the greeting, the caller will be prompted to identify the subscriber. A menu should provide options that depend on what services are listed under subscriber profile.

If new messages are originated, the caller may hang up after 7 or 10 digit numbers are entered. The system should accept this information and rely it to the MC for routing. If a 10 digit number was entered, then the system should append (1).

If the caller requires a reply, the system prompts the caller's confirmation number (CCN).

Normal Operation With Successful Outcome

Incoming calls will be answered by a Front End System (e.g. Summa4 switch) (FES). The Figure 1 depicts the Front End System (FES), the Voice Mail System(s), the Message Center (MC), and the Operator Services System (Op. Serv.). The MC routes all messages to the subscriber's wireless end device.

Figure 1: Normal Operation
Normal Operation

The FES answers the call and plays a greeting. If the access method is through a personal 800 number then the calls are answered with a greeting specifically for your subscriber. For all incoming calls

  1. FES prompts the caller for the subscriber identification (PIN), if the access method was through a non-personal 800 number.
  2. FES adds the MC/VAS on the call and the PIN is verified.
  3. If the PIN is correct, the caller is prompted with an appropriate menu to enter the menu option
     1 - numeric paging
     2 - voice mail
     3 or time out - transfer to an operator
    

Case 1 - caller enters digit 1

Case 2 - caller enters digit 2

Case 3 - caller enter digit 3 or a time-out condition occurs

Case 4 - caller enters digit 4

Checking Message Status

WES provides an acknowledgment that a message was accurately received. This acknowledgment is transparent to the user of the WES. The acknowledgment includes address information of the originating message, address of the WES, and the time the message was delivered. The caller should be capable to call and check the status of a previously submitted message.

The caller will be able to check on the status of message up to 72 hours after the message was originally sent. If all subscriber messages are successfully delivered, then a generic system message (e.g. all message were delivered) will be played to the caller and no message identification is needed.

If the delivery status of the message is negative, the system should

Access to Subscriber's Reply

The subscriber will be able to check the reply of messages up to 72 hours after the message was originally sent. The caller will be able to check replies in the same way as the caller has access to the message status. Only a caller requesting a reply and indicating a CCN at the time the message was originated will be capable to access message replies.

Subscriber Message Retrieval from MC

The subscriber should have access to the MC stored messages. The access can be through:

If the subscriber slects to retrieve messages directly from MC, in the log-in session, subscribers shall be required to enter PIN.

A message including the number and types of new messages should be available. As the subscribers retrieve the new messages, they will be offered the options of repeating, deleting, or sending a reply.

All messages are time stamped and presented to the subscriber in the order of their arrival. The time of a message reception needs to be reported relative to ``now'' (e.g. you received a message 2h and 15min. ago). For message over a day old, it is acceptable to report delivery time in standard format.

The MC should support an integrated mailbox (e.g. one mailbox for all email, paging and notification messages).

User Interface

  1. IVRMSG system goes onhook, waiting for a call.
  2. After ring detection it plays introduction message. Example: ``Welsome to Interactive Voice Response System ffor Limited Size Messaging system.''
  3. Next play a request for subscriber ID. Example: ``Please enter your subscriber ID.''
  4. The subscriber ID entered is checked for correctness and then saved. In case of error, the user is given a second chance to enter a correct subscriber ID.
  5. Next plays a request for the recipient subscriber ID. Example: ``Please enter the recipient subscriber ID.''
  6. The recipient subscriber ID entered is checked for correctness and then saved. In case of error, the user is given a second chance to enter a correct recipient subscriber ID.
  7. Next plays a request for selection. Example: ``Choose from this menu of canned messages:
    1. [1] Will be late.
    2. [2] Got your message.
    3. [3] Yes, can do.
    4. [4] No, can't do
  8. The selection entered is checked for correctness and then saved. In case of error the user is given a second chance to enter a correct selection.
  9. Next plays a request for second selection. Example: Press
    1. [1] to review your message.
    2. [2] to add additional recipients.
    3. [3] to send the message.
  10. The selection entered is cheked for correctness and then saved. In case of error, the user is given a second chance to enter a correct selection. If 1 is selected start at the top with the addition of playing the ID and giving them a chance to change it. If 2 is selected request for additional recipient subscriber ID. If 3 is selected continue.
  11. Send the email information to send mail program.


next up previous contents
Next: Dialout Up: IVR Applications Description Neda Previous: Private Applications   Contents