Internal Chat

One-to-one and group team messaging in the same Conversations screen as your customer channels, with a secure PIN lock.

MyVoipCRM Internal Chat lets the staff of one company message each other in real time. Sales, support and operations teams communicate internally, independent of WhatsApp; every conversation is managed in the Internal Chat tab of the Conversations screen, and can also appear in the unified inbox alongside the customer channels (WhatsApp, Web Chat, email and others).

What it does

  • One-to-one chat: private messaging between company staff
  • Group chat: project, department or team rooms; adding/removing members, leaving a group
  • Instant delivery: new messages, read receipts and a “typing” indicator over SignalR
  • Online users: a live list of connected staff
  • Media sharing: text, emoji, images, video, documents and voice messages
  • Reply and forward: reply to a message; forward it to another conversation
  • Message search: search the conversation list, and search message content across all internal chats
  • Translation: message and compose-box translation with DeepL (multiple languages)
  • AI conversation summary: a short AI-written summary of long conversations
  • Organisation: pinning, favourites, archive, mute, mark as unread
  • PIN lock: lock sensitive conversations behind a PIN
  • Conversation detail: media, document and link history; the group member list
  • Notification sound: toggle the audible alert for new messages

Menu and screens

  • Internal Chat tab — Conversations → All Conversations → Internal Chat (/mesajlasma?tab=internalchat)
  • Unified inbox (all channels) — Conversations → All Conversations → All (/mesajlasma)
  • Embedded conversations (iframe) — embedded use such as agent tasks/modals (/mesajlasma/embed)

Internal Chat has no separate “integration” or “settings” page. When the module is active, the Internal Chat tab appears in the Conversations screen automatically.

Conversation list filters

  • All: conversations that are not archived
  • Unread: conversations with unread messages
  • Pinned: conversations pinned to the top
  • Locked: conversations locked with a PIN
  • Favourites: starred conversations
  • Groups: group conversations only
  • Archive: archived conversations

Starting a conversation

  • One-to-one: pick a person from the company staff list to open a private chat
  • Group: create a team room with a group name and participants
  • One-to-one and group creation can be restricted separately by permission

The chat window

Messaging

Send text, emoji, images, video, documents and voice recordings. Reply to a message or forward it to another conversation. Message deletion follows permissions.

Side panel

The conversation’s media, document and link archive; in-conversation message search; the group member list and its management.

Translation and AI

Message translation with DeepL, and composing in a target language before sending. The AI conversation summary makes long threads quick to grasp.

Group management

Add or remove staff, or leave the group. The group admin is shown in the participant list.

PIN lock

Sensitive internal conversations can be locked with a PIN. A locked conversation shows a lock icon in the list and opens only after the PIN is entered. The PIN protects access to that conversation in your account only — other participants continue normally in their own view.

Getting started

1. Module check

  • The Internal Chat module must be active for your company (module management / licence).
  • Your staff account needs permission for the conversations list.

2. Open the Conversations screen

  • Go to Conversations → All Conversations (/mesajlasma).
  • Click the Internal Chat tab.
  • The hub state must show “connected” (a green wifi icon); use the reconnect button if the connection drops.

3. Start your first conversation

  • From the New conversation (+) menu at the top right, pick a person or create a new group.
  • Write a message; attach files, emoji or a voice recording.
  • Pin, favourite or PIN-lock the important conversations.

Internal Chat vs. Web Chat vs. WhatsApp. Internal Chat is strictly between company staff; customers never see it. Web Chat is for talking to visitors on your website. WhatsApp / Meta channels carry external customer messages. All three live in the same Conversations screen, in separate tabs or the unified inbox.

Who it is for

  • Fast internal coordination for sales and support teams
  • Companies that want secure team messaging inside the CRM instead of WhatsApp groups
  • Teams running operations through project-based group rooms
  • SMEs that want to work in one Conversations screen together with the customer channels
  • Managers who want sensitive internal threads behind an extra PIN lock

Frequently asked questions

The Internal Chat tab is missing

The Internal Chat module must be enabled for your company and your account needs the conversations-list permission. When the module is off, the tab does not appear at all.

Messages arrive late

Check the hub connection state (the wifi icon). If it shows disconnected, click reconnect or refresh the page. Corporate networks can block SignalR/WebSocket traffic.

Can customers see internal chat?

No. Internal Chat is only between authorised staff of the same company; it is completely separate from the customer channels.

I cannot create a group

Group creation is a separate permission. Ask your administrator to check the “create group” right; the one-to-one permission does not include it.

I forgot my PIN

Opening a locked conversation requires the correct PIN. There is no separate PIN reset screen; removing the lock may need the conversation owner or an administrator.

Is there an external integration or embed code?

No. Internal Chat connects to no external platform; it works directly inside the CRM once the module is on. To add a widget to your website, use the Web Chat module.

Which module is required?

The Internal Chat module is required. DeepL translation and the AI summary depend on the related services/permissions in your company configuration; no separate “Meta” or “web widget” module is needed.