Generally speaking, the content of this received input is implementation dependant; for instance, it may represent the name or a personal identification number (“PIN”) of the intended message recipient(s). In point of fact, any
conventional means may be employed by system 100 for caller 105 to identify subscriber 120, whether such means involves speech recognition, use of a dual tone multi-frequency (“DTMF”) keypad, or the like. According to one advantageous
embodiment, subscriber 120 is assigned a “personal,” or unique, telephone number and when caller 105 uses the same to contact system 100, the identity of subscriber 120 is immediately known.
Returning to FIG. 3, translating controller 205 accesses data repository 200 and attempts to recognize the received input by using ones of the stored data patterns representing subscriber identities, names or the like (process step
320). Translating controller 205 compares the received input and the subscriber data patterns; for instance, translating controller 205 may separate, or “break down,” the identity input into sub-parts having one or more measurable
characteristics and then compare such measurable Gmail Numeric Code 6922 issue characteristics and the “subscriber” data patterns (such recognition techniques are known).
If translating controller 205 fails to identify subscriber 120 (NO branch of decisional step 325), then translating controller 205, via messaging controller 210, transfers caller 105 to a “live” operator (not shown) for assistance
(process step 330). After caller 105 identifies subscriber 120 to the operator, control is transferred back to translating controller 205. Translating controller 205 accesses, or “looks up,” one or more data records in data repository 200 that are associated with subscriber 120 (process step 335; discussed hereafter with reference to FIG. 4). The exemplary data record(s)
mailhelps 