{"id":1386,"date":"2023-03-10T07:08:00","date_gmt":"2023-03-10T15:08:00","guid":{"rendered":"https:\/\/planfix.com\/blog\/?p=1386"},"modified":"2024-04-02T12:41:15","modified_gmt":"2024-04-02T10:41:15","slug":"dynamic-customer-segmentation-in-planfix","status":"publish","type":"post","link":"https:\/\/planfix.com\/blog\/use-cases\/dynamic-customer-segmentation-in-planfix\/","title":{"rendered":"Dynamic customer segmentation in Planfix"},"content":{"rendered":"
Planfix<\/span><\/a><\/span><\/div>\n\n\n
\"\"<\/figure>\n\n\n\n
<\/div>\n\n\n\n

“Yes, of course. We do that!”<\/em> This was our answer to a user’s request. And that request was as follows: “Please make a note or video tutorial about dynamic customer segmentation in Planfix. For instance, define certain conditions under which a customer falls into a given segment, and when they no longer meet these conditions, they \u2018leave\u2019 the segment. Dynamic segmentation of notifications would also be interesting: promotions, discounts, feedback prompts via SMS, messengers, etc.”<\/p>\n\n\n\n

So, with examples (which we’ll gradually complicate), let’s show you how to set up this kind of segmentation for customers and notifications.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Manual Configuration in Planfix<\/strong><\/h2>\n\n\n\n

Elementary, my dear Watson. We\u2019ll start with an example of the manual approach<\/em> to dynamic customer segmentation strategy. Imagine Watson\u2014Sherlock Holmes’ best friend, a military doctor, soldier, and at the same time, his manager, collecting requests to investigate extraordinary cases. He pays special attention to requests from customers who write more than three times.<\/p>\n\n\n\n

And while we’re on the subject of introductions: Watson, of course, works at Planfix crm system \ud83d\ude01<\/p>\n\n\n\n

<\/div>\n\n\n\n

How to Set Up Custom Workflow in Planfix<\/strong><\/h3>\n\n\n\n

Let’s look at how he built up his work. First, Watson created a contact template, “Sherlock Holmes’ Clients,” in which he inserted two custom fields – “Scheduled Meeting” and “Number of Requests.”<\/p>\n\n\n\n

Then he created a task template<\/a> – “Services of the best detective.”<\/p>\n\n\n\n

Set up a working template with multiple lists:<\/p>\n\n\n\n

\"Watson's<\/a>
Watson’s Work Scheduler<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

“New Requests”<\/strong> – here, you’ll find the requests for case investigations.<\/p>\n\n\n\n

“Clients”<\/strong> – contact cards of those who have contacted Holmes.<\/p>\n\n\n\n

“Clients who have written for the third time”<\/strong> is the dynamic list containing the clients who have written for the third time or more than three times. In the selection parameters, he set the conditions under which the contacts are segmented:<\/p>\n\n\n\n

\"Planner<\/a>
Scheduler list settings – “Clients who contacted us a third time.” (CLICK TO VIEW FULL SIZE)<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

“Meetings” – timetable showing the scheduled time for selected cases for Holmes.<\/p>\n\n\n\n

Watson has created two scripts<\/a> in Planfix to track the most active customers, such as those who have written to him three times.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Scenario Settings: Counting Requests<\/strong><\/h4>\n\n\n\n

The first script calculates the number of customer requests:<\/p>\n\n\n\n

\"Scenario<\/a>
Script Settings – “Count Requests”<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

Scenario Settings: Appointment<\/h4>\n\n\n\n

The second script resets the number of requests and marks that the meeting has been scheduled:<\/p>\n\n\n\n

\"Scenario<\/a>
Script Settings – “Meeting Scheduled” (CLICK TO VIEW FULL SIZE)<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

Now each new request from a client is counted by the script, and when the number of requests from a client reaches three, their contact details fall into the change list. This way, Watson sees it in the schedule list – “Clients who contacted you for a third time”:<\/p>\n\n\n\n

\"Result<\/a>
Scheduler list – “Clients who wrote for a third time”<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

When Watson is convinced that the case will interest Sherlock, he calls the client. He sets up a meeting by dragging one of his tasks to the “Meetings” calendar, where it\u2019s tagged with the “Scheduled Work Time” data tag<\/a>. The task no longer falls under the conditions and “leaves” the list of clients who have written for a third time.<\/p>\n\n\n\n

In this way, Watson processes the most active requests faster, selects unusual cases for Holmes from among them, and allows Holmes to hurry and find answers to them.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Automatic Configuration in Planfix<\/h2>\n\n\n\n

For some, it’s elementary, Holmes, but for others, it’s not. Let’s continue the exciting story of our two detectives and show the automatic version<\/em> of their work with dynamic segmentation not only of clients but also of notifications<\/a>.<\/p>\n\n\n\n

For instance, the detectives solve cases within two weeks, but sometimes this period may drag on. <\/p>\n\n\n\n

For such cases, Watson has created a filter with tasks \u2013 \u201cCase dragged on,\u201d a custom field of type \u201cText\u201d \u2013 \u201cMeeting point\u201d in the task template, and he\u2019s also configured an automatic script that:<\/p>\n\n\n\n