MyChat Blog

We have a solution to a problem when someone sends a message to the wrong group. MyChat is very flexible when you need to adjust settings for your business communication.

Companies use MyChat conferences (group chats) differently, according to their needs. Some teams use one general conference and add all employees to notify them about important events. Others create conferences to divide people according to different departments.

Another approach is to create conferences according to projects when you add people from different departments who work on the same project.

Some users like public conferences, and other use the server’s auto-created or hidden conference where you can join only via invitation. Moreover, some admins like to protect conferences with passwords.

People can also create conferences with their own settings and invite teammates.

This is MyChat flexibility: combine features and choose which tool is the best for your task.

Oops! Sent a message to the wrong chat

Have you been in such a situation? This is a common mistake that deals with inattentiveness. No blame for that — sometimes we are overloaded with work and can’t pay enough attention to where we send messages. Unfortunately, we realize it when people start to react to a message 🙂

Yes, MyChat provides placeholders that indicate a conference you type in:

All MyChat users have the right to delete their own messages quickly (time is configured on the server). You can delete your own message by right-mouse clicking on it:

But it is not enough, apparently 🙂 No error shall pass, and we have some solution.

How to forbid accidental message sending in public group chats?

All we need is a script on the server that reacts to the event of a message sent in a conference — OnConfMessage. The server “intercepts” the message, checks it and sends it if everything is OK. Otherwise, a message is held back and a client application sends a notification that a person attempts to send a message to a wrong chat.

The Help page describes a script. The example lists conferences that have limitation on, and also a list of user groups that remain intact by those limitations. It can be administrators, supervisors or company security team.

const
  NOTIFY_FLAG = true; // true/false: notify a user that he can't write messages in a conference
  RESTRICTED_CONFS = '|main|';
  ALLOWED_ROLES    = '|Administrators|Operators|NSS|';
  
function OnConfMessage(iCID, iUIN, iUID, iMsgType: integer; sConfName, sMsg: string): boolean;
var
  sRoleName: string;
  bFlag: boolean;
begin
  bFlag := true;
  if pos('|' + sConfName + '|', RESTRICTED_CONFS) <> 0 then begin
    sRoleName := mGetUserRoleName(iUIN);
    if pos('|' + sRoleName + '|', ALLOWED_ROLES) = 0 then begin
      bFlag := false;
      if NOTIFY_FLAG then 
        mSendCustomMsgToClientConsoleByCID(iCID, 
          'Sorry, but you can not send messages to the conference #' + sConfName,
          'Status', true, true, 4);
    end;  
  end;
  result := bFlag;  
end;

begin

end.

The example is simple, but you can change something by adding work time, weekdays, deadlines, and lists of conferences from a text file to avoid getting the script text. Release your imagination 🙂