Communicating with clients from Planfix

The wide range of Planfix integrations for messengers and social media let you communicate with third-party users (including clients) in the following way:

• the client messages your company's account in a messenger;
• you receive their message as a Planfix task;
• your comments on this task are sent to the client via the messenger they wrote to you from.

This allows you to seamlessly process all messages received from any channel in one central location, the Planfix interface. At the same time, the client will continue communicating with you using the messenger or social media page, with no reason to believe you're not doing so as well.

Channels supported

• Chatra
• VKontakte
• Facebook
• Instagram
• Skype
• Telegram
• Viber
• WhatsApp
• Avito

Helpful information

When a client writes to you, Planfix automatically creates a contact card for them that contains their name and their username or ID from the channel they wrote to you from. That said, the link to the channel isn't set at the contact level; it's set at the task level.

Important consequences:

• You can merge all the contacts that were created for the same client who reached out to you using multiple channels. This won't affect your ability to communicate with the contact in the separate tasks created for each channel. All such tasks will be displayed in the checklist in the merged contact's card:

• You can use the corresponding task to initiate contact via any of the channels, or the Message button provides an alternative for some of the channels:

You can also use a bulk action on tasks to merge tasks created for communicating via different channels. When this is done, future communication in the merged task will be sent to the channel set in the task chosen to merge into. One exception is when there was no communication channel set in the task chosen to merge into. In this case, the channel from the task that wasn't "preserved" in the merge will be used.

Important

Users who are accustomed to using Planfix with apps or services that can have multiple "threads" or conversations, such as email, may want to use a similar approach when communicating with a client from a chat or messenger. The idea is that they'd like to discuss specific questions in their own separate tasks, and then use the different Planfix tasks to send messages to the client's messenger or chat app.

However, this idea doesn't take into consideration the main difference between chats/messengers and email — email allows for multiple threads of communication between the same people, but chats/messengers don't. On the client's end, they see all of your communication in one chat/messenger thread, and they can't separate this thread into multiple ones. This limitation is why we use integration differently in these cases and carry out all communication with contacts from outside sources within one Planfix task.

There are two important reasons for this different approach:

Reason 1. This is the only way that the employee responding from Planfix will see the same thing the client sees in their messenger. This forces the employee to not only just respond, but to also give a description of the question they're responding to, using quotes, highlights, mentions, etc. This gives the client an understanding of the context the response fits into, and they can have a productive conversation.

If Planfix offered the ability to communicate with one contact separately in different tasks, the employees responsible for each specific task would send messages related to their own task, without considering that all of their messages are being sent to the same thread on the client's end. The messages from one task would be randomly mixed up with the messages from the other tasks. This would inevitably lead to confusion. The client wouldn't be able to figure out which of the questions at hand each message (sent from Planfix) corresponded to.

To illustrate this scenario, let's take a look at how the same conversation looks with the current Planfix framework, and how it would work if we allowed separate conversations to take place in separate tasks.

Now, the conversation would look like this:

If communication with a client in a chat/messenger were separated into several Planfix tasks, it could lead to the following scenario:

Reason 2. You can't automatically determine which of the questions at hand the client's response corresponds to. The client's responses then can't be placed in the correct task, and there can't be a productive conversation.

These restrictions prevent us from separating a conversation with a client from a chat or messenger into multiple Planfix tasks.

Go To

• Integrations
• Feature Description