Rigi24 Communications — SMS, Calls & Business Communication

Team Chat for Employees: Private and Group Messaging | Rigi24

A practical guide to team messaging, private groups, secure file sharing, mentions, read receipts, and Telegram fallback in Rigi24.

Team Chat for Employees: Private and Group Messaging | Rigi24
Rigi24 — Book. Manage. Grow.

This in-depth, practical guide explains the capabilities, operating rules, implementation steps, and limits of Rigi24. Product behaviour should be verified against the business’s actual subscription and deployment.

Why a company needs a dedicated team chat

Important workplace decisions often happen in scattered personal messages, phone calls, and hallway conversations. A customer may be promised a delivery date while the person fulfilling the order knows nothing about the promise. A dedicated team chat creates a recognizable workplace channel for clarifications, quick decisions, and handoffs. It does not replace professional judgment or the official customer record; rather, it reduces information loss between them. Before choosing a chat tool, write down the communication failures your team experiences most often. That gives you a measurable reason for adopting it and a practical way to judge whether it helps.

When to use a private conversation or a group

A one-to-one conversation is suitable for sensitive operational coordination, brief questions, and feedback that affects only two colleagues. A group is useful when several people share responsibility for a process, such as dispatch, sales, or front-desk coverage. Creating a new group for every small issue fragments attention and makes past decisions difficult to locate. Start with stable groups around actual responsibilities, then use direct messages when the audience is small. Consider which information needs to remain visible after a colleague changes shifts. Do not assume that every discussion belongs in a group merely because it concerns work.

Naming groups and identifying ownership

Names such as “General 2” or “Urgent” tell new employees very little. A practical group name describes the function, team, or location, for example “Sales — Tbilisi” or “Warehouse — Dispatch.” Decide who is responsible for adding participants and reviewing membership. Introduce a short description of which discussions belong there and which do not. A clearly named room improves discoverability, but ownership is what keeps it useful. If two groups serve the same purpose, consolidate their role instead of encouraging duplicated messages. A periodic membership review also reduces unnecessary access to operational information.

Replying without losing the original context

Fast discussions can contain several topics at once. A response such as “yes, do that” becomes ambiguous when other messages appear between the question and the answer. Reply-to-message support lets the recipient understand which earlier statement the answer addresses. Use it for decisions, corrections, or technical details that would otherwise be confusing. When a decision changes, explain the new decision instead of simply sending a new instruction without reference. For important customer commitments, summarize the final agreement in the appropriate business record or task. A chat reply is valuable context, but it should not become the only record of a binding commitment.

Mentions and targeted attention

A mention should signal that a specific colleague needs to look at a message, not merely that the sender wants more visibility. Mention only people who can take the next step, answer a necessary question, or make an approval decision. Excessive mentions cause attention fatigue; users then ignore the signal when it matters. Rigi24’s chat service checks that mentioned users are participants in the conversation. Mentions also have a shorter configured Telegram fallback threshold than ordinary unread messages. That threshold is a scheduling condition rather than a guaranteed delivery time. Establish a shared expectation about which situations deserve a mention and which can await routine review.

Sharing files in the same working context

An attachment is more useful when colleagues can see why it was shared. Add a brief description, customer reference when appropriate, and a clear request such as “please review the revised specification.” Team Chat supports images, PDFs, plain text, CSV, and common office formats, subject to server validation. A message can contain several files, with a configured size limit for each attachment. Files are kept in private storage and delivered through a permission-checked endpoint rather than relying on a public file URL. Even so, staff must avoid uploading secrets or unrelated personal information and should follow the organization’s retention rules.

Delivered and seen are different states

A message can be created successfully without the recipient having noticed it. Delivery tracking concerns whether the receiving side has received or synchronized the message; a seen marker records that the reader has viewed it. Neither state guarantees understanding, agreement, or action. For routine information, a seen indicator may be enough. For an important process, require an explicit acknowledgment or a separate task with an owner. The system’s service records message receipts for participants, along with delivery and read timestamps. Managers should not use these indicators as simplistic measures of employee productivity, because context and workload matter.

Typing indicators and respectful response expectations

A typing indicator can make a live exchange feel more responsive, but it should not create an obligation for immediate replies. Colleagues may be serving customers, operating equipment, or handling other tasks. Establish response expectations by urgency and working hours rather than by whether someone appears online. Do not rely on typing status as proof that an answer is coming. Short messages work well for clarifications; complex decisions deserve a structured explanation. Where a topic becomes lengthy, assign someone to summarize next steps and move the actionable item into the workspace. This prevents a conversation from turning into an unstructured to-do list.

How Telegram fallback notifications work

Rigi24 can use Telegram as a fallback notification channel for unread chat messages when the user has linked an eligible Telegram identity and the bot is configured. The current settings use approximately thirty seconds for ordinary messages and fifteen seconds for mentions before a receipt becomes eligible for fallback. A scheduled worker checks for due receipts; because the worker runs periodically, actual notification delivery can be later than the threshold. Messages already marked seen should be skipped, and repeated runs should not produce duplicate notifications for successfully processed receipts. Telegram is the alerting surface; the message and its authoritative status remain in Rigi24.

Why a Telegram notification is not another chat room

Copying conversations into multiple messaging systems creates conflicting histories. The fallback design instead offers a short alert and a way back to the Rigi24 experience. Users should return to the business chat to read context and respond rather than assuming that replying to an unrelated Telegram thread updates the workplace record. The fallback also depends on a valid linked Telegram account. A colleague without that linkage can still use the core chat, but will not receive the same Telegram alert. When designing support instructions, distinguish the primary product from optional notification delivery and avoid promising an exact second-by-second response.

Business separation and conversation permissions

In a multi-business platform, a participant from one company must not inherit access to another company’s rooms or files. Rigi24’s conversation service checks both business membership and participation in the specific conversation. File downloads additionally validate the attachment’s business and conversation identifiers. These controls need to hold at the HTTP boundary, not just in navigation menus, because URLs can be guessed or copied. When an employee leaves, revoke business access promptly and verify that earlier links no longer open. Group membership should be treated as an authorization decision rather than a visual preference. Periodic permission testing remains important after software changes.

Sales handoff: from inquiry to a timely answer

Imagine a sales colleague receiving a customer inquiry about availability and delivery. They ask the warehouse team a short question in the operational group, attach the product list, and identify who is responsible for the answer. The warehouse replies to the specific request and records any constraints. Sales then communicates the confirmed promise to the customer and updates the customer record or order. Without this last step, the conversation may be correct but the system of record remains wrong. Team Chat helps the handoff happen quickly; CRM or the relevant operational module keeps the long-term customer context.

Service escalation and urgent exceptions

A receptionist notices that an appointment cannot proceed because an essential resource is unavailable. A useful escalation message states the affected appointment, what happened, when a decision is needed, and who can decide. Mentioning the responsible colleague is reasonable when the issue is time-sensitive, but tagging everyone is not. Once the immediate response is agreed, record the final decision in the booking or customer workflow. Define what to do when a person is unavailable, including a fallback colleague and an escalation deadline. A chat room alone is not a reliable escalation policy unless the team has agreed who monitors it.

File naming, document versions, and accountability

A document named “final-new-3.xlsx” is rarely final for long. Prefer a descriptive name including project, document purpose, and revision date when the business process requires version control. If a newer version supersedes an older attachment, say so clearly and identify what changed. Keep legal and financial originals in their designated records rather than relying on chat search. Team members should know who can approve a file and who merely reviews it. A concise summary beside the attachment helps recipients understand the decision without opening every earlier document. This habit remains useful regardless of the software used.

The difference between a message and an assigned task

A colleague writing “please call this customer tomorrow” is not the same as assigning a tracked task. A chat message can be missed, buried, or interpreted as a suggestion. A task should have a clear title, responsible user, expected timing, and an explicit completion state. Rigi24 Workspace provides a separate location for those actions, including reminders and recurring items. Use chat for discussion, clarification, and rapid coordination; use Workspace when an activity must be completed and followed up. The two modules complement each other, but they should not be represented as a single unified automatic workflow unless that specific integration has been tested.

Practical rules that keep team conversations useful

Introduce a few lightweight rules before adopting the system: name the subject of new requests, mention only relevant colleagues, summarize final decisions, and attach files with context. Define which requests deserve a direct message and which belong in a shared team group. Agree on expected response times for routine and urgent matters and make those expectations compatible with actual working hours. Avoid posting passwords, payment credentials, or unnecessary sensitive personal data. Encourage staff to use a task when a message creates a deadline. Review the rules after the first month and remove any rule that creates more work than clarity.

What to verify before the first rollout

Create a pilot group with an owner and two staff members. Verify that all intended users can sign in, create the appropriate conversation, send and receive messages, and read attachments on their devices. Check that a nonparticipant cannot view a private conversation or its files. Test read indicators, reply references, and mention validation. If Telegram fallback is required, link a test identity and verify the real delivery behavior separately from simulation. Also check subscription access, CRM or Booking prerequisites, and billing entitlements. Complete this checklist before inviting an entire staff, so early problems do not undermine confidence in the rollout.

Mobile use and unreliable connectivity

Teams often work across phones, tablets, and desktop computers. A useful chat experience should remain understandable on a small screen, with readable file names and clear conversation selection. Network interruptions can delay synchronization; staff should distinguish an unsent draft from a confirmed stored message. Rigi24’s interface uses periodic polling for updates, so instant delivery should not be promised under every network condition. When testing, move between Wi-Fi and mobile data, return to the screen after a pause, and check whether unread counts reconcile. For urgent safety-critical work, keep an independent escalation channel rather than relying only on web chat.

Onboarding and offboarding colleagues

Adding an employee is not merely providing a login. Explain which business they belong to, which groups they should join, and what information is confidential. Show them how to reply, mention colleagues, share approved documents, and find the relevant workspace tasks. When their role changes, review conversation membership accordingly. When employment ends, remove or disable their business membership and verify that access to past messages and attachments is revoked. Do not leave an ex-employee in a group merely because a conversation was created long ago. A short onboarding checklist saves time and avoids inconsistent practices across departments.

Separate personal conversations from business records

Employees may naturally use familiar consumer messaging apps, but mixing personal accounts and company responsibilities creates ownership and privacy problems. Customers, documents, and project discussions should stay in the approved workplace environment wherever feasible. Communicate boundaries respectfully and transparently; the goal is reliable collaboration, not unnecessary monitoring. If a conversation includes a confidential customer detail, ensure that sharing is appropriate for each participant. Staff should understand how to report an accidental disclosure. Even in a private company chat, access must follow business need and applicable local data protection obligations.

Measuring whether team chat is helping

Do not judge adoption only by counting messages. A high message count may mean confusion rather than better productivity. Instead ask whether customer handoffs take less time, whether follow-up questions are repeated less often, and whether important decisions can be located later. Track a small number of service measures that matter to the business and collect qualitative feedback from employees. Review which groups are actively useful and which generate noise. If staff continue forwarding screenshots between platforms, investigate why. Successful adoption means clearer communication and fewer missed responsibilities, not simply more time spent inside the chat interface.

Where CRM and chat should meet

Chat is appropriate for colleague-to-colleague coordination; CRM is appropriate for durable information about a customer relationship. If a conversation changes the promised date, contact details, or next follow-up, update the corresponding customer record. Do not treat a chat attachment as automatically becoming a CRM document unless a supported linking feature has actually been used. Rigi24 supports attachment-related CRM references under defined conditions; verify the exact permitted targets and roles during deployment. The important operational principle is that employees know which record is authoritative. A team can communicate rapidly while maintaining a consistent customer history.

Plan and subscription prerequisites

Team Chat is a paid Rigi24 add-on and is intended for businesses with an active qualifying CRM or Booking module. The pricing discussed for this release is 99 GEL per month for Team Chat, 49 GEL for Workspace, or 129 GEL for the combined package, subject to the current commercial terms and invoice configuration. Businesses should verify actual entitlements in their panel rather than relying only on article text. Features may be restricted if subscription or billing requirements are not satisfied. A pilot should include a permissions and entitlement check to prevent a confusing situation in which a staff member sees a link but cannot open the module.

Common implementation mistakes

A frequent mistake is creating too many groups before observing the team’s real workflow. Another is treating every notification as urgent. Teams also lose value when they attach documents without context, fail to remove departed employees, or use chat as the only place for deadline-driven work. Avoid advertising delivery times as guaranteed when synchronization and scheduled notifications depend on network and worker activity. Finally, do not skip cross-user access tests. A chat system must be trustworthy in both routine collaboration and edge cases such as copied links, stale memberships, and attempts to download another conversation’s files.

A seven-step adoption plan

Start by identifying communication failures that cost the team time. Second, choose a small pilot group and designate an owner. Third, map members and permissions to real responsibilities. Fourth, establish a clear naming convention and short rules for mentions, attachments, and escalation. Fifth, test private messages, groups, file access, read states, and optional Telegram alerts. Sixth, move action items to Workspace or the relevant customer record. Seventh, review employee feedback and two or three concrete performance indicators after several weeks. Expand only after the pilot demonstrates value. This staged approach is usually more reliable than enrolling everyone on day one.

How to decide if the module is right for you

Team Chat is useful when colleagues frequently need to coordinate around orders, appointments, documents, and customer questions. It is less helpful when a business has no meaningful internal collaboration requirement or needs specialized emergency communications rather than a standard web chat. Evaluate operational fit, staff readiness, data access controls, and ongoing cost together. The strongest results come from simple group structures and clear accountability. For activities with deadlines or recurring obligations, use the separate Workspace module rather than trying to solve everything with a chat thread. Confirm the current feature set and subscription terms before purchasing.

Related reading and Rigi24 modules

Additional visual of a digital business management workspace
Rigi24 mobile-first booking and customer management experience

Frequently asked questions

What is the difference between a direct conversation and a group?

A direct chat is a two-person exchange; a group contains several authorized participants working on a shared process.

Can colleagues reply to an earlier message?

Yes. Replies can reference an existing message within the same conversation so that its context remains clear.

Who is allowed to download an attachment?

The server checks company access, active conversation membership, and the attachment’s conversation and business before delivering the file.

How many files may be attached to one message?

The current HTTP validation permits up to five attachments; each file is also checked for type and size.

Is Telegram the primary chat channel?

No. Telegram serves as an optional fallback alert for unread messages; the authoritative conversation stays in Rigi24.

Are notifications sent exactly fifteen or thirty seconds later?

Not necessarily. These are eligibility thresholds, and the periodic worker may process and deliver the alert later.

What do delivered and seen indicators prove?

They indicate recorded delivery or viewing, not agreement, comprehension, or completion of a business task.

What happens when an employee leaves?

The company should revoke their business membership and review conversations. Access controls must be verified against old links.

Does Team Chat require another active module?

The current add-on offering requires a qualifying active CRM or Booking subscription and applicable billing entitlement.