Skip to main content

The Saga of EA Customer support part 5

Jan 5, 2017 (14 Days after the initial contact)

At 2:24 AM I was sent the following in reply to my 3rd ticket where I stated that I was going to become a nuisance.
Thank you for contacting Electronic Arts Customer Experience.
I sincerely apologize for the delay caused in responding to your issue and appreciate your patience. This is ***** from the Game team following up your incident. 
I would like to inform you that your case was escalated to the dedicated team. In this case I suggest you to wait for email from the specialist team. 
Should you have any further questions regarding this or any other issues, please do not hesitate to let us know. You can also find answers to common questions on our Help Center at http://help.ea.com , or ask our community experts by visiting Answer HQ at http://answers.ea.co
This reply also closed the ticket.

At 5:26 PM I replied with the following:

Hi,
Thank you for taking the time to update me on this issue. However:
Acording to ITIL, The ticket isn't closed until both of the following are true:
  • An assigned engineer says it is over.
  • Customer contact person confirms it is over OR a reasonable amount of time passes since the resolution without the customer complaining.
Since neither of those are true, I am reopening this ticket, as well as the other tickets I have regarding this issue.

I believe that I sent the same reply back to my second ticket as well after it had been marked closed by the CSR.

At this point I guess I should be happy, I seem to have a bit of a dialogue with someone on the other end.  Unfortunate that it's about procedure, rather then being about the bug.
Labels:

Comments

Post a Comment

Popular posts from this blog

8Bitdo NES 30 Pro on linux

This post will go over the setup I had to do to get my   8Bitdo  NES30 Pro controller working on my Arch linux desktop with steam.  This results in the system loading the xboxdrv automatically when the controller is connected, and unloading once finished. Firmware Update The first thing to tackle was the firmware update on the controller,  This may not be needed, but I like to keep my devices up to date. After some googling, I was able to find a program called fwupd  that's able to update the controller via a USB connection.  It's available for Arch in the community repo. The basic syntax of the command is: fwupdmgr get-devices fwupdmgr refresh fwupdmgr get-updatessudo fwupdmgr update The controller will need to be put into 'Firmware update mode'.  Be aware that the final command will also update all eligible firmware on your system, so If you don't want that, please dig into the documentation Bluetooth Connection G...
1 comment
Read more

Craftware 1.17 on Arch Linux -- notes

Craftware a slicer for 3d printers is available for linux here .  It looks pretty good, and is supposedly multi threaded with support for hardware acceleration. I can only find it  as a deb file, and there's nothing in the AUR for it. I tried a few of the common methods for installing debs: debtap While it was able to create a package, upon installing it I got this error loading packages... error: failed to prepare transaction (package architecture is not valid) :: package craftware-1.17.1-1-i686 does not have a valid architecture So.. No good. I tried just extracting the package content, and running the binary: ./craftware: error while loading shared libraries: libomp.so: cannot open shared object file: No such file or directory and yes, it is installed. $ ldconfig -v           libomptarget.so -> libomptarget.so          libomp.so -> libomp.so          libzit...
1 comment
Read more

Dropbox Nov 2018 workaround

So Dropbox is no longer supporting anything besides ext4 on linux as of Nov 7th 2018.  Here's how to work around that WITHOUT superuser permissions. First, create a sparse file of whatever size you'd like for your Dropbox folder. $ truncate -s 5G ~/.Dropbox.img Now we need to format this as ext4, But we want to make sure that we own the created file system, not the default of root. $ mkfs.ext4 -E root_owner=$(id -u $USER):$(id -g $USER) ~/.Dropbox.img Setup the loopback device with our EXT4 image $ udisksctl loop-setup -f ~/.Dropbox.img You may need to mount the device if it hasn't been already: $ udisksctl mount -b $CREATED_LOOP_DEVICE Check where our filesystem is mounted: $ mount | grep Dropbox.img Move any existing data from the previous dropbox folder to the new location: $ mv ~/Dropbox/{.,}* /$MOUNTPOINT/OF/DROPBOX/IMAGE/UUID$ Link our new folder back to the dropbox folder $ ln -s  /$MOUNTPOINT/OF/DROPBOX/IMAGE/UUID$/ ~/Dropbox You can now star...
Post a Comment
Read more