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
Responsible Gaming is a strategic priority and an area of continuous development. We are enhancing behavioural analytics to detect early signs of risk and trigger proactive interventions. We have made limit- setting and self-exclusion workflows clearer and more accessible, reducing friction for users who need them.


We also expanded customer-support training so that teams handle sensitive cases with accuracy and care. Effectiveness is measured through adoption of moderation tools, reduction in harmful behavioural recurrence, and overall engagement patterns that indicate healthier usage. Our goal is to act before issues escalate, not only after they occur.


On the customer-service side: as you scale in Brazil, how are you structuring your support organisation and processes (e.g., multilingual, 24/7, omnichannel) and what role does automation or AI play in that improvement?


Scaling in Brazil required a complete redesign of our support organisation. We now operate an omnichannel model, ensuring users can move across touchpoints without losing context. We expanded availability for continuous support and strengthened multilingual capabilities where each brand requires it.


Automation plays a key role in triaging simpler requests, while AI tools assist agents with contextual insights and suggested responses. Tis increases accuracy, reduces handling time and allows human teams to focus on cases that genuinely require specialised attention.


How closely do the RG and customer-support teams work together at Esportes Gaming Brasil? Can you provide an example of how the link between support-service enhancements and RG safeguards has yielded a measurable benefit (for players or the business)?


Te integration between our regulatory and support teams is now mature and fully data-driven. Both areas coordinate closely, sharing criteria, alerts and standardised protocols. When the system detects risk signals, support staff receive precise guidance on how to communicate and which protection tools to recommend.


Tis alignment has already generated measurable outcomes, including shorter resolution times in critical cases and a reduction in repeated risky behaviours. Te result is greater user protection and higher operational efficiency.


Your group recently launched the LOTTU brand in Brazil, built on a new platform from scratch with speed, personalisation and a strong RG/tech backbone. Looking back, how would you assess its success to date in terms of user-acquisition, retention, brand positioning and regulatory compliance?


LOTTU was built natively within the regulated environment, which made its technical planning more efficient and accelerated its launch. Te product quickly found its audience, especially among users who value straightforward journeys and clean, modern interfaces. Early acquisition and engagement indicators are strong, and the brand has secured a clear position in our portfolio: fast, lightweight and highly


147


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