You, sir, are a friggin moron

[iradney]

So, *company* provides a service wherein you can kerfifle your joibles (most common one), and also gakoogle your miffnits.
All of our clients have chosen to kerfifle their joibles, with a percentage choosing to gakoogle their miffnits as well.

Now, we have clients, and their representatives - their reps sold *company*'s products to them and as such are their first point of contact for complaints and queries.

In this story, we have:

Me: Fabulous, darling
NagNag: Client
BlahBlah: Rep

Today, BlahBlah logged a call that NagNag couldn't gakoogle their miffnits the whole day so far (logged before noon today).

I give it to the techies, who duly begin investigating. Chat with the contact at NagNag and find out, OH! They've apparently been having this problem for a few weeks now! Ah! Wee!

BlahBlah literally phoned me about 12 times today about this issue, as NagNag was dogpiling them about it - I reminded BlahBlah that if NagNag had reported this issue when it first occurred, it would not be a problem any longer!!

After getting more and more irritated with these idiots, I passed it on to my supervisor to deal with.

My main gripe?

They had this issue for WEEKS. They only told us about it NOW. They're being completely unreasonable and expecting a damn near impossible turn-around time, and they're dicks. GAH! Is it asking to much to let us know when you actually get the problem, instead of days and days later? Hell, if I can do it, you can! Bloody morons!

[technical.angel]

kerfifle your joibles

Is it just me or does that sound dirty?

[Sientara]

Is it asking to much to let us know when you actually get the problem, instead of days and days later? Hell, if I can do it, you can! Bloody morons!

I have asked this before and usually the answer boils down to: we didn't need it then, but we do now.

The most amusing response was "we thought you shut it down for the holiday."

Couple of facts:
1. This was said 1 week after the holiday.
2. This was the outgoing fax server, not going to be shut down for anything besides upgrades.
3. I work for a hospital. We are 24/7.
4. They were the first to complain and they were not the only ones affected.

[Ironclad Alibi]

So, *company* provides a service wherein you can kerfifle your joibles (most common one), and also gakoogle your miffnits.
All of our clients have chosen to kerfifle their joibles, with a percentage choosing to gakoogle their miffnits as well.

Does *company* service the Retroincabulator?

[ArcticChicken]

Is it just me or does that sound dirty?

Nope, I went there, too.

[Fenrus]

Is it just me or does that sound dirty?

I goigetied her giflaygity with my googus, and for that, I'm am sorry...

Too obscure?

[Naaman]

I goigetied her giflaygity with my googus, and for that, I'm am sorry...

Too obscure?

Giggedy Giggedy ?

[EricKei]

Awwwl right!

We get this with our little low-end accounting software support, as well. People will get some little persistent data error every other day, but not call us about it until it's developed to the point that the file just won't open any more. Bonus points if it broke on the day they're trying to run payroll! Double bonus if we ask you how often you do backups and you respond "How do we do those?". Note that if the response is "we backup the server every day", the call time just tripled unless the next words out of your mouth involve your IT guy and "why, yes, we do have someone who actually knows how to RESTORE files from server backups". It only doubles if the IT guy can do Restores... PT in particular prefers its own backups to trying to reconcile the 30-odd files it needs to make up one dataset. That, and in-program backups run the Data Verification applet as part of the process...

Little news flash here, guys...If an ACCOUNTING package tells you any of these things, even if it doesn't happen very often, you need to give us a ring before the program rolls over and dies:

- Balance Sheet is out of balance (this should not be physically possible, and indicates corrupt data and/or bad table links)

- Account does not foot (corrupt data but an easy fix. "foot" = "tally up"; it means that the sum of all transactions in the account does not equal the running total stored elsewhere in the database)

- ANY error code that contains the words "Please call [software] technical support". They do not mean tomorrow or five weeks from now, they mean RIGHT FRAKKING NOW! I have yet to see those pop up for any error which is anything short of "Wow. You are so f*king f*ked."

- Any error which references line numbers in the source code, rather than specific data files (the install itself is messed up)

- Anything which references special options which are normally hidden from the end-user (like the Integrity Check in Peachtree). These are hidden for a REASON. If you don't know what you're doing, you can render your entire database unusable in seconds flat. Even if you DO know what yer doing, you need to be careful.

- Final bonus: If your building lost power any time recently while the accounting software was running (on any comp), then yes, that's what caused the problem. You also need to TELL us this up front.

[Calud]

Nope, I went there, too.

Same here.