Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!accuvax.nwu.edu!nucsrl!telecom-request From: Scot E Wilcoxon Newsgroups: comp.dcom.telecom Subject: Re: NY Tel New Service For Handling Operator Assisted Calls Message-ID: <1804@accuvax.nwu.edu> Date: 5 Dec 89 00:19:43 GMT Sender: news@accuvax.nwu.edu Reply-To: Scot E Wilcoxon Organization: Data Progress, Minneapolis, MN Lines: 28 Approved: Telecom@eecs.nwu.edu X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@eecs.nwu.edu X-Telecom-Digest: Volume 9, Issue 551, message 7 of 11 >[Moderator's Note: Can't you *just imagine* the fraud with this new toy? >On being asked to record their name, caller responds: >'Meet me at the airport at seven'; 'Call me back at acc-xxx-yyyy'; 'I do >not have change, but I'll be home soon.'; or a whole variety of messages >to which the callee can refuse to accept charges. Is telco going to >keep track of all the 'names' (heh-heh!) that callers use when placing >collect calls? I don't know what telco plans are, but it might be a profitable side effect. As the calls would undoubtedly get charged the minimum amount for a "collect" call, dredging for these lost calls could easily be worthwhile. Instead of several human operators handling many calls, a single operator could listen to the few recorded seconds from many calls and tap a "charge for call" button (or type the 'name') when appropriate. Security staff can start by with random sampling, and it could increase to a task to fill operator idle times (or not retiring an operator replaced by the automated service). A permanent record of corrected charged calls, and the legal differences between a phone call and an obvious recording should be useful. Should we consider it a "collect voice mail" service? :-) Scot E. Wilcoxon sewilco@DataPg.MN.ORG {amdahl|hpda}!bungia!datapg!sewilco Data Progress UNIX masts & rigging +1 612-825-2607 uunet!datapg!sewilco I'm just reversing entropy while waiting for the Big Crunch.