Path: utzoo!utgpu!watserv1!watmath!att!att!tut.cis.ohio-state.edu!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!ucsd!ucselx!bionet!hayes.ims.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request From: FLINTON@eagle.wesleyan.edu (Fred E.J. Linton) Newsgroups: comp.dcom.telecom Subject: "Re: Wrong Number Suggestions Needed" Message-ID: <14305@accuvax.nwu.edu> Date: 4 Nov 90 07:31:38 GMT Sender: news@accuvax.nwu.edu Organization: TELECOM Digest Lines: 23 Approved: Telecom@eecs.nwu.edu X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@eecs.nwu.edu X-Telecom-Digest: Volume 10, Issue 788, Message 5 of 10 In <14216@accuvax.nwu.edu> Craig R. Watkins writes: > When people call the old published Sears number, XYB-2451, they get an > intercept: "The number you have reached, XYB-2451 has been > disconnected; calls are being taken by XYA-5600..." The problem is > that two or three people per day match the old exchange and the new > number and dial XYB-5600 and get Dave. How about an intercept on Dave's number with the following message: "If you are trying to reach Sears at their new number, please hang up and try your call again, dialing eks wye EIGH , five six hundred . That's eks wye EIGH , , five six hundred . If you are calling the residence, please stay on the line, you will be connected in a moment." Then a 10-second timeout; and action to match the message. Might even work -- if the local Bell company were willing :-) . Fred or