[VoiceOps] Fraud
Matt Yaklin
myaklin at g4.net
Thu Feb 20 14:03:29 EST 2014
Did you reach out to your upstream provider who you sent the
calls to and ask what they can do for you? See if they will
forgive the bill since they were obviously fraudulent? Then
do the same for your customer?
Have you offered the customer to cut his bill in half for the
calls since you probably mark them up 100%? In other words give
him your exact cost and see if that helps the situation?
matt at g4.net
On Thu, 20 Feb 2014, Hiers, David wrote:
>
> That actually works out great for you.
>
>
>
> There is a federal law that limits credit card customer fraud liability to $50.
>
>
>
> Go to court. There is no federal law that limits phone customer fraud. If you don't have such a clause in your contract, you can't lose the case. The
> customer may walk, but that might work out in your favor.
>
>
>
>
>
>
>
> David
>
>
>
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of John Curry
> Sent: Wednesday, February 19, 2014 14:09
> To: voiceops at voiceops.org
> Subject: [VoiceOps] Fraud
>
>
>
> I am new to your site. I was looking in the Archives and saw in November 2013 there were some of you who experienced fraud. We had a an Avaya IP Office
> customers system who got hit pretty bad. The customer is treating the fraudulent calls like credit card fraud and not taking any responsibility. Does
> anyone have any advice on how to persuade the customer take this issue seriously? His bill was racked up pretty good. Strangely and coincidentally Avaya
> came out with a security bulletin the end of December 2013 on this same issue. I tried to contact Avaya with no response. It seems as though someone has
> built a sniffer for the Avaya IP Offices and gleaning their registrations.
>
> ___________________________________________________________________________________________________________________________________________________________
>
> This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and
> confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are
> hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please
> notify us immediately by e-mail and delete the message and any attachments from your system.
>
>
>
More information about the VoiceOps
mailing list