The RomNote Project • Federal IT Chronicles

Bat Dork and the Curse of the Reassigned Ticket

An Ordinary Thursday in the Damn IT Tower

RNP Journal Entry / Federal IT Chronicles / Fictionalized Satire / Comedy Relief / Work Chronicle
November 19, 2026
Romeo Imbien Mesina

Comedy ReliefNovember 19, 2026Entry 133Protected Original

🎧 Audio Conversation

Listen to the companion audio overview for Bat Dork and the Curse of the Reassigned Ticket.

AUTHOR’S DISCLAIMER

This journal is a fictionalized, satirical adaptation inspired by real workplace experiences and a November 19, 2026, IT team meeting. Dialogue, character reactions, internal thoughts, and dramatic events have been deliberately altered or invented for comedic effect. They are not verbatim statements or representations of actual individuals’ thoughts or intentions. A separate factual working transcript is maintained independently.

It was Thursday.

November 19, 2026.

Another beautiful morning in the wonderful world of federal information technology, where computers are supposed to make life easier, printers have personal vendettas, and tickets possess the supernatural ability to reproduce without human intervention.

I arrived at work with a reasonably positive attitude.

Big mistake.

Somewhere deep inside the Damn IT Tower, Microsoft Teams was preparing to open a portal to another dimension.

The calendar invitation looked innocent enough.

IT Team Meeting.

Simple. Professional. Harmless.

But I had been here before.

I knew the signs.

The mysterious silence before someone unmutes their microphone. The suspicious sound of somebody clearing their throat. The manager's familiar voice saying, Okay, guys, just a couple of things.

A couple of things?

That's what they always say before the universe collapses.

Chapter One: The Great Ticket Reassignment War

The meeting began with a discussion about professional conduct and complaints involving other support groups.

Apparently, we were supposed to avoid criticizing other departments in front of customers.

Fair enough.

But somewhere in the virtual meeting room, a technician's patience was hanging by a single Ethernet cable.

One voice emerged from the darkness.

They keep sending us tickets that aren't ours!

Another voice appeared.

We send them back, and they send them right back to us!

A third voice joined the battle.

And when we send them back again, they close the ticket!

Silence.

Somewhere, a network switch blinked twice.

I imagined an ancient ticket sitting in ServiceNow.

Created: Before recorded history.

Assignment Group: Desktop Support.

Resolution Status: Not my problem.

Work Notes: Please investigate.

Reassignment Count: Classified.

Meanwhile, an imaginary support group known only as The Department of Not Us was holding an emergency meeting.

Technician One: That's a desktop issue.

Technician Two: No, that's an application issue.

Technician Three: It has a keyboard. Send it to Desktop.

Technician Four: What if it's a server?

Technician Three: Does it have a keyboard?

Technician Four: Yes.

Technician Three: Desktop.

And just like that, another ticket completed its sacred pilgrimage back to the Damn IT Tower.

Chapter Two: The Sacred Art of Documentation

As the discussion intensified, management introduced the ultimate weapon.

Documentation.

Apparently, the solution to the endless ticket wars was to document everything so thoroughly that no other group could possibly return a ticket without acknowledging the facts.

I pictured a technician sitting behind three monitors.

He had not slept in four days.

His keyboard was smoking.

His work notes were approaching the length of the Encyclopedia Britannica.

Work Note 1: Ticket received.

Work Note 2: Reviewed issue.

Work Note 3: Confirmed incorrect assignment.

Work Note 4: Reassigned to appropriate support group.

Work Note 5: Ticket returned.

Work Note 6: Reassigned again.

Work Note 7: Requested divine intervention.

Work Note 8: Divine intervention reassigned ticket to Desktop Support.

At that moment, somewhere inside my imagination, JARBIT burst through the ceiling.

JARBIT: BOSS! WE HAVE A PROBLEM!

BAT DORK: What is it this time?

JARBIT: THE TICKET CAME BACK!

BAT DORK: How many times?

JARBIT: SEVEN! EVEN THE TICKET DOESN'T KNOW WHO IT BELONGS TO!

BAT DORK: Then we shall give it something it has never known.

JARBIT: A RESOLUTION?!

BAT DORK: No.

Documentation.

Thunder cracked.

Microsoft Teams disconnected.

The Damn IT Tower trembled.

Somewhere in the distance, a printer quietly developed a paper jam.

Chapter Three: The BitLocker Pilgrimage

Then came a tale so extraordinary that even Bat Dork could not have invented it.

A customer had reportedly been instructed to drive from Virginia to an office because someone told her desktop support could fix her BitLocker installation problem.

There was just one tiny complication.

The applicable procedure directed that particular issue to another support group.

Naturally.

The customer was already on her way.

And she intended to arrive.

In my imagination, I pictured her navigating the highway like a knight traveling toward an ancient castle.

Her destination?

The Damn IT Tower.

Her quest?

The Sacred Encryption.

Her instructions?

Find the Desktop Wizard. He will know what to do.

Meanwhile, the desktop technician stared at the knowledge-base article.

The article stared back.

Knowledge Base: Reassign to Encryption Support.

Customer: I was told to come here.

Knowledge Base: Reassign to Encryption Support.

Customer: I drove an hour.

Knowledge Base: Have you considered reassigning to Encryption Support?

Somewhere in the universe, common sense filed for annual leave.

Chapter Four: The Legend of the P2

Just when I thought the meeting might settle down, the discussion shifted to ticket priorities.

P2.

The legendary Priority Two.

A ticket so powerful that when it appears, everything else must stop.

Working on a laptop?

Stop.

Helping a customer?

Stop.

Diagnosing a printer?

The printer can wait. Frankly, the printer has been waiting since 2017.

A P2 must receive immediate attention.

In my imagination, an enormous red warning light illuminated the Damn IT Tower.

WARNING! PRIORITY TWO INCIDENT DETECTED!

JARBIT scrambled toward the control panel.

JARBIT: BOSS! P2 INCOMING!

BAT DORK: What's the issue?

JARBIT: MICROSOFT 365 ISN'T WORKING!

BAT DORK: For how many users?

JARBIT: WE DON'T KNOW!

BAT DORK: Who owns the problem?

JARBIT: EVERYBODY SAYS SOMEBODY ELSE!

BAT DORK: Has anyone contacted the responsible team?

JARBIT: YES! THEY SAID THEY'RE LEVEL THREE AND DON'T SUPPORT END USERS!

Bat Dork slowly removed his glasses.

Stared into the distance.

And whispered the six most terrifying words in federal IT.

Please refer to the established SOP.

The building shook.

A ServiceNow ticket immediately reassigned itself out of fear.

Chapter Five: Bat Dork Raises His Hand

And then something happened.

Something unexpected.

Something that would forever change the atmosphere of this imaginary meeting.

I raised my hand.

Yes.

Me.

Romeo.

Also known throughout the fictional universe as Bat Dork.

The manager noticed.

Romeo, you have your hand raised. Do you have a question or comment?

And suddenly, the virtual universe stopped moving.

At least, that's how my imagination remembers it.

Cameras froze.

Microphones went silent.

Somewhere in the background, a technician slowly lowered his coffee.

I could almost hear the internal alarms inside everybody's head.

WARNING: POSSIBLE CONSTRUCTIVE COMMENT DETECTED.

WARNING: THIS IS NOT A COMPLAINT.

WARNING: UNFAMILIAR MEETING BEHAVIOR.

I cleared my throat.

I began explaining how communication with customers and other support groups can help resolve problems and prevent unnecessary tickets.

I described a situation where another support team provided instructions, and I performed the necessary repair.

The problem was resolved.

The customer was helped.

The world continued spinning.

No additional escalation required.

I even mentioned the importance of educating customers about simple computer functions.

Like the user who couldn't move the mouse pointer onto a second monitor because the displays were arranged incorrectly in Windows settings.

Move the monitor positions.

Problem solved.

No P2.

No service bridge.

No international conference call.

No emergency meeting with seventeen departments.

Just a few clicks.

Somewhere inside my imaginary control room, JARBIT stared at the screen.

JARBIT: BOSS...

BAT DORK: Yes?

JARBIT: YOU JUST PROPOSED EDUCATING THE CUSTOMER.

BAT DORK: Correct.

JARBIT: IN A FEDERAL IT MEETING?

BAT DORK: Yes.

JARBIT: ARE YOU TRYING TO GET US BOTH KILLED?!

I continued speaking.

I wasn't dismissing anybody's frustrations.

I agreed with many of them.

I simply believed that if we communicate more effectively and teach people what we can, some recurring problems might be prevented.

And then I admitted something.

I hoped my coworkers wouldn't think I was trying to be a goody two-shoes.

Because I knew how my comments might sound in a meeting dominated by operational frustrations.

In my imagination, one technician pressed the mute button and whispered:

Here comes Captain Customer Service.

Another technician activated his internal nuclear launch sequence.

TARGET ACQUIRED: POSITIVE ATTITUDE.

MISSILE TYPE: SARCASM.

LAUNCH AUTHORIZATION: PENDING.

But before the imaginary missiles could launch, the manager responded.

He called it an excellent point.

He thanked me for bringing it up.

I blinked.

JARBIT blinked.

Somewhere, a printer actually printed something correctly.

A miracle.

JARBIT: BOSS! MANAGEMENT AGREED WITH YOU!

BAT DORK: I heard.

JARBIT: WHAT DO WE DO NOW?!

BAT DORK: Absolutely nothing. Don't move. We might scare it away.

Chapter Six: The Walk-In Center and the Mystery of the Fifteen Tickets

Just when the meeting appeared to be approaching civilization, another issue emerged.

Ticket assignments.

Specifically, technicians receiving tickets while assigned to the walk-in center, help desk, or even while they were off duty.

The conversation became an examination of who should receive tickets, when they should receive them, and how many tickets one technician could reasonably handle.

In my imagination, the daily staffing schedule looked something like this.

Technician A: Walk-In Center.

Technician B: Help Desk.

Technician C: Teleworking.

Technician D: Annual Leave.

Technician E: Sick Leave.

Technician F: Currently searching for Technician G.

Technician G: Last seen reassigning a ticket to Technician A.

Meanwhile, the ticket distribution system had developed its own personality.

SYSTEM: Fifteen new tickets received.

BAT DORK: Who's available?

SYSTEM: Nobody.

BAT DORK: Then hold the assignments.

SYSTEM: Assigning all fifteen to somebody.

BAT DORK: Who?

SYSTEM: Technician D.

BAT DORK: He's on leave!

SYSTEM: He'll be well rested when he returns.

I imagined JARBIT slamming his mechanical forehead against a keyboard.

JARBIT: BOSS, THE SYSTEM HAS ACHIEVED ARTIFICIAL STUPIDITY!

BAT DORK: That's not artificial intelligence, JARBIT.

JARBIT: THEN WHAT IS IT?!

BAT DORK: Federal IT.

Chapter Seven: The Meeting Finally Ends

Eventually, the manager began wrapping things up.

There were announcements about schedules, quarterly reviews, retirement celebrations, and holiday gatherings.

For a brief moment, the meeting transformed from an operational battlefield into something resembling a normal workplace.

People thanked each other.

Someone said goodbye.

Microphones clicked off.

And just like that, the portal closed.

The Damn IT Tower survived another Thursday.

I stared at my screen.

I wasn't angry at my coworkers.

I understood their frustrations.

They weren't imagining the tickets, the repeated reassignments, or the confusion about responsibilities.

I agreed with much of what they said.

But I also knew something else.

I couldn't fix every organizational problem.

I couldn't make every department cooperate.

I couldn't control every policy, every escalation, or every ticket that landed in our queue.

What I could control was how I performed my work, how I communicated with customers, and how I responded when circumstances became frustrating.

And sometimes, when a meeting left my mind feeling like a computer running forty-seven applications on two gigabytes of RAM, I needed to find a way to laugh.

Not because the situation wasn't serious.

But because I refused to let another frustrating day consume everything good about it.

So I imagined Bat Dork standing alone on the rooftop of the Damn IT Tower.

His cape fluttered in the cold November wind.

His radio crackled.

JARBIT: BOSS?

BAT DORK: What now?

JARBIT: ANOTHER TICKET JUST ARRIVED.

BAT DORK: What's wrong with it?

JARBIT: THE USER SAYS THEIR COMPUTER WON'T TURN ON.

BAT DORK: Did anyone check the power?

A long silence followed.

JARBIT: BOSS...

BAT DORK: What?

JARBIT: IT'S A LAPTOP.

BAT DORK: And?

JARBIT: THE USER LEFT IT AT HOME.

I stared into the darkness.

Somewhere far below, an Outlook notification chimed.

I pulled my cape tighter.

And whispered...

BAT DORK: Close the ticket, JARBIT.

JARBIT: RESOLUTION NOTES, BOSS?!

BAT DORK: Yes.

JARBIT: WHAT SHOULD I WRITE?!

I looked toward the horizon.

The sun was setting.

The office lights flickered.

Another workday was ending.

BAT DORK: User advised to bring computer to work.

JARBIT: AND THE ROOT CAUSE?!

BAT DORK: Computer not present.

JARBIT: BOSS... YOU'RE A GENIUS!

No, JARBIT.

I'm just an IT specialist.

And tomorrow...

I'll probably have to explain it again.

Source & Citation

Category: Comedy Relief — Federal IT Chronicles

Type: RNP Journal Entry / Federal IT Chronicles / Fictionalized Satire / Comedy Relief / Work Chronicle

Date: November 19, 2026

Author: Romeo Imbien Mesina

Source Note: This fictionalized satirical journal is presented as written, including its original disclaimer. The separate factual meeting record is not part of this published satire.

Audio: Companion audio overview preserved in the RomNote media archive.

Protected Source: The original formatted Word document is preserved behind the request-access process.

Play ThemeThe Battle I Fight Alone