search.noResults

search.searching

saml.title
dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
that is necessarily the right thing to do next. Tere may be another action that is far more relevant to that individual customer. Tat is the limitation of compartmentalising customers into journeys. Te system is effectively saying: "You meet these criteria, therefore this journey applies."


What we really want to ask is: "Given everything we currently know about this customer, what is the best thing to do next?"


Is that why you believe operators need to move away from thinking primarily about customer journeys and instead build a dynamic understanding of each individual player?


Yes. Journeys are useful organisational constructs, but customers don't behave like journeys. A customer can simultaneously be high value, showing signs of churn, interested in a new product, changing their playing behaviour and becoming more or less responsive to certain types of promotion. Tose things don't happen neatly one after another.


So instead of deciding which box the customer currently belongs in, the better approach is to continuously understand that individual and decide what action makes most sense given their current context. Tat is a very different way of thinking about CRM.


What does “dynamic understanding” mean in practice, and how is it different from the single customer view or increasingly granular segmentation operators already use?


A single customer view is important, but having the data and knowing what to do with it are two different things. Traditionally, a single customer view might tell you the customer's value, the games they play, their deposits, profit and loss, frequency of play and lots of other attributes. Tose fields may change over time, but the way they are used is often relatively static. Tey feed segments, models or predetermined journeys.


A dynamic understanding means continuously looking at those signals in combination and asking how a change in behaviour affects what we believe about that customer's future value and what we should do next. Te important part isn't simply having the 360-degree customer view. It is having a dynamic decisioning capability sitting on top of it.


If one thing changes, what does that mean for everything else we know about the customer, and does it change the action we should take? Tat is where it becomes much more powerful than increasingly granular segmentation.


130


Once you have that understanding, how does optimising for lifetime value change the next-best-action decision compared with optimising for an immediate response, deposit or engagement?


It changes the time horizon. If you optimise for an immediate deposit or click, the obvious decision can often be to communicate now or put an incentive in front of somebody. But that doesn't necessarily maximise the long-term relationship. Tere is a lot of discussion about real-time CRM in gambling, but actually a huge amount of good CRM isn't about responding instantly. It is about understanding behavioural patterns.


Imagine a customer who normally plays blackjack or poker on a Friday night. Occasionally they lose a hand, stop playing and leave. You don't necessarily need to immediately react and say, effectively, "We've noticed you've stopped - come back." Tat may simply be completely normal behaviour for that customer.


Te more useful signal is when they start deviating from their normal pattern. So there is absolutely a place for real-time intervention, but there is also enormous value in understanding historical behaviour, normal playing patterns and predicted future behaviour.


Optimising lifetime value means choosing the action - and the timing - that is most likely to improve the overall customer relationship, rather than simply maximising the next response.


One possible action is to do nothing. With so much emphasis on real-time CRM and hyper-personalisation, are operators in danger of assuming better technology should mean communicating more frequently rather than making better decisions?


Definitely. For years, there has been enormous pressure in CRM to communicate more. How many customers have we contacted? How many campaigns have we sent? What are our competitors doing? How many times have we spoken to this customer this week? But that isn't how people behave.


If you repeatedly send somebody irrelevant messages, they don't necessarily unsubscribe. Often they simply stop paying attention. Once that happens, you've damaged the future value of that communication channel. I've heard the argument before that brands need to maximise their "mental availability" with customers. In CRM, I think relevance is much more important.


Relevance beats frequency. Sometimes the best possible action is doing nothing. Don't spend money unnecessarily. Don't send somebody an offer they don't need. Don't talk about something they have only a marginal interest in. Wait until there is something


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140  |  Page 141  |  Page 142  |  Page 143  |  Page 144  |  Page 145  |  Page 146  |  Page 147  |  Page 148  |  Page 149  |  Page 150  |  Page 151  |  Page 152  |  Page 153  |  Page 154  |  Page 155  |  Page 156  |  Page 157  |  Page 158  |  Page 159  |  Page 160  |  Page 161  |  Page 162  |  Page 163  |  Page 164  |  Page 165  |  Page 166  |  Page 167  |  Page 168  |  Page 169  |  Page 170  |  Page 171  |  Page 172  |  Page 173  |  Page 174  |  Page 175  |  Page 176  |  Page 177  |  Page 178  |  Page 179  |  Page 180  |  Page 181  |  Page 182  |  Page 183  |  Page 184  |  Page 185  |  Page 186  |  Page 187  |  Page 188  |  Page 189  |  Page 190  |  Page 191  |  Page 192  |  Page 193  |  Page 194  |  Page 195  |  Page 196  |  Page 197  |  Page 198  |  Page 199  |  Page 200  |  Page 201  |  Page 202  |  Page 203  |  Page 204  |  Page 205  |  Page 206  |  Page 207  |  Page 208  |  Page 209  |  Page 210  |  Page 211  |  Page 212  |  Page 213  |  Page 214  |  Page 215  |  Page 216  |  Page 217  |  Page 218  |  Page 219  |  Page 220  |  Page 221  |  Page 222