Rigi24 The Rigi24 learning book · Stories and practice
The Rigi24 learning book · Stories and practice

Chapter Sixteen: The File That Was Finalized Three Times

Learn technology and business through stories

Chapter 16Educational fiction with dramatized characters and clients Rigi24 Kadrebi SkolaPlus Business management

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.

Read the story ↓Tools and further reading ↗

Chapter Sixteen: The File That Was Finalized Three Times

Four floors, a hundred employees, and one sentence everyone had understood differently.

Eight fifty — Fourth floor

ناتیا در حال بررسی نسخه‌های متناقض برنامه سفر
ناتیا در حال بررسی نسخه‌های متناقض برنامه سفر

Magda was looking out of her office window at Pekini Street.

The sky was overcast, and the morning traffic in Tbilisi was just beginning to build.

On her desk sat a cup of coffee, two contracts, and a laptop whose notification chime she had heard three times that morning.

Magda was the director of Blue Sky Travel, a company with nearly a hundred employees that handled group travel, hotel reservations, transport coordination, and corporate travel planning.

The company occupied four floors.

The first floor housed sales and corporate client relations.

The second floor handled hotel reservations and accommodation arrangements.

The third floor handled transport and travel operations.

The fourth floor housed accounting and management.

The building was not so large that employees could not visit the other floors.

But they had so much work that if they had to go up and down for every question, they would probably spend most of the day in the elevator.

The internal phone lines were always busy.

Sometimes three people would call the same person at once.

At other times, someone would fail to pick up, then say a few minutes later:

“I wasn’t at my desk!”

Magda had been used to this state of affairs for years.

Until that morning.

Her extension rang.

Elene, who handled hotel reservations, was on the line.

“Magda, we have a problem with Aftab’s group of forty-eight.”

Magda asked:

“What kind of problem?”

“We don’t know whether to confirm Thursday’s reservation for eight people or forty-eight.”

Magda raised her eyebrows.

“Wasn’t the plan settled?”

Elene said:

“That’s what I wanted to ask.”

Before the call was over, another extension flashed on the display.

Beka, who handled transport.

Magda answered the call.

“Go ahead, Beka.”

“Magda, do we need to send one car on Thursday or two buses?”

Magda stared at the phone.

“How do those two possibilities even fit together?”

Beka said:

“We thought the whole group was leaving on Thursday.”

Magda asked quietly:

“Who said that?”

Beka replied:

“Sales.”

Magda was silent for a few moments.

Then she said:

“Apparently, we all need to talk about the same thing today.”

Nine ten — A sentence that arrived only halfway

On the first floor, Marika was sitting at Salome’s desk.

Salome, who normally handled the Aftab account, had suddenly fallen ill and was due to be on leave for two days.

Marika had to carry on with her work.

Several notes lay on Salome’s desk.

One of them was written in red pen:

“Aftab group — 48 people — Batumi — Thursday / Friday”

Marika picked up the note.

“Thursday or Friday?”

Her colleague replied:

“Friday, I think.”

Marika asked:

“Then why does it say Thursday too?”

“I don’t know. The plan probably changed.”

Marika dialed the hotel reservations extension.

“Elene, do you know what day this group is supposed to check in?”

Elene said:

“According to the first file, Friday.”

“Then what’s Thursday about?”

“Yesterday, Salome said a few people would be arriving earlier.”

“How many?”

Elene paused.

“I understood it was eight, but another file came through for the whole group.”

Marika asked:

“Which file?”

“The one she sent yesterday afternoon.”

Marika looked through the folders on the laptop.

She found three files.

Aftab_Final

Aftab_Final_New

Aftab_Final_ReallyFinal

Marika put her head in her hands.

“Which one is actually the latest version?”

Elene laughed.

“That’s what I’d like to know!”

Nine twenty-five — A contract that would not wait

Magda called all three department leads to a brief meeting.

Elene came up from the second floor.

Beka came from the third.

Marika came from the first.

Tea, who handled accounting, joined them from the room next door.

Magda asked:

“Who has the latest information from the client?”

Marika said:

“Salome.”

“Where is Salome?”

“On leave.”

Magda asked:

“Then who’s responsible for taking over the account?”

Marika said:

“I am.”

“Good. What was the client’s latest change?”

Marika hesitated for a moment.

“I’m not quite sure yet.”

Magda looked at Elene.

“What do you know?”

“The hotel has room for eight people from Thursday. For the rest, from Friday. But if everyone wants to come on Thursday, we need to request more rooms now.”

Beka said,

“I’ve planned for two buses on Thursday.”

Marika asked in surprise,

“For eight people?”

Beka replied,

“For forty-eight people!”

Tea opened a folder.

“I’ve also calculated the cost of the extra night’s accommodation for forty-eight people.”

Magda looked at them.

“So the four of us are sitting here, each talking about a different trip.”

No one laughed.

Magda continued,

“The hotel has given us until one in the afternoon to confirm the new arrangements. Before then, we need to find out what the client actually asked for.”

Nine Forty — The Record That Remained

Marika said,

“We activated Rigi24 Team Chat a while ago. I think Salome posted a message about this project there too.”

Magda asked,

“Then why are we still hunting for files on our phones?”

Marika gave a faint smile.

“Because we haven’t all got into the habit of coordinating our work there yet.”

Magda said,

“Then we’ll start today.”

Blue Sky had already been using Rigi24 CRM to manage its corporate clients.

They had also activated the corporate chat add-on some time earlier.

Several work groups had been created, but some employees were still in the habit of getting things done through internal calls or personal messages.

As an authorized employee, Marika opened the relevant operations group conversation.

Among the messages, they found a note from Salome.

“The client has requested a change to the group’s arrival schedule. I’ll share the final details once they’re confirmed.”

Elene said,

“That’s the message I saw.”

Beka asked,

“Then why didn’t you say it wasn’t confirmed?”

Elene said,

“Because I didn’t see the next message.”

Marika scrolled down.

There was another message.

But it had been addressed to someone else.

“Only eight of the speakers need to be in Batumi on Thursday night. The rest of the group will arrive on Friday morning.”

Magda asked,

“Who wrote this message?”

Marika said,

“Salome.”

“And who did she send it to?”

“The previous travel coordinator.”

Beka said,

“I hadn’t seen this message.”

Elene replied,

“Neither had I.”

Magda said quietly,

“So the problem isn’t simply that the information wasn’t recorded. It was recorded, but it didn’t reach the people responsible.”

Ten O’Clock — One Group for One Project

Magda decided they needed a dedicated group conversation for this account.

Authorized members were selected from the relevant departments.

They named the group:

Aftab — Corporate Travel Coordination

Marika from sales.

Elene from hotel reservations.

Beka from transport.

Tea from accounting.

And Magda from management.

Marika asked,

“Does that mean we discuss everything about this project here from now on?”

Magda said,

“Shared operational information, yes. But not everything belongs in the group. Confidential information must only be shared with authorized people.”

Tea said,

“For example, bank account details or the company’s internal profit calculations.”

Magda replied,

“Exactly.”

Beka asked,

“What if it’s urgent? Do I still have to send a message?”

Magda said,

“No. For something urgent, you can make an internal call. But if the outcome affects the plan, we need to record a summary of the decision as well.”

Elene said,

“So internal calls aren’t being phased out.”

Magda smiled.

“They’re not meant to be. We just don’t want an important company decision to exist only in one person’s memory.”

Marika sent the first message to the group:

“According to the latest information available, only eight speakers will arrive in Batumi on Thursday. The other forty are scheduled to arrive on Friday. This still requires final confirmation from the client.”

Beka replied,

“Received. I won’t change the transport arrangements until we have final confirmation.”

Elene wrote,

“We’ll hold the Thursday rooms for eight people. I’m waiting for confirmation about the rest.”

Tea added,

“For now, I won’t finalize the financial calculations based on any of the previous versions.”

Magda smiled for the first time that morning.

“Good. At least we’re all talking about the same trip now.”

Ten Twenty — One File, Four Floors

هماهنگی نسخه new برنامه سفر در گفت‌وگوی تیمی
هماهنگی نسخه new برنامه سفر در گفت‌وگوی تیمی

Marika prepared the latest travel plan file.

But before sending it, she changed its name.

Aftab_Travel_Plan_Review_V4

Beka laughed.

“Version four again?”

Marika said,

“Yes. But this time I’ve put ‘under review’ in the name. No one should think it’s final.”

She attached the file to the group conversation.

In her message, she wrote:

“The new version is for internal review. Please do not make any new commitments based on it until the client has approved it.”

A few minutes later, Elene replied beneath the same message:

“Hotel accommodation for eight people on Thursday can be arranged.”

Beka replied to the same message:

“For eight people, a suitable vehicle will be enough; we won’t need two buses. We’ll review Friday’s arrangements for the other forty.”

Tea wrote:

“Once the numbers and length of stay are confirmed, please finalize the file so I can complete the financial calculations.”

Marika looked at the screen.

Before that day, gathering information like this would have taken at least four phone calls.

Now the replies were all visible beneath the same file.

More importantly, anyone covering for her the next day would be able to see what each department had said.

Ten forty-five — Message Seen

Beka was waiting for Magda’s response about transport costs.

He wrote in the group:

“@Magda, please let us know your final decision on changing Thursday’s vehicles.”

A few minutes later, the message status showed that it had been seen.

Reassured, Beka moved on to something else.

Elene asked him:

“Has the vehicle change been approved?”

Beka replied:

“Magda has seen the message.”

Elene said:

“I asked whether it had been approved.”

Beka paused.

“No. She hasn’t replied yet.”

Elene smiled.

“Then it hasn’t been approved yet.”

Beka said:

“You’re right.”

He checked the message again.

A few minutes later, Magda replied:

“Do not record any further changes until the client approves them. Once we have approval, we’ll review the final cost.”

Beka said:

“Now we have a clear answer.”

Elene replied:

“Exactly. Seeing a message and making a decision are different things.”

Eleven oh five — Information That Wasn’t for Everyone

ارسال خصوصی گزارش مالی محرمانه به مدیر شرکت
ارسال خصوصی گزارش مالی محرمانه به مدیر شرکت

On the fourth floor, Tea had prepared the internal cost report.

The file included service purchase prices, the company’s profit margin, and the terms of supplier contracts.

She was about to send it to the project group.

But before selecting the file, she paused.

She said to Magda:

“This report includes internal financial information. Wouldn’t it be better if I sent it directly to you?”

Magda replied:

“Yes. The operations group is for coordinating travel arrangements. Not every member needs to see all the company’s financial details.”

Tea opened her private conversation with Magda.

She sent the file there.

Magda reviewed the information.

Then she wrote a summary of the decision that could be shared with the group:

“The proposed transport plan can be considered from a budget perspective. Please make no binding commitments until final approval has been received from the client.”

Marika read the message.

She said to Beka:

“This way, we know the outcome we need for our work without passing around all the internal financial documents.”

Beka said:

“So work groups and private conversations each have their own purpose.”

Marika replied:

“Yes. And each employee should only have access to the conversations and records they’re authorized to access.”

Eleven thirty — The Client Record

Marika opened Aftab Company’s details in CRM.

The client record already existed.

The history of business communications, previous proposals, and the person responsible for the account were all clearly recorded.

Marika said:

“We discussed the plan in chat, but we need to add the final outcome to the client record too.”

Magda asked:

“Why?”

“Because the same company might ask for our services again next month. We shouldn’t have to read every message in the group to find out what the last agreement was.”

Magda nodded.

“That’s right.”

Using the information-linking feature, Marika linked the itinerary file to the client record she was authorized to access.

Then she explained:

“The file and our internal conversation stay in chat. But we need to record a summary of the confirmed information and client follow-ups in CRM.”

Magda said:

“So chat doesn’t replace CRM.”

“No. Chat is for coordinating staff. CRM is for client records and client relations.”

Magda asked:

“And who’s responsible for taking things forward?”

Marika said:

“We’ll specify that in the client follow-up too. If a task has a clear deadline and someone responsible for it, we can also track it through the task board.”

Magda smiled.

“Good. Now we really are using the system properly.”

Twelve o’clock — The Final Call

Marika called Aftab Company’s representative.

“Hello. I’m calling for final confirmation of the travel arrangements.”

The client’s representative replied:

“Go ahead.”

Marika said:

“According to your latest request, eight of the speakers will arrive in Batumi on Thursday night, and the other forty will arrive on Friday morning. Is that correct?”

“Yes, exactly.”

“Should we arrange accommodation from Thursday for the first eight?”

“Yes.”

“And the main group’s schedule hasn’t changed?”

“No. Still Friday.”

Marika said:

“Very good. Please send us your final confirmation in writing as well, so we can finalize the arrangements.”

The client’s representative agreed.

A few minutes later, the confirmation arrived.

Marika saved the file and recorded the confirmation in the client record.

Then she wrote in the group:

“The final arrangements have been approved. Eight people on Thursday, forty on Friday. The client’s written confirmation has been received and saved in the relevant record.”

Elene replied:

“I’ll finalize the hotel booking on that basis.”

Beka wrote:

“I’ll revise the transport schedule and report back.”

Tea said:

“I’ll check the final calculations against the approved itinerary.”

Magda glanced at the clock.

It was twelve fifteen.

There were still forty-five minutes left before the hotel’s deadline.

Twelve Twenty-Five — Who Is Responsible?

Magda opened the group again.

Replies from every department were visible.

But one question remained.

“Once the hotel booking is confirmed, who is supposed to send the final itinerary to the client?”

Marika said:

“I am.”

Magda asked:

“Where is that recorded?”

Marika hesitated.

“I haven’t recorded it anywhere yet.”

Magda smiled.

“Then do it now.”

Marika recorded herself as responsible in the client follow-up section.

A task with a specific deadline was also created on the task board to review and send the final itinerary, since the company had activated the relevant add-on as well.

Magda said:

“Now, if you’re on leave tomorrow, whoever takes over can check the status of the task.”

Marika replied:

“Yes. And they won’t have to guess what needs doing just from the chat messages.”

Magda said:

“Exactly.”

Then she added with a laugh:

“Though I hope you won’t be on leave tomorrow too. This one case is enough for this week!”

One Ten — Salome’s Leave

Salome called from home.

Her voice was a little hoarse.

“Marika, I’m sorry I left you with this case half-finished.”

Marika said:

“Don’t worry. We’ve finalized the itinerary.”

Salome asked:

“Eight people on Thursday, the rest on Friday?”

“Yes.”

Salome breathed a sigh of relief.

“Good. That’s what I said yesterday, but I wasn’t sure everyone had heard.”

Marika said:

“As it happens, not everyone had.”

Salome sighed.

“So you’ve had quite a time of it.”

Marika replied:

“A bit. But now the information is clear in the group, we have an approved file, and the outcome is recorded in CRM.”

Salome said:

“That’s a relief.”

Marika continued:

“When you’re back, you can review the relevant history using your own access permissions and see what decisions were made.”

Salome laughed.

“So I won’t have to ask everyone what happened, all over again?”

“No.”

“That alone is the best news I’ve had today.”

Two Forty — Why Wasn’t the Phone Enough?

Magda held a brief meeting with the department heads.

She said:

“I don’t want you to stop making internal calls from tomorrow and only talk in chat.”

Beka laughed.

“That’s a relief!”

Magda continued:

“The internal phone system is great for urgent matters. But when we discuss a contract, a file, or an important change, there needs to be a traceable record of the outcome.”

Elene said:

“For example, if we’d coordinated everything only by phone today, someone might have made the same mistake again tomorrow.”

Marika said:

“But now the latest file, the client’s approval, and each department’s outcome are all clear.”

Tea added:

“And confidential information has only been shared with authorized people.”

Magda said:

“Exactly.”

Then she asked:

“If a new employee joins the company, should they be able to see all the company’s information from day one?”

Everyone said:

“No.”

Magda continued:

“Then access permissions, group memberships, and records need to be managed properly. Having a company chat system doesn’t mean everyone has unrestricted access to everything.”

She looked at the screen.

“We have nearly a hundred employees. If a piece of information exists only on one person’s personal phone, the company will always depend on that one person’s memory.”

Three Thirty — Four Floors, One Answer

On the second floor, Elene recorded the latest status of the hotel booking.

She wrote in the group:

“The booking has been made according to the approved itinerary. The outcome and the relevant file have been made available to authorized staff.”

On the third floor, Beka finalized the vehicle schedule.

“Transport arrangements for Thursday and Friday have been coordinated.”

On the fourth floor, Tea reviewed the final costs.

“The financial calculations have been checked against the final itinerary.”

On the first floor, Marika read the messages.

Then she updated the client record with the outcome.

She no longer had to call the other three floors to find out where things stood.

But more important than the convenience was something they now had:

A clear history of what information had been received, who had discussed it, and which decision was final.

Marika sent the final file to the client.

A few minutes later, a reply arrived:

“Approved. Thank you for coordinating everything so carefully.”

Marika smiled.

She saved the message in the client record.

Then she wrote in the group:

“The final itinerary has been sent to the client, and receipt has been confirmed.”

Beka replied:

“Great.”

Elene sent a check mark.

Tea wrote:

“The financial file is ready for the next stage of follow-up too.”

From the fourth floor, Magda looked at the screen.

For the first time that day, she felt she truly knew what had happened on the other three floors.

Four twenty — The NetCity Office

Nika was reading the Team Chat article.

Mari asked from behind her desk:

“What did you learn today?”

Nika replied:

“That workplace chat isn’t just for employees to say hello and ask how everyone is.”

Mari smiled.

“Go on.”

“It’s really important for companies with several departments. Especially when information and files need to pass between different people.”

Giorgi said:

“And when an employee is on leave?”

Nika replied:

“If the information has been recorded in the right workflow, other authorized people can carry on with the work.”

Mari asked:

“How is it different from an internal phone line?”

Nika said:

“The phone is for immediate communication. Workplace chat helps keep a record of work conversations and files.”

Giorgi asked:

“How is it different from CRM?”

Nika laughed.

“That one I know now! CRM is for client records. Team Chat is for internal communication between employees.”

Morteza said from behind the technical desk:

“And don’t forget that each business’s permissions and information privacy must be respected too.”

Nika said:

“Yes. One company’s chat mustn’t be visible to another company. Even within the same company, each person only has access to the conversations and information they’re authorized to access.”

Mari said:

“Good.”

Nika opened his notebook.

He wrote:

“Fast communication matters, but communication with a record can also be followed up.”

Then he added another line:

“CRM is the memory of client relationships. Team Chat is the memory of work conversations between employees. The task desk defines responsibility for getting the work done.”

Giorgi read what he had written.

“Good. Now you understand the difference.”

Nika smiled.

“Yes. I just hope we don’t have another new module in the next chapter!”

Mari laughed.

“Why?”

“Because there’s no room left in my notebook.”

Without looking up from his monitor, Morteza said:

“Then we’ll have to design a capacity management system for your notebook too.”

Everyone laughed.

Five ten — The Call No One Answered

Magda closed her laptop.

After a busy day, coordination between the company’s four floors had finally paid off.

The working groups were clearly defined, the files were in the relevant conversations, and employees no longer had to call several people to find the latest decision.

But just as she was about to leave the office, Marika came in.

“Ms. Magda, we have another problem.”

Magda laughed.

“Is today ever going to end?”

Marika showed her phone.

“A client from Germany called to book a tour. They called the company’s WhatsApp number three times, but no one answered.”

“Who had the phone?”

“I think Salome had it.”

“But Salome’s on leave!”

“Yes.”

Magda was silent for a few moments.

Marika continued:

“The client says they tried another number too, but no one answered.”

Magda looked at the internal phone on her desk.

Then at her laptop.

“We have nearly a hundred employees, four floors of offices, several phone numbers... but a client abroad can’t speak to us?”

Marika said nothing.

Magda continued quietly:

“Today we solved the problem of communication between employees. Apparently, tomorrow we’ll have to see how clients can reach them.”

Practical articles related to this story

RIGI24 · ARTICLE Team Chat RIGI24 · ARTICLE Workspace

Tools and further reading

Explore the real services and related guidance behind this chapter:

EXTERNAL · Kadrebi.ge ↗Kadrebi: attendance, shifts and reportsExplore employee management and attendance records. EXTERNAL · SkolaPlus.ge ↗SkolaPlus: attendance and school–parent communicationDiscover the second call’s school-related theme. RIGI24 · INTERNALRigi24 business toolsExplore more solutions and educational stories. RIGI24 · INTERNALRigi24 articles and guidesPractical articles for additional reading. RIGI24 · INTERNALBrowse all storiesLearn technology and business through stories EXTERNAL · NetCity.ge ↗About NetCityMeet the company behind the services.

Learning note: examples are illustrative, not a substitute for reviewing real records.