Hello Everyone,
We are trying to implement the Churn prediction model in CI for a customer. We have many questions about it in term of best practices:
If you can help me on one of this point I will appreciate a lot !
Thanks in advance :)
You're welcome!
Unfortunately, currently only the detail parameter is used in the churn model to take additional info (i.e., satisfaction). In the future version, we will consider to use event for model improvement. Thanks a lot for your feedback!
Thank you very much Zhi for these informations !
I'm just a little surprised for the event parameter: you mean that no matter which variable we choose it doesn't impact the model performance. For example for a ticketing activity it would be great to bring more information than just the creation date, but also that this ticket has been created by email/phone or add the customer satisfaction rate on this ticket... So it is the same for detail parameter ? Whatever we fill in it does't impact the Churn model performance ?
What is the best way to test the Churn model ? To train it on a part of the dataset (all data except last 6 months for example) and then compare results with the other part (last 6 months data) ?
Does the event parameter or activity type in activities has an impact on the model training ? What about the detail parameter ? Can we use a continuous variable or only categorical ones ?
Should we split activities to obtain better results, ex: slit entity tasks into phone calls and email correspondence or tickets into incident and asks
Why event activities for subscription is set by default to “Is a recurring subscription” when we created it from the Churn model?
Hi Dimitri,
Thank you very much for raising it.
We will come back to you soon.
Yours,
Nimrod
André Arnaud de Cal...
291,965
Super User 2025 Season 1
Martin Dráb
230,836
Most Valuable Professional
nmaenpaa
101,156