Before you begin
This story-led series teaches practical concepts in attendance tracking, school management, and business software. Each chapter presents a relatable situation, followed by takeaways and links to explore the tools further.
Important note: Characters, dialogue, and the names of individuals or client businesses in these scenarios—apart from explicitly identified real brands—are fictional or dramatized for educational purposes. This is not a factual account of a real case or an allegation against any person or company. NetCity, Rigi24, Kadrebi and SkolaPlus are real brands and services; their features may evolve.
Chapter Ten: The Message That Never Got a Reply
Sometimes a message is seen, but the task hidden behind it goes unseen.
9:17 a.m. — A Promise Made Too Soon
Irakli Kakhabridze was sitting at his desk in the office of the Two Balconies restaurant.
He picked up his phone.
The restaurant’s Instagram page was open.
A colorful picture filled the screen.
Above it were the words:
“Two Balconies Loyalty Club — Earn points with every purchase starting today!”
Irakli stared at the picture for a few seconds.
Then he exclaimed, “What on earth is this?!”
The restaurant’s marketing manager looked out from the next room.
“What happened?”
Irakli held up his phone.
“Who published this?”
“The loyalty club advertisement we prepared.”
“Didn’t I tell you not to publish it yet?”
The woman looked surprised.
“I thought it had been approved. You said you wanted to start this week.”
Irakli put a hand to his forehead.
“I said we wanted to start, not that we’d already started!”
The marketing manager said, “But several people have already written to ask about the points.”
Irakli sighed.
“We haven’t even decided the club’s rules. We haven’t activated the module!”
He looked at the post again.
The image was beautiful. The colors worked well together, and the promotional text was appealing.
There was just one problem.
It advertised something that had not been launched.
Irakli told the marketing manager, “Stop any further promotion for now. We need to sort out the status of this post and give customers an accurate answer.”
Then he checked the messages on his phone.
A few days earlier, he had written to NetCity:
“Hello. I have a question about activating Rigi24’s Loyalty Club for our restaurant’s two branches. We’d like to know what it offers and how we can set it up.”
There were two blue check marks beneath the message.
But no one had replied.
Irakli dialed Giorgi’s number.
9:58 a.m. — NetCity
Nika entered the office carrying a glass of tea.
Giorgi was on the phone.
“Yes, Mr. Irakli, I understand.”
He listened for a moment.
“You’re right. Please give me a chance to investigate.”
Nika stopped beside Mari’s desk.
“What’s going on?”
Mari motioned for him to wait.
Giorgi continued, “I’ll let you know the result of our follow-up today. But before promising anything about features or activation, I need to check the details.”
The call ended.
Giorgi put down the phone.
“A request has gone unanswered.”
Nika asked, “Whose?”
“Irakli’s. The owner of Two Balconies.”
Nika smiled.
“The restaurant with two branches?”
“Yes.”
“More trouble with the waiters?”
“No. This time it’s the loyalty club.”
Mari asked, “What happened?”
Giorgi explained that Irakli had sent a message about the loyalty club several days earlier and had received no reply.
“Now the restaurant has published an advertisement saying customers can earn points from today, even though they haven’t launched that feature.”
Nika said, “So was it Rigi24’s fault?”
“We don’t know yet,” Giorgi replied. “First we need to see what was requested and who was supposed to follow up.”
Mari opened the customer’s record.
The restaurant’s details were there, along with notes from earlier meetings.
But there was no new request to activate a loyalty club.
“I can’t find a recent request in the follow-up history,” Mari said.
Nika asked, “Then where’s his message?”
Giorgi showed him the phone.
“In the company’s WhatsApp account.”
10:15 a.m. — The Message That Had Been Seen
Luka was taking care of some administrative work when Giorgi called him over.
“Luka, did you open Irakli’s message?”
Luka thought for a moment.
“Which message?”
“The one about Two Balconies’ loyalty club.”
His expression changed.
“Oh ... yes.”
Mari asked, “Why wasn’t it followed up?”
“I saw it on Thursday afternoon,” Luka replied. “Because it was about pricing and activation, I meant to pass it to Giorgi.”
“But you didn’t,” Giorgi said.
“No. I got busy with something else right then and forgot.”
Nika asked, “So the two blue check marks mean somebody read it, but they don’t tell us whether anybody did anything?”
“Exactly,” said Mari.
Luka spoke up.
“It was my mistake. I should have registered the request or assigned it to the right person immediately.”
Giorgi answered, “What matters now is making sure it doesn’t happen again.”
Mari pointed at the screen.
“We use Rigi24 CRM ourselves. If we leave a customer request sitting in a messenger instead of putting it into our follow-up process, what’s the point of having CRM?”
Nika said, “So we’ve fallen into the same trap we tell our customers to avoid!”
Giorgi gave a rueful smile.
“Yes. Exactly.”
10:40 a.m. — Three Modules, Three Different Jobs
Giorgi started a video call with Irakli.
Mari and Nika joined the meeting.
After exchanging greetings, Irakli said, “Look, I’m happy enough with Rigi24 to be asking about more of its features. But I need to know exactly what I’m buying.”
“That’s fair,” Giorgi replied. “First, tell us what you expect from a loyalty club.”
“We have two branches,” said Irakli. “Some guests visit regularly. I’d like to give loyal customers points or special benefits.”
Nika asked, “Something like a gift after every ten visits?”
“Possibly. Or points based on what they spend. We haven’t decided yet.”
Mari said, “Then the first step is to define the loyalty program’s rules. The Loyalty Club is a separate module; it isn’t the same thing as the Restaurant module.”
Irakli asked, “Then what’s the difference between that and CRM?”
Giorgi explained, “CRM helps manage business relationships, customer histories and requests that need following up. The Loyalty Club is for the rewards and benefits a business chooses to offer its customers.”
Nika said, “So what we should have done with your request today belongs in CRM.”
Mari smiled.
“Yes.”
Nika continued, “But the points you want to award your restaurant guests belong to the Loyalty Club.”
“So both could be useful,” said Irakli, “but they don’t do the same job.”
“Correct,” Giorgi answered. “We need to work out which features actually suit your business.”
Irakli thought for a moment.
“One more question. Will everyone who has bought something at either branch automatically become a club member?”
“We shouldn’t assume that,” Mari replied. “We need to review the data we have, the membership method, customers’ consent and how the different parts connect. Information should not be transferred automatically into a club without the necessary setup and authorization.”
Irakli nodded.
“Good. I don’t want customer information used incorrectly just for convenience.”
Nika opened his notebook.
But before he could write anything, Mari said, “And Nika, please don’t write that all the modules connect automatically!”
Nika laughed.
“I was writing exactly the opposite!”
11:20 a.m. — Customers Ahead of the Advertisement
Back at Two Balconies, the marketing manager’s phone kept lighting up.
Customers were asking about the loyalty club advertisement.
One had written, “I bought something yesterday. Where were my points recorded?”
Another asked, “Do we have to pay to join?”
A third message read, “Does this apply to both branches?”
Irakli looked through them.
“Look what’s happened. We haven’t set the rules, but customers believe the program has already started.”
The marketing manager said, “We could delete the advertisement.”
“Deleting it isn’t enough,” Irakli replied. “Some people might have saved a screenshot.”
He thought for a moment.
“Let’s explain clearly that the advertisement went out too early and the club isn’t active yet. And we mustn’t promise points when the conditions haven’t been decided.”
Giorgi, still on the call, said, “That’s a sensible decision. We’ll follow up on the software side, but communication with the restaurant’s customers needs to come from your business.”
“Yes,” Irakli replied. “That’s our responsibility.”
Nika looked at Mari and whispered, “This time neither the customer nor the software made the mistake.”
“It’s too early to conclude that,” Mari replied. “But so far the main problem has been coordination and the way work was handled.”
Irakli had heard them.
“The problem is that I said I wanted to start, my colleague understood that we had started, and your team didn’t answer the request to investigate it.”
There was a moment of silence.
Then Nika said, “So three people understood three different things.”
Irakli laughed.
“Exactly. Now we need to turn those three interpretations into one decision.”
12:10 p.m. — An Old Customer, a New Opportunity
After the call, Giorgi registered Irakli’s request in the follow-up record.
In the description, he wrote:
“Review the need for a Loyalty Club across two restaurant branches, define membership and points rules, check activation requirements, and provide a suitable proposal.”
He then assigned a person to follow it up.
Mari said, “This time the request needs to have a clear status.”
Luka replied, “I’ll handle the administrative arrangements and record the result in the customer file.”
“And I’ll coordinate with the customer about the commercial terms and module selection,” Giorgi said.
Nika asked, “And me?”
Mari answered, “You’ll read the module documentation properly so you don’t confuse the Loyalty Club with CRM next time.”
Nika sighed.
“I feel like every time I learn one thing, two new articles appear for me to read.”
From the technical desk, Morteza said, “That means there’s still plenty to learn.”
Nika turned around.
“Morteza, as the company owner, can’t you order the articles to be shorter?”
Morteza laughed.
“I can order you to read them more carefully.”
Mari and Giorgi laughed too.
Nika said, “Another one of my suggestions rejected!”
1:40 p.m. — A Sound Decision
Irakli sat in the restaurant office.
This time he was not making a rushed decision.
On a sheet of paper he had written three questions:
“Who can join the club?”
“How are points calculated?”
“What benefit does a customer receive?”
The marketing manager asked, “When should we publish the advertisement again?”
“When the rules are clear, the module is ready, and we know how to manage it ourselves.”
“What if it takes a while?”
“That’s all right. I’d rather start a few days late than make a false promise to customers on day one.”
The marketing manager smiled.
“This time I’ll get written approval before publishing!”
Irakli laughed.
“Please do.”
3:50 p.m. — A Timely Call
Giorgi called Irakli again.
“Hello, Mr. Irakli. I wanted to let you know that your request has been registered and someone has been assigned to follow it up.”
“Thank you,” Irakli said. “We’ve also corrected the original advertisement and explained to customers that the program hasn’t been activated yet.”
“Good. Once we’ve reviewed your needs and the activation terms, we’ll send you an appropriate proposal.”
“I have just one request,” Irakli said.
“Of course.”
“If something isn’t ready, tell me from the beginning. I’d rather know the truth than wait for a promise nobody can say when they’ll deliver.”
“You’re absolutely right,” Giorgi replied.
Irakli continued, “I’ve been in business for years. I’ve learned that customers don’t always expect an issue to be solved instantly. But they do expect to know somebody is working on it.”
After the call ended, Giorgi recorded that sentence in the customer relationship notes.
4:20 p.m. — Something Worth Remembering
Nika was sitting beside Mari’s desk.
“Today I learned that having a long-standing customer doesn’t guarantee they’ll stay with us forever.”
“That’s right,” said Mari.
“Even if they were happy with our services before.”
“Yes.”
“And if we just read a request on WhatsApp, it might get forgotten later.”
“That’s why business requests need to enter a clear follow-up process,” Mari replied.
“So Rigi24 isn’t only for our customers. We have to use it properly ourselves.”
Mari smiled.
“Finally!”
Nika said proudly, “I think I deserve some loyalty points today.”
“What for?”
“For still working here despite all these articles you keep making me read!”
Mari laughed.
“That’s not what the Loyalty Club is for.”
“Then I propose a new module: the Patient Employees Club!”
From his desk, Giorgi said, “Just make sure it actually exists before you advertise it!”
Laughter filled the office.
5:10 p.m. — A Call from Human Resources
Mari was closing the day’s last support record when the phone rang.
The number belonged to a company that used the human resources management system.
Mari answered, “NetCity, good afternoon.”
A woman spoke from the other end.
“Hello. I manage HR at a services company. I have a question about the attendance report for one of our night shifts.”
“Go ahead,” Mari said.
“One of our employees came to HR today. He says he worked last night, but his attendance report doesn’t match the shift schedule.”
“Have you checked the clock-in and clock-out records?” Mari asked.
“Yes, the events are there. But what the report shows isn’t what we expected. Before changing anything, we wanted to be sure the shift settings were right.”
“That was the right thing to do,” Mari said. “Please send the relevant technical details and that shift’s settings through the support channel so we can review them.”
“Of course. We haven’t changed any of the employee’s records.”
“Good. First we need to understand the cause of the difference.”
The call ended.
Nika, who was packing his bag, asked, “What happened?”
“An HR department has asked us to investigate a discrepancy in a night-shift report.”
“Did the employee clock in incorrectly?”
“We don’t know,” Mari replied.
“Was the device faulty?”
“We don’t know that either.”
“Then what do we know?”
Mari smiled.
“We know the HR manager has looked into it and has contacted us with a technical question. We need to examine the data.”
“So this time we’re not going to guess,” Nika said.
“You’re finally learning.”
Nika opened his notebook.
On a fresh page he wrote:
“Sometimes the time is recorded correctly, but the report is interpreted incorrectly.”
After a few seconds, he added another title beneath it:
“The Shift That Went Missing from the Report”
Mari asked, “What’s that?”
Nika smiled.
“Probably the title of tomorrow’s adventure.”
Tools and further reading
Explore the real services and related guidance behind this chapter:
Learning note: examples are illustrative, not a substitute for reviewing real records.