Two weeks after my visit in disguise, a former employee called me.
Her name was Teresa Moreno.
She had worked the morning shift for nearly six years before resigning in February.
I remembered receiving a polite resignation email.
It said she wanted to spend more time with her family.
“That's not the real reason I left,” she told me.
She had tried to report Kyle several times.
One complaint concerned a server being denied tips after a customer complained.
Another described the way Kyle spoke to older diners.
The last involved an unfamiliar reader at the counter.
Teresa had photographed it while cleaning.
She did not touch it.
Then she sent the photo and a note to the employee hotline.
Kyle answered two hours later.
He accused her of spying on coworkers.
He told her not to return for her next shift.
She later received her wages but no explanation.
She left rather than challenge him.
“Why are you telling me now?” I asked.
“Because I saw your notice about the security review.”
She hesitated.
“And because my mother still eats there. I don't want her card taken.”
I asked whether she still had the photograph and messages.
She did.
Dana arranged to receive copies with original timestamps.
The image showed the black reader clearly.
It was sitting beside a receipt roll in an open drawer.
A small printed label displayed part of a serial number.
That gave the processor something concrete to compare with its records.
Teresa's email also contradicted Kyle's claim that nobody had raised concerns before my visit.
I sat with Dana as she reviewed the messages.
“You should have received this,” she said.
“I know.”
“Who had access to the hotline?”
“Kyle.”
“And who reviewed it?”
“I assumed personnel did.”
“Did you ever ask for a report?”
“No.”
There was no comfortable way around that answer.
I had created a system that looked responsible on paper.
In practice, it sent complaints to the very person employees feared.
I called Teresa and apologized.
She listened without interrupting.
When I finished, she said something I deserved to hear.
“Frank, you were always nice to us when you came in.”
“I tried to be.”
“But nice isn't the same as available.”
I wrote that down.
Then I asked whether she would consider meeting the outside human-resources consultant to help us improve our reporting process.
She agreed, but she did not want her old job back.
“I've found somewhere I feel safe,” she said.
“I'm glad.”
The next day, the payment processor confirmed that the partial serial number matched equipment associated with the outside merchant account under review.
Brooks asked Teresa to provide a formal witness statement.
The police were also preparing to seek further records through legal process.
This was progress, but not a conclusion.
Meanwhile, Omar's audit continued.
He had traced several irregular refunds to a manager login used after normal closing hours.
The records showed the login came from a device inside Rosie's office network.
That was stronger than a username alone.
But he still had to determine who had been physically present.
The security footage showed Kyle entering the office on one of those evenings.
It did not show the actual refund entry.
Omar also found legitimate correction entries that Kyle had made during busy weekends.
We couldn't simply label every transaction under his name as fraudulent.
I admired Omar's patience even when it frustrated me.
There was one afternoon when I almost abandoned the cautious approach.
A customer posted a video claiming Rosie's had stolen her retirement savings.
Her voice shook as she described a fraudulent charge.
The video spread quickly.
Strangers left angry comments beneath it.
Some called for the restaurant to close.
Others accused the woman of inventing the story.
I wanted to respond to every comment.
I wanted to explain that our processor had not linked every suspicious charge to Rosie's.
Then I wanted to apologize for a situation I could not fully verify.
Dana stopped me.
“Take the complaint seriously without making claims you can't support,” she said.
We contacted the woman privately through our dedicated assistance process.
She provided the date of her restaurant visit and the bank dispute reference she was comfortable sharing.
The dates did not match the period when the suspect reader was documented at Rosie's.
That didn't prove nothing had happened.
It meant her claim needed separate examination.
We forwarded the details to the processor through approved channels.
I posted a brief public statement describing our security review, verified controls, and customer assistance line.
I did not identify the woman.
I did not attack her credibility.
A week later, she sent a message thanking us for listening.
Her bank had found that at least one charge involved a merchant unrelated to Rosie's.
Other disputed activity was still under review.
She didn't take down her video immediately.
I didn't ask her to.
The experience reminded me how vulnerable people felt when money vanished from an account.
An owner with good lawyers could defend his reputation.
A customer frightened about her bills might have only her voice and a phone.
I did not have to agree with every allegation to treat the person making it respectfully.
At the next staff meeting, we reviewed the incident without using her name.
The lesson was practical.
Report concerns accurately.
Use secure channels.
Don't promise outcomes an outside bank controls.
And never punish someone simply because the first version of a complaint turns out to be incomplete.
He built two separate lists.
One contained confirmed accounting errors and unsupported refunds.
The other contained suspicious but unresolved events.
He insisted that we keep them distinct.
At home, I opened the old restaurant ledgers my mother had kept.
They were written in blue ink on paper.
Every page listed the cost of eggs, coffee, bread, and repairs.
At the bottom of some pages, Rosie had written notes.
Mrs. Green's boy started college.
Luis needs Wednesday off for his mother's appointment.
Give Mr. Harris his meal to go if it rains.
There was no secret business wisdom in those notes.
Only attention.
My mother remembered the people behind the numbers.
I had let myself believe financial reports could replace that attention.
On Friday evening, I worked the floor for the dinner shift.
I refilled water glasses and delivered bread baskets.
A teenager asked whether the chicken soup contained dairy.
I went to the kitchen and checked.
A father needed a high chair.
I carried one over myself.
An older couple returned a plate because the vegetables were cold.
We warmed it and apologized.
None of those moments belonged in the investigation file.
But together they reminded me what the place was supposed to be.
At closing, Amber brought me a notebook.
She had written down suggestions from staff.
Better shift communication.
A separate complaint line.
Written procedures for discounts.
Manager approval for refunds above a reasonable threshold.
Training that included how to serve someone who couldn't afford a full meal.
I thanked her for collecting the ideas.
“Don't let this turn into a speech and a poster,” she said.
I smiled sadly.
“That's a fair warning.”
Then my phone rang.
It was Detective Brooks.
She said they had located the business address listed on the outside merchant account.
The office was a small rented suite above a tax-preparation business.
The account records named an organizer.
She could not tell me everything yet.
But she asked one question.
“Frank, did Kyle ever tell you he was planning to open his own restaurant?”
I looked at my mother's photograph.
“No,” I said.
“He never did.”
Click here to continue reading: PART 9: Kyle’s Plan for Another Restaurant Revealed Why Rosie’s Customers Had Been Treated as Targets
The Day I Entered My Mother’s Restaurant With Four Dollars and No One Recognized Me
Part 8 of 16
