Lead with Data: Transform Success with Dashboards & Automation
2024 46 min

Lead with Data: Transform Success with Dashboards & Automation


In the dynamic realm of business today, leveraging data and digital strategies is crucial for amplifying customer success. Discover how Shiji ReviewPro revolutionized their customer success approach using data-driven insights, innovative dashboards and automated CTAs. Join us to uncover actionable strategies that can elevate your leadership effectiveness and ensure scalable success!



0:00

Welcome everyone. Happy Pulse once again. My name is Nate Bartlett. I'm an

0:08

enterprise

0:08

CSM at GainSight. It's my pleasure to introduce our next presenters. Just for

0:12

your sake of

0:13

understanding, we are in Track 1, Scaling CS, working smarter, not harder. So

0:17

that being

0:18

the case, if you would like to engage throughout the course of the presentation

0:21

, please pull

0:21

up your Pulse app, go down to the Q&A and Pulse portion and make sure you're

0:26

engaging

0:27

in Track 1. It's my pleasure to introduce from Shiji, sorry, my apologies, Shij

0:35

i Review Pro,

0:37

Kirsten Andres and Angela McKellie. Please join me in welcoming them to the

0:43

stage.

0:44

Thank you. Hi everyone. Welcome to Pulse. Very happy to be here, in my case,

0:52

for the

0:52

third time for Angela, actually, for the first time and we put her all to the

0:56

stage already.

0:58

So first of all, I would ask you for a big applause for Angela. So my name is

1:07

Kirsten

1:07

Andres. I'm the Senior Director of Customer Success and Operations at Shiji

1:11

Review Pro.

1:13

I'm half Catalan, half German, based in Barcelona, Spain. I've been working in

1:18

hospitality for

1:19

almost 20 years and now in Shiji Review Pro for almost seven years. And here

1:26

with me,

1:26

we have Angela McKellie, who is our CS Systems Manager. We'll go later on a bit

1:32

more into

1:33

detail on what her position is and all the magic that she does. So Angela McK

1:39

ellie, she

1:40

is from Italy, but she's based in Jilina in a very, very beautiful city in

1:46

Slovakia.

1:48

So yeah, and she's been with us, actually, for almost 10 years. So that's

1:52

impressive.

1:53

So the session that we're going to present today is lead data, transfer success

1:58

with

1:59

dashboards and automation. I think a lot of us are struggling with kind of the

2:04

same thing.

2:05

So now that we're getting into the eye world, and obviously this is super

2:10

exciting, and

2:11

I think during the keynote and the few sessions that we will attend, everyone

2:15

is like with

2:16

those eyes. But at the same time, you also need to start with certain

2:19

automation that

2:20

you can also do even if you don't use AI currently. So basically, we will cover

2:28

some

2:29

of what we do in Shiji Review Pro and our journey. Then we'll introduce you

2:34

with some

2:34

of the problems that we have. And Angela will then, as the expert, show

2:40

solutions we found

2:42

for that. Focusing on digital customer success, data-driven automated tasks,

2:47

scalability and

2:48

efficiency, and obviously what is the impact that this had in our business. So

2:55

let me introduce

2:56

you a bit to what we do at Shiji Review Pro. So as I said, my background is in

3:01

hospitality.

3:02

So what we do basically is software for hotels and restaurants. So we were

3:09

Review Pro, but

3:11

in 2019 we were acquired by Shiji. And this even made us more successful since

3:18

we were

3:19

looking into other solutions that Shiji was offering. So we really wanted to

3:25

close the

3:26

circle in hospitality from the PMS, which is basically the reservation or the

3:33

check-in

3:33

checkout systems that a hotel would use. POS with Infruses, which is what an F&

3:41

B venue

3:41

would use to take the orders and so on. And also with other products, also with

3:49

Shiji

3:49

Get Solutions, where we include Shiji Review Pro, where we focus on the guest

3:54

experience.

3:55

So a bit like we personally do with GainSAD or with other customer success

4:01

platforms

4:02

that you could be using, we provide to our customers the hotels or the

4:07

restaurants the

4:08

option to know how their guests are doing and what are the areas that they can

4:14

improve based on data.

4:15

So going a bit deeper into our customer success journey, obviously as always in

4:23

partnership with

4:24

GainSAD. And I want to take just a minute to talk about what we feel hearing

4:30

here very often.

4:31

And it's the human first piece. And this is so key from becoming a provider or

4:38

a tool

4:39

in order to become a partner of your customer. So what is key and what we felt

4:44

with GainSAD is

4:46

sharing all those best practices, also organizing this event to get all

4:50

together as part of a community

4:52

has been a game changer in order to continue with them and be so loyal to them.

4:58

So just to give you

5:01

a run back, so we started with GainSAD in 2017. There is when we created our

5:07

customer success

5:08

department. So we used to have only account management. But when we went from

5:13

an only product

5:14

to a multi-product, we realized that a lot of our long tail clients were churn

5:21

ing. So we wanted to

5:24

create this customer success department back then, which was only a department

5:28

to become a mindset

5:30

currently in 2024 for all our company. So back then, as we said, we created

5:36

that. We created

5:37

the health score in order to actually being able to measure what is the health

5:43

of our clients,

5:44

having the visibility that we were talking about. But at the same time, also

5:50

having this

5:51

visibility for all our departments, because obviously our sales department

5:56

maybe would go for an

5:58

expansion opportunity. But then, since they didn't have the visibility, they

6:02

were going blind and

6:04

maybe getting with a not very happy client that didn't want to

6:09

renew or even expand. Then, in 2019 and 2020, we focused on, well, since we

6:18

started partnering

6:20

also with the GainSAD PXPs with our product team, we implemented our in-app NPS

6:26

, because before we

6:27

were sending it through emails, but the conversion rate wasn't too high. So we

6:31

changed the add to

6:32

have through in-app engagement. And then in 2021 to 2023 last year, we really,

6:39

what we did is really

6:41

okay, let's wait, let's look back and see what can be improved. So we did, for

6:46

example, the revamp

6:48

of our product spotlight, product spotlight is an email that we sent now on

6:52

quarterly basis,

6:53

before it was monthly, to all our client base to present the new features or

6:59

maybe features

6:59

that we want to promote with our clients, to make sure they are up to date. And

7:05

if they don't

7:07

read the release notes, they have that specific email that would get into their

7:12

inboxes. We also

7:14

worked on the client lifecycle, a big focus obviously on the expansion and the

7:20

QBRs. And I'll go back

7:22

in a minute about the relationships between reactive and proactive, and making

7:29

sure that

7:30

there was more product adoption through our knowledge pod that we use. And

7:35

really, what we did also

7:38

in 2024, and let me move to the next slide, is thinking about this reactive to

7:45

proactive approach.

7:46

So as we said, we have this account management customer success departments,

7:50

but we wanted to

7:51

put everything together. Why we wanted to do this? Because we wanted to

7:56

differentiate,

7:57

which we weren't doing before, the support piece, which is more of the reactive

8:01

approach that our

8:02

support department has now, in order that our customer success managers could

8:08

focus,

8:08

what we said really matters, and engaging with our clients proactively,

8:14

identifying those risk

8:17

proactively before. And this is only possible through data and a lot of times

8:25

of the automation.

8:26

So this is what we are going to see, much deeper now. So before going to that,

8:32

I just wanted to

8:33

mention, so as we said, Angela is our customer success systems manager. She

8:38

actually used to

8:39

be the team leader of the support team. But then she wanted to explore some new

8:45

areas.

8:46

And she was so pivotal to become successful in what everything that we're doing

8:51

. Because

8:52

it's true that we started our CS operations team on an earlier stage. But at

8:58

the same time,

8:59

we saw that obviously they were focusing more on this strategy, and what are

9:03

the processes that

9:04

could be improved. However, we really needed a person that would focus on the

9:10

systems that we

9:12

use. And we'll go back to that later. But we use many systems, probably a lot

9:16

of you.

9:17

So we wanted to have really the person on one hand that has the technical

9:22

mindset.

9:23

She loves AI. So she's going to put us into that path as well very soon. She's

9:31

actually

9:31

already doing some investigations. So yeah, and the idea obviously would be

9:37

putting all this

9:38

technical sidepad. Also having it with her team work mindset that obviously

9:45

made bringing the

9:46

issues that we had as a customer success organization together with the

9:52

operation to make sure

9:53

that we can leverage some of the repetitive tasks for the team.

9:58

So on the digital customer success, some of the challenges that we found at the

10:05

beginning

10:07

was first inconsistent and manual onboarding. So we had a lot of processes that

10:14

needed a lot of

10:17

manual interaction from our customer success managers. And we wanted obviously

10:22

to avoid it,

10:22

because otherwise they wouldn't have time to do what really matters, which is

10:27

engaging with our

10:28

clients. Then also the self-education options. We had our learning and support

10:35

system. We had

10:37

certain videos, but as you probably all of you know, if you have videos, you

10:43

always need to

10:44

get it updated on a regular basis if your product is developing obviously. So

10:51

we also focused on

10:53

on other pieces to solve this. Then as we said, we didn't have the visibility

11:02

as a CSM to know what are the support pieces or the raising tickets that were

11:09

done by us,

11:12

let's say, by the CSMs. And yeah, again, as we said, some repetitive tasks. So

11:19

now I presented

11:20

some of the challenges over to Angela for the solutions. So whenever we

11:26

encounter something

11:28

that's heavily manual, the very first thing that we want to do is to automatize

11:33

the majority or the

11:35

highest volume that we can out of it. So when we looked at the onboarding

11:40

process, how it used to

11:42

be done, we are talking sending email templates through our ticketing system,

11:49

manually by the

11:50

support team or the CSM team. So absolutely we needed to automatize it. And we

11:57

will see some

11:58

examples later, but to solve the challenge of it being so manual, so reliant on

12:07

the support

12:08

and the customer success manager team, we automated as much as possible out of

12:15

it, out of the onboarding

12:15

process. For what concerns the fact that the customers, so the options of self-

12:22

education,

12:22

like CSM was mentioning, where they are, where available, but we found that the

12:27

customers were

12:28

not really aware or were not using them as much as we would have liked. So we

12:33

made sure that the

12:37

customers were aware of these solutions as well as we revamped them as much as

12:43

possible so they

12:44

could be as useful and engaging as they could be. For the reliance on the CSM

12:54

support teams,

12:54

we set up in-app engagements which can guide the customers to find the

13:00

solutions that they are

13:02

looking for, to understand and learn and get the value out of the tool instead

13:07

of having somebody

13:08

who holds them by their hands and drives them there. And for the fact that the

13:16

time of the team was

13:17

consumed on repetitive tasks, we have configured a knowledge bot on with games.

13:24

mpx in-app, that's

13:25

where the customers are actually, the end users, that could explain where they

13:31

could find the

13:31

articles that could help them directly there without having to raise a ticket

13:36

for the team.

13:37

So, what have you, this is an example, what we have done, this is a journey

13:44

orchestrator program

13:45

that we have set up for an onboarding journey. All our onboarding journeys now

13:51

are fully automated

13:52

using journey orchestrator programs. What we do is that we have a connector

13:57

with our CRM.

13:59

The connector brings in the data that we need to trigger the program and in

14:04

this way, every new

14:06

customer is getting the onboarding program that they need to start their

14:10

journey. Just to give you

14:14

a few numbers, so about 600 emails were sent automatically since January 2024,

14:23

that's first of

14:23

600 emails that the CSM team or the supporting didn't have to send manually.

14:28

But also, if we

14:29

calculate about five minutes per email to find the right data, select the right

14:36

template,

14:37

send it over, find the right contact and so on, that's about 55 hours of CSM

14:43

time.

14:44

That's given back to the customers. So, what does it mean? Because the CSM team

14:48

or the supporting

14:49

don't have to do these manual tasks, like you have heard in, I'm sure many

14:55

sessions here already,

14:56

they can actually take that time and focus on the things that really matter,

15:00

that human interaction.

15:02

For the onboarding content in app, we have launched an onboarding pilot for

15:11

small segments

15:13

by using, but by really pushing the Gensite TX guide engagements, the power of

15:20

it, why? Because

15:22

especially for onboarding, guides are really useful because they literally tell

15:28

the customers

15:29

where to click, what to do next and what to do. So, we have used the guides

15:37

engagements and we

15:38

have created an onboarding journey for them. We have also revamped all the

15:44

onboarding content

15:45

in app that we used to have so that it is in line with our standards, with our

15:51

new designs and

15:53

it is as engaging as it can be. So, as I was mentioning earlier, because this

15:59

content is in app,

16:01

it is more engaging because it's right there. So, it's not an email that you

16:05

have to read and

16:07

then maybe you're going to go on the app and actually do what the email says

16:11

you should be doing as

16:12

an end user. You are there and you are more likely to actually do what you're

16:19

supposed to be doing

16:21

in your onboarding journey for you to get the value out of the tool in the end.

16:30

This is our knowledge bot for admins. The administrator users can review basic

16:38

and advanced materials

16:40

again directly in app where they needed most and because it's in the knowledge

16:46

bot, it's always

16:47

available. We are aware that we have many different types of learners and many

16:52

types of learners with

16:54

different speed of learning. So, somebody may need one hour to go through the

16:59

all the onboarding

17:00

materials. Somebody may have just 10 minutes and then the following day another

17:05

10 minutes because

17:06

the knowledge bot is always available. They can just check the materials

17:10

whenever they can or they

17:12

want and go back to it if they forget something or if they want to review it.

17:18

Inside of the knowledge

17:20

bot, we have put as many different types of materials of learning materials

17:25

that we could.

17:27

So, we've got articles but we also got videos and we've got the guide

17:33

engagement for somebody

17:34

who is more hands-on in learning. Thank you Angela. So, on the data driven

17:43

automated tasks,

17:45

some of the challenges that we also faced was obviously the lack of visibility

17:50

on risk and

17:51

opportunities. So, we started with the health score as we said. We started also

17:55

with the NPS but

17:57

obviously this was not the only metrics that we could use in order to know if a

18:02

client would

18:03

renew in the end and if they would expand also in the end. And one key that has

18:10

been very challenging

18:12

for us to go from this reactive to this proactive approach is really making our

18:19

CSM's understand

18:21

why is it so important that they understand what is the value that our clients

18:26

want to take

18:28

out of our tool, let's say. But not only our tool, but also as a consultant, as

18:33

a sharing the best

18:34

practice. We for example, release a benchmark report that we do globally on

18:41

yearly and quarterly

18:42

basis. So, really reading this benchmark report to bringing the value to the

18:48

clients. And the first

18:50

thing to start with that is actually asking your clients what is the outcome

18:54

that they want to

18:56

achieve when purchasing your product. And then as we said, so lack of

19:03

visibility of customer

19:05

satisfaction. So, on one hand we have the health score, the NPS, but we were

19:09

also lacking on some

19:10

other surveys that we implemented and that Angela will go more into detail.

19:18

So, for the lack of visibility on risks and opportunity, we have configured

19:24

that as

19:24

driven automated CTAs. I will show you examples in the following slides.

19:30

For the lack of visibility on customer desired outcomes, we have been using the

19:37

customer goals

19:38

feature within K-Insight CS. And we have improved the way we are tracking data

19:45

in terms of

19:46

customer and usage. And for the limited visibility on customer satisfaction,

19:54

we have created automated surveys at Success Plan Culture.

20:00

So, for the data-driven automated CTAs, these are a few examples that we have

20:08

configured.

20:10

We have got for risk, for example, we have got a CTA that goes to the customer

20:16

success manager

20:17

leaders if there is a touch point where the risk is high. We have got for

20:25

opportunities,

20:26

we have got a CTA to the CSMs if there is an app itself for a new property for

20:31

big segments,

20:32

for them to actually make sure that the configuration has been done correctly

20:36

and the onboarding and

20:39

the following steps can go as smoothly as possible. And for the risk management

20:46

, we have got a CTA

20:47

to the customer success managers for big segments if there are no touch points

20:52

within the previous

20:54

90 days. So, during this year, we have generated 900 CTAs that were not there

21:04

before. So, whenever

21:07

you look at this automations, we always have to think how it was before. So,

21:12

there were no touch

21:13

points for risk. Sorry, there were no CTAs for the touch points where the risk

21:20

was high. So,

21:22

the leaders could jump in, but only if they were made aware of the risk by the

21:28

customer success

21:29

managers. In this way, because the CTAs are triggered by rules, we are 100%

21:35

sure that they are always

21:37

triggered no matter what happens after. So, we are able to cover a bigger

21:43

amount of cases.

21:45

For the customer goals, we really are advising and we are really pushing the

21:53

customer success

21:54

managers to use customer goals to track the desired outcomes and expectations

22:00

of the customers. This

22:01

not only for them to keep track on, okay, what are the goals that we agreed on

22:06

with the customers,

22:08

where are we now? But then also, when they are looking at the retroactively

22:13

during the reviews

22:15

with the customers, they can also use that to showcase value. This is what this

22:20

is the agreed

22:21

value that you wanted to achieve. This is the goals that we agreed on and this

22:26

was achieved.

22:27

And then for the higher visibility, we have revamped the C360 page so that now

22:39

whenever a

22:39

customer success manager goes into the C360 page, all the data is available.

22:46

They are able to see

22:47

the NPS, the usage, the health score trends so they can have an immediate

22:54

reference on how the customer

22:58

is doing. And for the surveys at Success Plan closures, so we used to, as Kist

23:08

ram was mentioning,

23:10

we implemented the NPS score, but then we realized that the NPS score gives us

23:17

good data, but it's not

23:19

the whole picture. For example, we've got some processes, some implementations

23:26

in place, and we

23:27

also wanted to know what was the customer satisfaction about those

23:31

implementations.

23:32

So now what happens is for each implementation, we got a specific Success Plan

23:38

and whenever the

23:38

Success Plan is closed by the customer success manager, these triggers an

23:43

automatic journey

23:44

or accelerator program that sends out the survey to the customers where we can

23:49

pick up the feedback

23:50

on how the implementation went. Thank you, Angela. So on some other challenges

23:59

that we had and that

24:01

we were, we wanted to really increase the scalability and efficiency of our CS

24:06

Ms. We presented some of

24:08

the automated programs. But as we said, the most challenging part, and I think

24:14

we've been mentioning

24:15

this also through AI, is all this time-consuming, repetitive manual tasks that

24:21

our CSMs don't want

24:22

to do. But obviously, as maybe from the leadership, we need to have a way in

24:29

order to measure the

24:31

performance of our CSMs, but at the same time how happy our clients are. Then,

24:36

as it was mentioned

24:38

in the keynote, we also had a lot of siloed, isolated and incurring data. And

24:44

this was not only at the

24:46

beginning because of the silos between departments, but above all, so on the

24:50

silos of the different

24:52

tools that we were using. The CRM, Gainside, Gera for the ticketing tracking,

24:57

the ticketing system that

24:58

we use to communicate with our clients and so on. Then, obviously, we, at the

25:06

same time,

25:08

using all the tools will make that all the workflows, processes, and so on,

25:13

would sell in different

25:14

tools as well. And that our different departments, seeing sales, finance,

25:20

product, and so on, would

25:22

use different systems at the same time as well. And again, what would spring

25:29

that, that would

25:30

be our CSMs, or even us in the leadership team, would also spend too much time

25:36

searching for the

25:37

data that could make us take certain decisions on how to improve our risk

25:43

mitigation.

25:44

So again, for the time consuming and repetitive manual tasks, we went for the

25:53

automation. And then,

25:54

for all the other challenges that we have seen, so the isolated and incoherent

25:59

data, the workflows

26:01

and processes spread among multiple systems. And because of that, the customer

26:06

success and support

26:07

team having to chase the data and the information across multiple platforms,

26:12

the solution was to

26:13

bring the processes and the data into one system as much as possible.

26:17

For the CTA, so we created CTA and dashboards for CSMs and leaders.

26:29

CSMs and leaders get automatic CTAs when it's time to take action during an

26:36

implementation.

26:36

The CTA includes all the necessary information to action the first steps.

26:43

Because it is being

26:45

triggered within the system, then the data can be seen and analyzed in one

26:52

place using dashboards,

26:56

which again removes the necessity of checking the customer data on

27:01

gain site and then going on the CRM to check the sales-related information,

27:06

and then going to the ticketing system to check the tickets and so on.

27:09

This is a very specific example of an improvement of a revamp that we have done

27:20

for a process.

27:22

It's the onboarding calls process. So a brief introduction of the process is

27:28

whenever we have

27:29

a small segment that contracted a specific product, our customer success

27:35

managers reach out to them

27:36

and give them an onboarding call, which is basically they go through with them

27:41

the biggest

27:44

features that they are supposed to be aware of within in the tool during their

27:49

onboarding phase.

27:52

This is how the process used to look like. Each color that you see is a

27:57

different system.

27:58

So what would happen is that the opportunity was closed one in our CRM. The

28:05

leader of the onboarding

28:06

calls would check if the customer actually qualifies for the call and assign

28:11

the task to a customer

28:12

success manager, which then would go on the ticketing system, send the

28:17

invitation to the

28:18

customer, then they would go back to the CRM, update the data there, then they

28:22

would go on

28:23

the game site, create the success plan, they would go back to the ticketing

28:27

system, continue

28:28

the conversation with the customer, go back on the game site once they had the

28:31

call to log the

28:32

touchpoint, go back on the CRM to update the data there, and then that would

28:37

trigger sending the

28:38

satisfaction survey from the game site. And this is how the onboarding calls

28:45

process

28:47

look now. There is only one piece that's on the CRM, which is when the

28:52

opportunity is

28:53

closed one, but everything else was brought into game site. What is it, the

28:59

asterisk? It means

29:00

that the process has been automatized. So automatically the rule triggers in

29:07

game site triggers a

29:09

CTA for a designation. Then if the leader says yes, this is onboarding call,

29:18

then this

29:19

automatically triggers a CTA for the customer success manager and the success

29:24

plan is created

29:25

automatically. Customer success managers can send the emails to the customer

29:33

via success plan

29:35

in game site, they log the touchpoints in game site, and then once the success

29:39

plan is closed,

29:40

the survey is sent automatically from the inside.

29:43

I don't know if you can see it, but this is actually, I was preparing a

29:51

different presentation

29:52

some weeks ago, and I asked the leader of the onboarding calls, Yana, to give

29:59

me some feedback

30:00

on how this new process is going. And actually this is the feedback that she

30:06

has given me.

30:07

This is the original message, it's a screenshot. And she's saying that the

30:13

assignment process went

30:14

from 10 minutes to a few seconds. The manual creation of the success plan was

30:19

taking about

30:20

three minutes. Now it's done automatically. The communication with the client

30:25

went from 5-10

30:26

minutes to a few seconds, and the finalization of the whole process went from

30:32

10 minutes to

30:33

1 minute. So take all these great results and multiply it by 76, which is the

30:42

amount of onboarding

30:43

calls that we have generated for the 2024. All right, so before we go actually

30:52

to the impact on our

30:53

business, and that's a good example that Angela added the information of our

30:58

elite for the onboarding

31:00

calls designation, I think this is also key to keep in mind. CSOPS and the CSMs

31:05

will always need to

31:07

work together. So if CSOPS, for example, is implementing a new process,

31:11

obviously what we

31:13

tried to do is get the feedback from the CSMs or from the leadership team. So

31:18

we can see,

31:20

as we said, we're saving the time and making their lives easier.

31:24

So just as a wrap-up, let's say, so with all those projects and revamp projects

31:34

that we did,

31:34

we actually seen an increase of 17% year to date on our health score. And this

31:44

was a wrap-up thanks

31:47

to the improving the engagements via CTA's customer goals and programs,

31:52

improving the

31:53

adoption thanks to our knowledge bot and self-service system, improving

31:57

satisfaction,

31:58

thanks to the success plans, the surveys, and by empowering also CSMs to use

32:04

our

32:04

three six new revamp 360 and home page to realize where the data sits and

32:12

obviously all the

32:14

automations that we put in place. On the other side, also we increased 900% of

32:22

our productivity

32:24

based on that. Those were obviously mainly achieved through the automations.

32:30

And as Angela was explaining, obviously as a leadership team and for the CSMs

32:37

as well,

32:37

it's taking us less time to find the right data in order to take the most

32:43

relevant actions.

32:45

On the other side, we also increased our proactive churn retention on a 38%.

32:56

And it's a bit difficult to explain that, but obviously we have our churn

33:02

retention.

33:04

But here what we're talking about is, as we said, being able to have the time

33:08

to reach out proactively

33:10

to those clients that didn't have any call or any touchpoint during the last 90

33:15

days,

33:15

that maybe had a high risk identified and we didn't have the time to follow up

33:21

on that.

33:21

Or maybe also a lot of the times the leadership team would get involved in

33:27

those complaints that

33:29

would also take our time of focusing on other strategies that we need to take

33:34

care of.

33:35

And which is really impressive with our knowledge bot. It's actually we got

33:42

over 15,000 interactions

33:45

with our new knowledge bot. And this is also why we want to not only have this

33:50

for our admin users,

33:52

but also for any other type of users moving forward. So hopefully we'll be able

33:58

to bring that

33:59

in our next poll session. And we wanted to do like a last sentence, let's say,

34:06

to wrap up the

34:07

presentation. So we chose that. And it's the power of data and automation,

34:13

achieving

34:14

and much efficiency, scalability and customer satisfaction, but a full together

34:19

. As we said,

34:21

this is key. Make your CSOps team talk to your CSMs to your leadership team, as

34:28

well as the other

34:29

departments, because the first start where you cannot have a silent mindset,

34:35

obviously, is in your

34:36

own department and company. And actually, I wanted to thank some of our

34:41

customer success team members

34:44

that are also here with us. And first of all, so we don't get that nervous. But

34:50

there also a

34:51

representation of what we achieved together. And as I said before, always with

34:57

a human first

34:59

approach. Thank you. Yeah. And if I can add, I would like to do a big shout out

35:08

to Fernando.

35:09

She's sitting here in the first row. And she's my best buddy in actually making

35:16

every, most of these

35:17

things that you have seen happen. She has been absolutely key for many of these

35:22

projects that

35:23

you have seen. So thank you. All right. So I think we have some time for a Q&A.

35:34

So we're going to

35:36

continue actually doing that. You see that there are some thumbs. So we will

35:42

see the questions flowing.

35:44

But if there are any that you're especially interested in, please just put the

35:49

thumbs up.

35:50

So the first question goes from Jenna, automated onboarding. How do you ensure

35:56

customers are

35:57

engaging with onboarding emails, especially if they're not personalized? Do you

36:02

find that your

36:03

team have to follow up after the automated emails, calls, meetings, etc. That's

36:08

actually a very

36:08

good question, Jenna. And this was mainly why we also, as Angela was explaining

36:13

and she can

36:14

complete the answer in a minute, why we decided to reduce the amount of emails

36:21

that we were sending.

36:22

Because obviously the conversion rate would be a bit lower. If it wouldn't

36:27

include the

36:28

personalization, it would obviously be a longer threat, let's say, and put this

36:33

into

36:34

in-app engagements that would go through the tool to let them know what are the

36:41

next steps

36:41

that they need to check. Yeah. So regarding the onboarding, this is actually

36:47

one of those

36:48

challenges that we were seeing when we were sending out the onboarding only

36:53

through emails.

36:54

And that is, yes, we can see the emails were being opened, but we don't really

37:00

see if,

37:01

what happened after that point. So now that we've got the pilot ongoing where

37:08

the onboarding

37:10

engagements are in-app and they are made by Gensite PX guides type of

37:15

engagements,

37:16

the cool thing with those type of engagements is if it has multiple steps, you

37:21

can actually see

37:23

if there were any drop-offs. So if the guide was completed and if there were

37:28

any drop-offs,

37:29

where did the user drop-off? This is the first good data that you can get from

37:35

this type of

37:35

engagements, but also within Gensite PX, you can also create reports where you

37:43

see

37:43

whether the user that finished that engagement actually ended up going to the

37:49

section that you

37:50

are explaining within that specific engagement, for example. Thank you, Angela.

37:57

So if we move to the next question is we found that if there are too many CTA's

38:02

CSM's get blindsided, did you face a similar challenge and CTA adoption? So we

38:07

have here two

38:08

of our team leaders. I think they can come and stage and respond for that, but

38:11

yeah, definitely.

38:12

We had many challenges and we're still facing challenges, of course. So I think

38:18

what we really

38:19

did is identifying those CTA's that where we wanted to focus on, because as you

38:24

said, if you're

38:25

starting with too many CTA's, the CSM's doesn't know where to start. So we had

38:32

a big focus on those

38:34

bigger segments, larger accounts, because as we explained, the idea of the long

38:38

tail clients is

38:39

that we will do those onboarding calls, but at the same time, everything

38:43

through their process

38:44

would be a self-learning path and automate it. However, with the bigger

38:48

segments, what we try

38:50

to do is to be in contact more often. So we have a rule of having a touchpoint

38:57

at least

38:57

every 90 days. So this is where we focus on, but on the other side also on the

39:04

high risk

39:04

mitigation that would trigger through the touchpoints that the CSM's put.

39:10

However, what I think has

39:12

been super pivotal, as Angela was explaining, is for the leadership team to

39:17

have the visibility

39:19

on all those CTA's that were enclosed. Sometimes it could be overwhelming as

39:24

well. So having those

39:26

dashboards and reports, then they are able to tackle this during the team

39:30

meetings, during the

39:32

one-to-one scatchups and so on. Angela, you want to mention that? Yes. So also

39:37

for the CTA's, in

39:38

terms of systems, what we have done is that when we created, configured the CTA

39:43

's, we have added

39:45

tokens inside of the CTA's. So when the CTA is generated, the title and the

39:52

content already gives

39:54

the customer success managers an idea of what precisely what the CTA is for. So

40:00

when they go

40:01

check their cockpit, it's easier for them to actually filter them out or

40:07

determine what CTA's

40:09

are still pending. And another thing that we have done is that we have

40:13

activated a rule that

40:15

automatically clears out all the old CTA's if they have not been closed within,

40:24

I think it's

40:24

for the previous years. So this also helps with keeping that cockpit really

40:29

relevant and clean.

40:30

Thank you. Next question from Sam. How many customers would a typical CSM

40:37

manager at your

40:38

at your organization? So I would respond to that saying that it really depends

40:44

on the market. So

40:45

since we cover seven different languages from our CSMs, we try to divide best

40:51

through markets.

40:53

So depending on the market, for example, the UK market, we have a very big

40:57

client base.

40:58

But since they are very advanced, they might not need so much proactive

41:05

engagement from our CSMs.

41:08

However, for example, I don't know, for the French market, we don't have that

41:15

big client base.

41:17

So then what our CSMs have, they're doing kind of different markets. But in

41:22

average, I would say,

41:23

they usually look after between 30 to 40 accounts. It's true that we have some

41:30

specific CSMs that look after more of the larger accounts. So in that case, it

41:36

would be maybe

41:37

one to even one to five accounts that they look after because the engagement

41:42

that we have with them

41:43

is much more than with some other markets.

41:52

Then Adriane's question, based on what criteria do you measure the increase in

41:57

productivity?

41:58

I got this one. That's a good question. So this was based on the feedback that

42:03

you have seen

42:04

from Yana. So the reduction of how long it used to take versus how long it

42:10

takes now.

42:11

And then it was applied on a formula, which I don't remember by heart.

42:17

But it gave us that 900% increase if you're interested in the formula,

42:24

then you can catch up with me later or send me a message on the pulse up and I

42:27

can share it with you.

42:28

Thank you, Angela. 900 CTA's are a lot. Yes, they are. How many CTA's for CSM

42:37

is that? Where

42:38

they all work or somewhere ignored because not relevant and created noise? And

42:43

yes, actually,

42:45

you want to take it? Yes, so these just a clarification, 900 CTA's were not

42:50

only for the

42:50

customer success managers were also for the leaders. So here you've got the CTA

42:55

's for the

42:56

leaders when there is an designation to be done or the CTA's to the leaders

43:02

where an onboarding

43:03

program was failing and the support team needed to jump in and recent the

43:07

program or contact the

43:09

customer differently. And then yes, also the CTA's for the customer success

43:15

manager. So it's not

43:17

only for the CSM's, it's more like covering different situations and different

43:23

owners.

43:23

Then there are some CTA's that do need to be action. So for example, when we've

43:28

got

43:29

an implementation, then the customer success manager knows that they have to

43:33

create a success

43:34

plan and continue with the process. But there are some CTA's that are just for

43:38

notification,

43:38

like for example, just to let you know you have been assigned these big company

43:44

. And in that case,

43:45

they just take it as a notification and close it and there is nothing else to

43:50

be on there.

43:50

If I might add to that to those CTA's that we were mentioning on risk

43:55

mitigation for those

43:56

accounts that didn't have any touch points during the last 90 days, just to

44:00

give you an average

44:02

buy CSM's. It should be, I don't know, 15 to 20. Obviously, ideally they wouldn

44:08

't have any because

44:09

it means that we're engaging with our clients, but we know the reality of our

44:13

day today. So it's

44:14

complicated and at the beginning, and I think this is important, that try to be

44:20

vulnerable here,

44:21

that even if you start and you see you're putting too many or creating too much

44:26

noise

44:28

for your CSM's, that's okay in the sense if they provide the feedback back to

44:33

you and you take

44:34

decision and do some changes based on their feedback.

44:39

Then I think this would be the last question. So do you use different in-app on

44:46

boarding

44:46

journeys for different user roles? You want to take this one?

44:50

Yes. So right now the in-app on boarding journey is made for administrators,

44:56

the pilot,

44:57

but we've got some content within the new knowledge pod for users type, which

45:03

Fernando is working on,

45:05

and that has guides for users. So yes, right now the pilot is for

45:10

administrators only, but the idea

45:12

is to roll it out personalized depending on the user type.

45:17

Thank you. So first of all, I wanted to thank absolutely everyone for attending

45:24

the session,

45:25

and it was mentioned before, and we do that for our customers as well. We love

45:30

feedback, so if you can

45:32

just rate our session, that will definitely help us to improve for future times

45:40

And here you have a super expert at GainSight and everything that is related to

45:44

systems.

45:45

So if you want to come to see us later, that would be great catching up. Thank

45:50

you so much.

45:50

[applause]

45:57

Thank you so much. Everyone, let's hear it again for Angela and for Kirsten.

46:02

Thank you so much. That concludes our morning session.