WEBVTT - Consumer Talk: Service bots could alienate customers

0:00:00.920 --> 0:00:06.960
<v Speaker 1>Lunch with Pippa Hudson and now Consumer Talk featuring Wendy Nola.

0:00:08.720 --> 0:00:12.040
<v Speaker 1>Wendy joining us via zoom from Johannesburg today, so she's

0:00:12.080 --> 0:00:14.120
<v Speaker 1>up in Koteng for a conference, but glad that you

0:00:14.160 --> 0:00:16.240
<v Speaker 1>were able to step out to join us for this hour.

0:00:16.440 --> 0:00:17.640
<v Speaker 2>Nice to have you with us, Wendy.

0:00:17.960 --> 0:00:20.120
<v Speaker 1>We're going to be picking up on two questions which

0:00:20.120 --> 0:00:22.960
<v Speaker 1>we're posed by listeners during last week's show, and the

0:00:23.000 --> 0:00:25.119
<v Speaker 1>second of them is going to lead us into a

0:00:25.160 --> 0:00:29.200
<v Speaker 1>broader conversation about whether the migration to digital customer service

0:00:29.240 --> 0:00:32.680
<v Speaker 1>platforms is actually perhaps having a negative impact on the

0:00:32.720 --> 0:00:34.160
<v Speaker 1>customer service experience.

0:00:34.479 --> 0:00:35.560
<v Speaker 2>So more on that later.

0:00:35.640 --> 0:00:39.920
<v Speaker 1>We've got some very interesting listener WhatsApps spewing in on

0:00:39.960 --> 0:00:41.760
<v Speaker 1>this subject, and I have to say most of them

0:00:41.880 --> 0:00:45.680
<v Speaker 1>saying how frustrating they find the digital platforms, with one

0:00:45.760 --> 0:00:48.440
<v Speaker 1>or two exceptions. So looking forward to sharing that feedback

0:00:48.479 --> 0:00:51.959
<v Speaker 1>with everybody, and please keep on sharing your view on WhatsApp.

0:00:51.960 --> 0:00:55.480
<v Speaker 1>Oh seven two five six seven one five sixty seven.

0:00:55.680 --> 0:00:58.640
<v Speaker 1>Do you find it convenient and easy to interact with

0:00:58.760 --> 0:01:01.480
<v Speaker 1>a chatbot or an on online form or do you

0:01:01.520 --> 0:01:04.760
<v Speaker 1>prefer talking to a human being or having an email

0:01:04.800 --> 0:01:07.959
<v Speaker 1>where a person will respond to you, for example, what

0:01:08.120 --> 0:01:12.320
<v Speaker 1>has been your experience? Is digital migration helping or hindering

0:01:12.560 --> 0:01:14.040
<v Speaker 1>the customer service experience?

0:01:14.080 --> 0:01:15.759
<v Speaker 2>That is the big question of the afternoon.

0:01:16.160 --> 0:01:18.000
<v Speaker 1>But before we get to that, WHND are we going

0:01:18.040 --> 0:01:20.720
<v Speaker 1>to start with an update on clothing labels, Because towards

0:01:20.760 --> 0:01:23.360
<v Speaker 1>the end of last week's show, Stephanie sent us a

0:01:23.400 --> 0:01:27.080
<v Speaker 1>message asking why isn't it obligatory for South African based

0:01:27.080 --> 0:01:30.120
<v Speaker 1>stores to declare the country of origin on their clothing.

0:01:30.720 --> 0:01:33.840
<v Speaker 1>She said it was an issue across both online stores

0:01:33.880 --> 0:01:37.679
<v Speaker 1>and personal in store experiences, and her point was, I

0:01:37.720 --> 0:01:42.920
<v Speaker 1>want to support local South African made quite clothing.

0:01:42.600 --> 0:01:43.240
<v Speaker 2>For example.

0:01:43.520 --> 0:01:45.920
<v Speaker 1>I want to be able to make an informed choice,

0:01:46.080 --> 0:01:48.040
<v Speaker 1>but it's very hard to do that if they don't

0:01:48.080 --> 0:01:50.800
<v Speaker 1>tell you where the product was made. And her question was,

0:01:50.800 --> 0:01:55.480
<v Speaker 1>are South African retailers, manufacturers, wholesalers and creators not supposed

0:01:55.520 --> 0:01:59.280
<v Speaker 1>to add country of origin to an item's packaging and labeling?

0:02:00.040 --> 0:02:02.040
<v Speaker 1>At the time, you said straight away, I'm great with

0:02:02.080 --> 0:02:04.240
<v Speaker 1>food labels, but I need to do some double checking

0:02:04.240 --> 0:02:06.480
<v Speaker 1>on the subject of clothing labels. Tell us what you

0:02:06.520 --> 0:02:07.000
<v Speaker 1>found out.

0:02:07.560 --> 0:02:10.480
<v Speaker 3>Yes, thanks Papa, So yeah, I was pretty sure it

0:02:10.560 --> 0:02:14.640
<v Speaker 3>was the case, but I don't like to so emphatically

0:02:14.639 --> 0:02:16.360
<v Speaker 3>if I'm not one hundred percent sure. So my first

0:02:16.360 --> 0:02:19.240
<v Speaker 3>port of call was Michael Lawrence, who's the executive director

0:02:19.320 --> 0:02:23.880
<v Speaker 3>of the National Clothing Retail Federation of South Africa. He said, yes,

0:02:23.960 --> 0:02:28.240
<v Speaker 3>labeling is required for products online purchases. Enforcement is a problem,

0:02:28.280 --> 0:02:31.480
<v Speaker 3>but technically an online product can be sent back by

0:02:31.600 --> 0:02:34.639
<v Speaker 3>SARS if picked up that no labels are present at

0:02:34.639 --> 0:02:39.040
<v Speaker 3>the time of inspection. And I think the key there

0:02:39.120 --> 0:02:42.760
<v Speaker 3>is at the time of inspections, because I am I'm

0:02:42.760 --> 0:02:46.480
<v Speaker 3>pretty sure that it's not happening. You know that inspections

0:02:46.639 --> 0:02:49.880
<v Speaker 3>are not happening across the board, so a lot can

0:02:49.919 --> 0:02:53.920
<v Speaker 3>be slipping through. So he directed me to, of course,

0:02:54.200 --> 0:02:57.040
<v Speaker 3>a friend of the show, Lee, Sobriti hused the Consumer

0:02:57.080 --> 0:03:01.800
<v Speaker 3>Goods and Services on Bard, who said, yes, CPA Protection

0:03:01.880 --> 0:03:06.239
<v Speaker 3>Act and its regulations provide very clear requirements for product

0:03:06.320 --> 0:03:10.080
<v Speaker 3>labeling and information to consumers. It's sections twenty two for

0:03:10.160 --> 0:03:13.239
<v Speaker 3>those who are interested of the CPA that requires that

0:03:13.400 --> 0:03:18.760
<v Speaker 3>all information must be presented in play in an unstable

0:03:18.840 --> 0:03:22.360
<v Speaker 3>language so that consumers can make informed choices. That's the

0:03:22.360 --> 0:03:24.600
<v Speaker 3>point of the disclosure, right Pepper. It's always so that

0:03:24.639 --> 0:03:28.839
<v Speaker 3>we go into things knowing everything there is to knowes

0:03:28.880 --> 0:03:31.239
<v Speaker 3>that we can make the right choice for us. Section

0:03:31.320 --> 0:03:35.760
<v Speaker 3>twenty four prohibits false and misleading or deceptive trade descriptions

0:03:36.520 --> 0:03:40.880
<v Speaker 3>and trade description includes details such as country of origin,

0:03:41.080 --> 0:03:45.440
<v Speaker 3>material composition, and mode of manufacture of goods. And then

0:03:45.520 --> 0:03:50.760
<v Speaker 3>also in the regulations of the CPA, there is the

0:03:50.840 --> 0:03:54.640
<v Speaker 3>regulation directs that such descriptions should be applied to goods

0:03:54.800 --> 0:04:00.800
<v Speaker 3>in a conspicuous and legible manner. Understand, it's got to

0:04:00.800 --> 0:04:03.240
<v Speaker 3>have a label on, it's got to have a descriptor.

0:04:03.440 --> 0:04:05.720
<v Speaker 1>And it's got to be in plain, understandable language and

0:04:05.840 --> 0:04:10.880
<v Speaker 1>also quite easy to see in an easy to spot place. Wendy,

0:04:10.920 --> 0:04:12.560
<v Speaker 1>I know you've told us so many times. When it

0:04:12.600 --> 0:04:15.840
<v Speaker 1>comes to online purchases, we don't only look at the CPA,

0:04:16.000 --> 0:04:19.400
<v Speaker 1>We also look at the Electronic Communications and Transactions Act.

0:04:19.760 --> 0:04:22.040
<v Speaker 2>Does that add anything on the subject.

0:04:22.279 --> 0:04:26.840
<v Speaker 3>Yes, so, mbud Lee says Section forty three of the

0:04:26.880 --> 0:04:30.839
<v Speaker 3>ECTA ector as when you call it requires online suppliers

0:04:30.880 --> 0:04:34.080
<v Speaker 3>to disclose the main characteristics of their goods, as well

0:04:34.120 --> 0:04:38.159
<v Speaker 3>as full supplier details and pricing information, again allowing consumers

0:04:38.200 --> 0:04:41.520
<v Speaker 3>to make an informed decision. So, in short, the Umbud

0:04:41.640 --> 0:04:43.880
<v Speaker 3>is clear that when the two ac are considered together

0:04:43.960 --> 0:04:46.880
<v Speaker 3>as they must be, there's a very clear obligation on

0:04:46.920 --> 0:04:51.400
<v Speaker 3>retailers and manufacturers to disclose country of origin clearly and prominently,

0:04:51.680 --> 0:04:53.719
<v Speaker 3>and that the same level of detail and description would

0:04:53.720 --> 0:04:57.640
<v Speaker 3>apply to both, you know, a physical store situation and

0:04:57.680 --> 0:05:00.720
<v Speaker 3>the online shopping environment. Bearing my and that when the

0:05:00.760 --> 0:05:04.120
<v Speaker 3>Act came into being in all that was draught up

0:05:04.120 --> 0:05:06.599
<v Speaker 3>as a two thousand and eight, it came into fourth

0:05:06.640 --> 0:05:10.400
<v Speaker 3>and twenty eleven, online shopping wasn't what it is today,

0:05:10.600 --> 0:05:12.480
<v Speaker 3>and so I think we woul have seen a lot

0:05:12.520 --> 0:05:14.400
<v Speaker 3>more detail around that if the Act had to come

0:05:14.440 --> 0:05:17.279
<v Speaker 3>out you know today or in the last I say,

0:05:17.320 --> 0:05:18.160
<v Speaker 3>post COVID era.

0:05:18.320 --> 0:05:19.040
<v Speaker 2>Yeah.

0:05:19.160 --> 0:05:21.680
<v Speaker 1>So in summary, Stephanie's right to be looking forward and

0:05:21.680 --> 0:05:23.960
<v Speaker 1>she has every right to expect to see that at

0:05:24.000 --> 0:05:26.760
<v Speaker 1>this disclosure on the label. Final question before we leave

0:05:26.800 --> 0:05:28.880
<v Speaker 1>this topic, Wendy, is if it's not there, what's the

0:05:28.880 --> 0:05:29.640
<v Speaker 1>correct thing to do?

0:05:29.640 --> 0:05:31.880
<v Speaker 2>Do you report the retailer to the ombit? What do

0:05:31.920 --> 0:05:32.200
<v Speaker 2>you do?

0:05:33.400 --> 0:05:37.320
<v Speaker 3>Yes? Absolutely, And I mean if you're very sure about

0:05:37.360 --> 0:05:39.520
<v Speaker 3>your facts as well, you could put it on social

0:05:39.560 --> 0:05:45.320
<v Speaker 3>media because I think we need to, you know, we

0:05:45.400 --> 0:05:47.560
<v Speaker 3>need this to be top of mind for consumers to

0:05:47.600 --> 0:05:49.359
<v Speaker 3>know to look for it and go, well, it should

0:05:49.400 --> 0:05:51.600
<v Speaker 3>be here. I don't know where this garment is made up,

0:05:52.200 --> 0:05:57.480
<v Speaker 3>preferred to, you know, locally made or I don't mind important,

0:05:57.480 --> 0:05:59.400
<v Speaker 3>but I don't want from X company. We have the

0:05:59.480 --> 0:06:02.000
<v Speaker 3>right to know things when we're putting our money stuff.

0:06:02.040 --> 0:06:05.120
<v Speaker 3>So I think it's a good conversation to be had. Yes,

0:06:05.200 --> 0:06:07.760
<v Speaker 3>go to the umbut, go to the supply as well,

0:06:08.320 --> 0:06:10.440
<v Speaker 3>and then put it out on social media and remembering,

0:06:10.480 --> 0:06:14.760
<v Speaker 3>of course you've if it's not a hundred percent truon

0:06:14.800 --> 0:06:17.599
<v Speaker 3>in the public interest, it's opening yourself up for a

0:06:17.640 --> 0:06:20.320
<v Speaker 3>defamation claim, so make sure it's always.

0:06:20.080 --> 0:06:23.160
<v Speaker 1>Such a fast Okay, thanks for that, and thanks Stephanie

0:06:23.160 --> 0:06:26.800
<v Speaker 1>for raising an important topic. Now, the second subject, the

0:06:27.000 --> 0:06:29.560
<v Speaker 1>question that came through last week, is one that's going

0:06:29.600 --> 0:06:31.360
<v Speaker 1>to sort of lead us nudge us in the direction

0:06:31.440 --> 0:06:35.440
<v Speaker 1>of the main talking point around customer service and digital channels.

0:06:35.960 --> 0:06:38.960
<v Speaker 1>Last week we read out Zuki's query on air. Zuki

0:06:39.000 --> 0:06:41.320
<v Speaker 1>Makuzeni writing in to say, I am registered on the

0:06:41.320 --> 0:06:45.120
<v Speaker 1>clicks website for online shopping. Recently, when trying to log

0:06:45.160 --> 0:06:48.960
<v Speaker 1>onto my account, the site has required verification of one's

0:06:49.240 --> 0:06:52.960
<v Speaker 1>mobile phone number, which Zuki says is a perfectly understandable

0:06:52.960 --> 0:06:55.720
<v Speaker 1>security measure. She's quite happy to go along with it,

0:06:55.800 --> 0:06:58.479
<v Speaker 1>So get your one time pin and enter that to continue,

0:06:58.680 --> 0:07:01.159
<v Speaker 1>But she says her difficulty is been I can't receive

0:07:01.240 --> 0:07:04.279
<v Speaker 1>the one time pin on my registered number. When I

0:07:04.320 --> 0:07:07.200
<v Speaker 1>looked into why this was happening, Clicks told me that

0:07:07.279 --> 0:07:10.120
<v Speaker 1>the OTP can't be received if one is registered on

0:07:10.200 --> 0:07:13.480
<v Speaker 1>the Wasper do not Contact list and just reminded to

0:07:13.520 --> 0:07:15.560
<v Speaker 1>listeners that is the place where you go and register

0:07:15.680 --> 0:07:18.600
<v Speaker 1>that you do not want to be contacted with unwanted

0:07:18.640 --> 0:07:22.120
<v Speaker 1>marketing and unsolicited marketing, etc. So Zuki says, I'm on

0:07:22.160 --> 0:07:24.960
<v Speaker 1>that list because I don't want to receive unsolicited marketing.

0:07:25.200 --> 0:07:27.440
<v Speaker 1>But the only way for me to keep purchasing through

0:07:27.440 --> 0:07:30.400
<v Speaker 1>my online account was either to take myself off that

0:07:30.520 --> 0:07:33.520
<v Speaker 1>list or to provide an alternative cell phone number, which

0:07:33.600 --> 0:07:36.360
<v Speaker 1>wasn't on the list. Now, in Zuki's case, thankfully there

0:07:36.400 --> 0:07:38.200
<v Speaker 1>was a second phone available she could give them the

0:07:38.240 --> 0:07:41.480
<v Speaker 1>alternative number. But her point is it doesn't seem right

0:07:41.520 --> 0:07:44.240
<v Speaker 1>for a retailer to force one to de register from

0:07:44.360 --> 0:07:47.120
<v Speaker 1>Wasper in order to have an account on their site.

0:07:47.560 --> 0:07:50.760
<v Speaker 1>We have very good reason to register with WASPA. After all,

0:07:51.360 --> 0:07:53.560
<v Speaker 1>were you aware of this? I think clicks should found

0:07:53.720 --> 0:07:57.160
<v Speaker 1>find a better solution, was her comment. Zuki also a

0:07:57.280 --> 0:08:00.000
<v Speaker 1>very significant question, thank you, and when do you reach

0:08:00.080 --> 0:08:00.760
<v Speaker 1>start to Clicks?

0:08:00.800 --> 0:08:01.920
<v Speaker 2>What did they tell you?

0:08:02.440 --> 0:08:04.680
<v Speaker 3>I Dare said, I'll put it to them that there

0:08:04.920 --> 0:08:08.320
<v Speaker 3>has to be a way to avoid this unfortunate situation,

0:08:08.560 --> 0:08:10.960
<v Speaker 3>or many of us would not receive the one time

0:08:11.000 --> 0:08:14.360
<v Speaker 3>pins that our banks send us via SMEs fourth centification

0:08:14.440 --> 0:08:17.280
<v Speaker 3>wouldn't be able to make any purchases. So I said

0:08:17.280 --> 0:08:20.520
<v Speaker 3>there has to be a technical solution, and their response

0:08:20.840 --> 0:08:24.000
<v Speaker 3>was yes. Clicks is implemented a solution to ensure that

0:08:24.040 --> 0:08:28.120
<v Speaker 3>customers can receive their OTP via SMS even if they

0:08:28.160 --> 0:08:32.439
<v Speaker 3>are registered on the Wasper do not contact list. This

0:08:32.559 --> 0:08:36.920
<v Speaker 3>update was implemented on the seventeenth of October, ensuring that

0:08:36.960 --> 0:08:42.560
<v Speaker 3>all customers can complete their verification processes without issue. You know,

0:08:42.840 --> 0:08:46.080
<v Speaker 3>we'll provide any additional information if needed. So it sounds

0:08:46.120 --> 0:08:49.680
<v Speaker 3>to me as if they this was an unintended consequence

0:08:49.679 --> 0:08:50.240
<v Speaker 3>obviously that.

0:08:53.200 --> 0:08:56.480
<v Speaker 2>Oh yeah, we see it, and we seem to be

0:08:56.600 --> 0:08:59.480
<v Speaker 2>having some difficulties. Okay, Wendy, thanks for that.

0:08:59.520 --> 0:09:01.680
<v Speaker 1>Sorry, we just lost your signal for a second there,

0:09:01.720 --> 0:09:05.360
<v Speaker 1>but just to recap again, the issue has been sorted out,

0:09:05.400 --> 0:09:08.559
<v Speaker 1>so Zuki, thanks for bringing it to our attention and

0:09:08.600 --> 0:09:10.199
<v Speaker 1>to their attention. I don't know if it was your

0:09:10.200 --> 0:09:13.079
<v Speaker 1>complaint or probably many other people with the same issue

0:09:13.480 --> 0:09:16.000
<v Speaker 1>flagging the fact that it was a problem. Whatever it was,

0:09:16.200 --> 0:09:18.160
<v Speaker 1>they have found a work around and it shouldn't be

0:09:18.160 --> 0:09:19.880
<v Speaker 1>an issue going forward, So thank you for that.

0:09:20.640 --> 0:09:21.000
<v Speaker 2>Okay.

0:09:21.080 --> 0:09:24.480
<v Speaker 1>So that segues neatly wendy into the other digital service

0:09:24.520 --> 0:09:26.240
<v Speaker 1>issue we want to talk about today, and this is

0:09:26.240 --> 0:09:30.800
<v Speaker 1>the question of whether migrating onto digital and AI platforms

0:09:30.880 --> 0:09:34.160
<v Speaker 1>is actually making it harder for customers to engage with

0:09:34.240 --> 0:09:38.000
<v Speaker 1>businesses and particularly to receive help when something has gone wrong.

0:09:38.559 --> 0:09:40.840
<v Speaker 1>As a matter of interest, is that something customers complain

0:09:40.920 --> 0:09:42.600
<v Speaker 1>to you about often or not?

0:09:45.640 --> 0:09:48.640
<v Speaker 3>Yes, it is a common theme. They won't complain to

0:09:48.760 --> 0:09:51.960
<v Speaker 3>me directly about that, it'd be about an issue they had,

0:09:51.960 --> 0:09:57.200
<v Speaker 3>and then it becomes a catalog of the annoyances the

0:09:57.200 --> 0:10:00.720
<v Speaker 3>frustrations they experienced in trying to raise with the company,

0:10:00.720 --> 0:10:02.240
<v Speaker 3>which is often why are they write to me in

0:10:02.240 --> 0:10:05.199
<v Speaker 3>the first place, Because they couldn't get anywhere in engaging

0:10:05.240 --> 0:10:08.800
<v Speaker 3>with the company that they do business with and via

0:10:08.920 --> 0:10:11.880
<v Speaker 3>the channels that that company has chosen to put in

0:10:11.920 --> 0:10:13.560
<v Speaker 3>place for them. So that's why they come to me.

0:10:13.679 --> 0:10:18.280
<v Speaker 3>So it's actually a very significant consumer issue. And it

0:10:18.320 --> 0:10:20.720
<v Speaker 3>occurs to me that if companies did a better job

0:10:20.880 --> 0:10:24.680
<v Speaker 3>of making them selves accessible to their customers, that you know,

0:10:24.760 --> 0:10:27.120
<v Speaker 3>I would have a much smaller inbox. Yeah.

0:10:27.200 --> 0:10:31.240
<v Speaker 1>Yeah, So I had a recent experience that was a

0:10:31.240 --> 0:10:33.000
<v Speaker 1>good example of this, and we're going to share it

0:10:33.040 --> 0:10:35.720
<v Speaker 1>with today. And I don't want to emphasize this. The

0:10:35.800 --> 0:10:38.559
<v Speaker 1>problem at the crux of this matter has been resolved

0:10:38.600 --> 0:10:41.240
<v Speaker 1>and is not an issue. What it is interesting to

0:10:41.280 --> 0:10:44.400
<v Speaker 1>me is how it demonstrates this question of making yourself

0:10:44.440 --> 0:10:47.440
<v Speaker 1>accessible to the customer. And when I mentioned it to Wendy,

0:10:47.480 --> 0:10:49.560
<v Speaker 1>she said, thank you, please send me a summary. I

0:10:49.559 --> 0:10:51.680
<v Speaker 1>want to take this up with Discovery Healthy, where the

0:10:51.720 --> 0:10:55.480
<v Speaker 1>service provider in question. Kind of long story short I

0:10:55.520 --> 0:10:58.439
<v Speaker 1>recently had I received this claim statement for Discovery, opened

0:10:58.480 --> 0:11:02.320
<v Speaker 1>it up to find a very large pharmacy order that

0:11:02.360 --> 0:11:04.920
<v Speaker 1>Discovery had paid straight to the pharmacy and I went, well,

0:11:04.960 --> 0:11:07.679
<v Speaker 1>hang on a second, I never received that order. So

0:11:07.720 --> 0:11:10.000
<v Speaker 1>you've paid close to one in half thousand rand for

0:11:10.080 --> 0:11:12.880
<v Speaker 1>drugs that were never dispensed to me, and I wasn't

0:11:12.880 --> 0:11:15.000
<v Speaker 1>sure if this was a fraudulent claim or if it

0:11:15.160 --> 0:11:18.520
<v Speaker 1>was an error. But my first thought, Wendy, was I

0:11:18.520 --> 0:11:20.680
<v Speaker 1>need to let Discovery know straight away that there's a

0:11:20.720 --> 0:11:23.600
<v Speaker 1>problem with this claim because they have paid it out

0:11:23.640 --> 0:11:26.240
<v Speaker 1>of their chronic illness benefit.

0:11:26.840 --> 0:11:29.160
<v Speaker 2>It's their immediate loss. Let me flag it straight away.

0:11:29.360 --> 0:11:32.440
<v Speaker 1>And that is where my run around began, because I

0:11:32.520 --> 0:11:36.160
<v Speaker 1>first tried calling the customer helpline. After being on hold

0:11:36.200 --> 0:11:38.360
<v Speaker 1>for more than ten minutes, I eventually gave up and

0:11:38.400 --> 0:11:40.920
<v Speaker 1>then went to the website trying to find an email

0:11:41.240 --> 0:11:45.800
<v Speaker 1>where I could send a query. Everything on the website,

0:11:45.840 --> 0:11:48.079
<v Speaker 1>everything on the website was pushing me to the online

0:11:48.960 --> 0:11:52.400
<v Speaker 1>Complaints and Compliments for so I tried to use that,

0:11:52.880 --> 0:11:54.720
<v Speaker 1>but I couldn't get that form to load. It just

0:11:54.720 --> 0:11:57.520
<v Speaker 1>got stuck in an endless loop of please click here

0:11:57.559 --> 0:12:00.480
<v Speaker 1>to populate the form, please click here, and it just

0:12:00.600 --> 0:12:02.880
<v Speaker 1>kept on going back to the same place without ever

0:12:02.920 --> 0:12:07.840
<v Speaker 1>offering me the form. So I then tried the chatbot

0:12:08.080 --> 0:12:09.280
<v Speaker 1>and asked the chatbot can you.

0:12:09.240 --> 0:12:10.760
<v Speaker 2>Please give me an email address?

0:12:11.400 --> 0:12:13.720
<v Speaker 1>The chatbot wanted to push me back to the online

0:12:13.720 --> 0:12:18.280
<v Speaker 1>form instead, so I thenually found please let me speak

0:12:18.320 --> 0:12:22.560
<v Speaker 1>to an agent option within the sort of chatbot WhatsApp

0:12:22.600 --> 0:12:25.800
<v Speaker 1>line function, and eventually got to a human agent on

0:12:25.840 --> 0:12:27.800
<v Speaker 1>the other side and asked it the same question, Can

0:12:27.800 --> 0:12:29.520
<v Speaker 1>you please give me an email address where I.

0:12:29.520 --> 0:12:32.800
<v Speaker 2>Can send you send this statement and flag the fact

0:12:32.800 --> 0:12:33.559
<v Speaker 2>that it's a problem.

0:12:34.000 --> 0:12:36.800
<v Speaker 1>So yeah, and she gave me an address, which I

0:12:36.920 --> 0:12:39.880
<v Speaker 1>then duly used. It immediately bounced back saying this email

0:12:39.920 --> 0:12:43.200
<v Speaker 1>is undeliverable. So I went back into the chat thankfully

0:12:43.240 --> 0:12:45.000
<v Speaker 1>she was still online, said can you please give me

0:12:45.000 --> 0:12:47.680
<v Speaker 1>an alternative email address? And it was at that point

0:12:47.920 --> 0:12:51.160
<v Speaker 1>that this took an interesting turn. She says, we've gone digital.

0:12:51.440 --> 0:12:55.320
<v Speaker 1>We don't do email anymore, and you guessed it. She

0:12:55.360 --> 0:12:58.560
<v Speaker 1>directed me to use the online form, and when I

0:12:58.559 --> 0:13:00.760
<v Speaker 1>explained to her, look, that form is not working for me.

0:13:01.360 --> 0:13:03.680
<v Speaker 1>Plus I would like to do email rather because I

0:13:03.679 --> 0:13:05.520
<v Speaker 1>would like to be able to keep a record of

0:13:05.559 --> 0:13:07.840
<v Speaker 1>what I have sent on which date to hurry, etc.

0:13:09.160 --> 0:13:12.560
<v Speaker 1>Got a very indifferent response. So anyway, long story short,

0:13:12.600 --> 0:13:14.880
<v Speaker 1>I did eventually get that form to load, I filled

0:13:14.880 --> 0:13:17.920
<v Speaker 1>it out, I hit send, and the screen went blank.

0:13:18.000 --> 0:13:20.240
<v Speaker 1>The form contents disappeared, There was no record of it

0:13:20.280 --> 0:13:22.720
<v Speaker 1>being delivered. There was no reference number or anything like that.

0:13:23.240 --> 0:13:26.120
<v Speaker 1>So in the end, I went back into my inbox

0:13:26.240 --> 0:13:29.480
<v Speaker 1>and searched for every Discovery email address I'd ever used

0:13:29.520 --> 0:13:33.160
<v Speaker 1>over the years, and eventually, after trying and getting this

0:13:33.840 --> 0:13:38.720
<v Speaker 1>undeliverable response from about fifteen different attempts, Forensics A Discovery

0:13:38.800 --> 0:13:40.840
<v Speaker 1>got through and Wendy, I have to say that the

0:13:40.920 --> 0:13:43.960
<v Speaker 1>query was resolved quickly. They sent an auto response saying

0:13:44.000 --> 0:13:47.240
<v Speaker 1>we've received your query, and within two or three days

0:13:47.240 --> 0:13:49.680
<v Speaker 1>I received a response saying we've looked into it, the

0:13:49.720 --> 0:13:52.280
<v Speaker 1>issue has been resolved, the claim has been reversed.

0:13:52.720 --> 0:13:57.280
<v Speaker 2>Thanks very much. The final yeap, Sorry, go for it.

0:13:57.360 --> 0:14:00.520
<v Speaker 3>Yes, I was gonna say, I think you should repeat

0:14:00.600 --> 0:14:02.439
<v Speaker 3>that for the benefit of our listeners who might be

0:14:02.440 --> 0:14:04.600
<v Speaker 3>in the same situation. There is one email that works

0:14:04.600 --> 0:14:05.800
<v Speaker 3>if we have a similar complaint.

0:14:05.880 --> 0:14:06.760
<v Speaker 2>Okay, so the one.

0:14:06.640 --> 0:14:10.720
<v Speaker 1>Still working email is Forensics at Discovery dot co dot ZDA.

0:14:11.160 --> 0:14:14.480
<v Speaker 2>But I mean, I mean, it really was a nine.

0:14:14.840 --> 0:14:16.960
<v Speaker 1>I spent about an hour and a half Wendy trying

0:14:17.000 --> 0:14:20.200
<v Speaker 1>to flag what one would think would be a quite

0:14:20.280 --> 0:14:20.920
<v Speaker 1>easy to.

0:14:21.240 --> 0:14:22.760
<v Speaker 2>Do things, so nineteen minutes.

0:14:23.120 --> 0:14:25.360
<v Speaker 1>And then the cherry on top was when yesterday I

0:14:25.480 --> 0:14:29.760
<v Speaker 1>received an email from Discovery saying you recently interacted with

0:14:29.840 --> 0:14:32.320
<v Speaker 1>our agent who sent you a follow up please will

0:14:32.320 --> 0:14:35.560
<v Speaker 1>you rate our service? And I hit the star rating

0:14:35.640 --> 0:14:39.320
<v Speaker 1>to give the rating and it went, sorry, something went wrong,

0:14:39.960 --> 0:14:43.920
<v Speaker 1>we can't receive you're rating, And that kind of summed

0:14:44.000 --> 0:14:45.200
<v Speaker 1>up for me where we're at that.

0:14:45.280 --> 0:14:47.240
<v Speaker 3>I didn't even share that with Discovery.

0:14:47.360 --> 0:14:48.480
<v Speaker 2>No, that was just that.

0:14:48.560 --> 0:14:50.720
<v Speaker 1>I mean, that was after the fact, but it was

0:14:50.800 --> 0:14:54.200
<v Speaker 1>quite a demonstration of where things are going wrong that

0:14:54.280 --> 0:14:56.960
<v Speaker 1>you get stuck in this endless loop trying to channel

0:14:57.040 --> 0:15:01.200
<v Speaker 1>you to a non human platform and after nineteen minutes

0:15:01.240 --> 0:15:04.000
<v Speaker 1>what should have been a fairly simple thing to resolve

0:15:04.040 --> 0:15:05.960
<v Speaker 1>to say, hey, I need to stick up a red flag.

0:15:06.000 --> 0:15:08.960
<v Speaker 1>Somebody needs to look at this claim because something is wrong.

0:15:10.120 --> 0:15:12.800
<v Speaker 1>Couldn't be done. And I'm looking at the clock and

0:15:12.800 --> 0:15:15.000
<v Speaker 1>seeing that we're marching towards hop us too. So we

0:15:15.120 --> 0:15:18.680
<v Speaker 1>will obviously feedback to you what Discovery has said when

0:15:18.720 --> 0:15:22.440
<v Speaker 1>engaging with Wendy on this. But it's not the Discovery

0:15:22.480 --> 0:15:24.280
<v Speaker 1>service issue I want to talk about today. It's this

0:15:24.440 --> 0:15:28.720
<v Speaker 1>question of whether digital migration of the customer service function

0:15:28.920 --> 0:15:32.360
<v Speaker 1>is actually doing companies a disservice and in the end,

0:15:32.680 --> 0:15:36.400
<v Speaker 1>eroding the level of customer service I see lots of

0:15:36.400 --> 0:15:39.280
<v Speaker 1>WhatsApps coming in responding, so we'll share those and we'll

0:15:39.280 --> 0:15:40.480
<v Speaker 1>share Discovery's response.

0:15:41.760 --> 0:15:45.960
<v Speaker 2>Join the conversation. Join the conversation you're with Kate Talk.

0:15:47.880 --> 0:15:50.360
<v Speaker 1>We're back with Wendy Nola joining us by a zoom

0:15:50.400 --> 0:15:53.800
<v Speaker 1>this afternoon, and before we share Discoveries feedback, I just

0:15:53.840 --> 0:15:55.520
<v Speaker 1>want to share some of the listener questions that have

0:15:55.600 --> 0:15:58.400
<v Speaker 1>come in, rather WhatsApps that have come in. Wendy, I've

0:15:58.440 --> 0:16:00.000
<v Speaker 1>been asking since the beginning of the show, do you

0:16:00.160 --> 0:16:03.840
<v Speaker 1>prefer do you find the digital platforms helpful? Do you

0:16:03.840 --> 0:16:06.480
<v Speaker 1>prefer interacting with those or do you prefer speaking to

0:16:06.520 --> 0:16:10.000
<v Speaker 1>a human being? And a couple of running themes and Jenny,

0:16:10.000 --> 0:16:12.600
<v Speaker 1>I completely agree with you, she says, I found that

0:16:12.640 --> 0:16:16.440
<v Speaker 1>digital platforms are useful when you just need statements or tax.

0:16:16.320 --> 0:16:17.160
<v Speaker 2>Certificates, etc.

0:16:17.800 --> 0:16:20.640
<v Speaker 1>But if it's a more complicated query, you need to

0:16:20.720 --> 0:16:23.760
<v Speaker 1>speak to a person. Sometimes when talking to the bot,

0:16:23.800 --> 0:16:26.120
<v Speaker 1>they don't understand you. You waste a lot of time

0:16:26.440 --> 0:16:29.840
<v Speaker 1>trying to rephrase your question until you just give up.

0:16:30.760 --> 0:16:34.760
<v Speaker 1>Similar comment from Andy saying customer service via digital is

0:16:34.800 --> 0:16:38.160
<v Speaker 1>nonexistent in my experience. I have yet to have a

0:16:38.160 --> 0:16:41.160
<v Speaker 1>re query resolved via WhatsApp. I feel it's just a

0:16:41.200 --> 0:16:45.480
<v Speaker 1>way to avoid interacting with customers, very frustrating, and it

0:16:45.520 --> 0:16:49.240
<v Speaker 1>doesn't work. Karen saying, I definitely prefer speaking to a human.

0:16:49.320 --> 0:16:53.040
<v Speaker 1>I find the chatbot or digital process more time consuming

0:16:53.320 --> 0:16:56.880
<v Speaker 1>and definitely more frustrating. And then a very interesting perspective

0:16:56.920 --> 0:17:00.880
<v Speaker 1>from Alice saying I'm located in the EU. Online chat

0:17:00.920 --> 0:17:05.080
<v Speaker 1>customer service here is mostly staffed by real people. As

0:17:05.080 --> 0:17:07.439
<v Speaker 1>soon as I see a brand that is only using

0:17:07.520 --> 0:17:10.760
<v Speaker 1>AI bots for customer service, I will ditch that brand

0:17:11.160 --> 0:17:13.399
<v Speaker 1>and never buy from them again, even if I have

0:17:13.480 --> 0:17:16.160
<v Speaker 1>to pay more to switch. So Alice very firmly saying

0:17:16.200 --> 0:17:19.280
<v Speaker 1>I will not support your brand if all you offer

0:17:19.320 --> 0:17:23.159
<v Speaker 1>me is an AI bot and Wendy. One of the

0:17:23.160 --> 0:17:24.879
<v Speaker 1>things I said to you when I summarized all of

0:17:24.880 --> 0:17:28.920
<v Speaker 1>this in my email was I'm not quite fifty years old.

0:17:28.920 --> 0:17:32.480
<v Speaker 1>I consider myself relatively tech savvy. I'm used to engageing

0:17:32.560 --> 0:17:34.960
<v Speaker 1>with online platforms. I do so all the time. I

0:17:35.000 --> 0:17:38.359
<v Speaker 1>produce content for online platforms. If I found it that

0:17:38.640 --> 0:17:43.560
<v Speaker 1>difficult to get through to some sort of resolution, imagine

0:17:43.560 --> 0:17:45.919
<v Speaker 1>what it is like for an elderly customer who is

0:17:46.000 --> 0:17:50.200
<v Speaker 1>not all fair with these platforms, and especially when you're

0:17:50.200 --> 0:17:52.960
<v Speaker 1>dealing with something like a medical aid, elderly customers are

0:17:53.000 --> 0:17:55.639
<v Speaker 1>going to make up a lot of their complainants by default.

0:17:56.160 --> 0:18:00.560
<v Speaker 1>Surely we should be doing better to offer them something. Really,

0:18:00.640 --> 0:18:03.000
<v Speaker 1>I love the email that's just come in from someone

0:18:03.040 --> 0:18:06.040
<v Speaker 1>who's asked to remain anonymous, and that's absolutely fine, but

0:18:06.200 --> 0:18:09.000
<v Speaker 1>listen to this. I work as a financial advisor.

0:18:09.040 --> 0:18:09.399
<v Speaker 2>They're right.

0:18:09.560 --> 0:18:13.200
<v Speaker 1>Our business has been moving quite swiftly towards digital channels.

0:18:13.560 --> 0:18:16.800
<v Speaker 1>Although I embrace the digital age, it is very sad

0:18:16.840 --> 0:18:20.000
<v Speaker 1>how companies ignore our elderly, many of whom are not

0:18:20.200 --> 0:18:23.240
<v Speaker 1>as tech savvy. When I have to issue a policy

0:18:23.400 --> 0:18:26.560
<v Speaker 1>or update an existing one, I prefer to jump into

0:18:26.600 --> 0:18:29.840
<v Speaker 1>my car to see the client face to face, rather

0:18:29.920 --> 0:18:31.600
<v Speaker 1>than tell them that I'm going to send them a

0:18:31.600 --> 0:18:35.760
<v Speaker 1>document to sign via electronic signature, for example. There needs

0:18:35.800 --> 0:18:38.840
<v Speaker 1>to be a better way to service all customers by

0:18:39.040 --> 0:18:42.000
<v Speaker 1>various means, and for the client to select the option

0:18:42.240 --> 0:18:44.320
<v Speaker 1>they prefer to do their business.

0:18:44.720 --> 0:18:47.080
<v Speaker 2>And I mean, I wish there were more people like

0:18:47.119 --> 0:18:49.080
<v Speaker 2>you prepared to go the extra mile like that. But

0:18:49.160 --> 0:18:52.080
<v Speaker 2>thank you. I think that says so much of importance, Wendy.

0:18:53.400 --> 0:18:57.119
<v Speaker 3>And also I mean I look at the case is

0:18:57.160 --> 0:19:01.920
<v Speaker 3>the complaints that the phase onward that regulates, yeah, considers

0:19:01.920 --> 0:19:06.679
<v Speaker 3>complaints around brokers, and and the is very tough on

0:19:07.200 --> 0:19:11.840
<v Speaker 3>brokers that you know, are just forwarding stuff by email

0:19:11.920 --> 0:19:13.719
<v Speaker 3>or whatever. If there's a key change on the policy,

0:19:13.840 --> 0:19:16.000
<v Speaker 3>like you didn't need a tracking device, now you need one,

0:19:16.240 --> 0:19:18.720
<v Speaker 3>and they're not making the call or putting at the

0:19:18.720 --> 0:19:20.800
<v Speaker 3>top of the email. Please note this is not just

0:19:21.160 --> 0:19:24.359
<v Speaker 3>the normal, normal increase in your fees. You must you

0:19:24.440 --> 0:19:26.840
<v Speaker 3>now need a tracking device or whatever. And if they

0:19:27.520 --> 0:19:33.479
<v Speaker 3>if they don't fulfilled mandate in terms of the you know,

0:19:33.600 --> 0:19:36.600
<v Speaker 3>what they're required to do as as financial advisors, then

0:19:36.920 --> 0:19:40.560
<v Speaker 3>the decisions go against them, and that the you know,

0:19:40.960 --> 0:19:43.720
<v Speaker 3>in the one case it was exactly this tracking thing,

0:19:43.760 --> 0:19:46.760
<v Speaker 3>the broke to pay half the loss and the customer

0:19:47.800 --> 0:19:50.280
<v Speaker 3>pay the other because you should have read the email.

0:19:50.320 --> 0:19:54.360
<v Speaker 3>But what I'm saying is they're in that I love

0:19:54.440 --> 0:19:57.639
<v Speaker 3>that email. But she will know that, you know, there

0:19:57.680 --> 0:20:00.320
<v Speaker 3>will be many of her colleagues who are not doing

0:20:00.400 --> 0:20:02.120
<v Speaker 3>enough to make sure there was a meeting of the mind,

0:20:02.119 --> 0:20:05.399
<v Speaker 3>who are not servicing their customers in the way that

0:20:05.640 --> 0:20:09.199
<v Speaker 3>works for them. So in this country, in particular, I

0:20:09.240 --> 0:20:12.440
<v Speaker 3>think we've got the elderly, and then we've got people

0:20:12.440 --> 0:20:16.199
<v Speaker 3>who just haven't got onto the digital train, and I

0:20:16.280 --> 0:20:19.480
<v Speaker 3>mean or you know, totally alienated. So yeah, I love

0:20:19.560 --> 0:20:23.520
<v Speaker 3>this topic. As you can probably tell, I did engage

0:20:23.520 --> 0:20:27.399
<v Speaker 3>with Discovery. I sent the missity of your case and

0:20:27.480 --> 0:20:30.159
<v Speaker 3>I asked a number of questions such as, what is

0:20:30.560 --> 0:20:33.440
<v Speaker 3>the company's position on emails a means of members being

0:20:33.440 --> 0:20:37.119
<v Speaker 3>able to engage with the scheme, When did that policy change?

0:20:37.160 --> 0:20:40.840
<v Speaker 3>And how were members informed? Why the long wait on

0:20:40.880 --> 0:20:45.320
<v Speaker 3>the phone option, you know, is ten minutes plus considered

0:20:45.320 --> 0:20:48.680
<v Speaker 3>an acceptable wait time? What's the issue with the online

0:20:48.840 --> 0:20:52.159
<v Speaker 3>form not loading and submitting? And then I said, you

0:20:52.160 --> 0:20:55.520
<v Speaker 3>know of particular interest to me, was your comment, Pippa

0:20:55.600 --> 0:20:58.520
<v Speaker 3>that because it's something I feel very strongly about. Those

0:20:58.600 --> 0:21:02.159
<v Speaker 3>online forms. Routinely take photos before I sent, but a

0:21:02.200 --> 0:21:04.120
<v Speaker 3>lot of people won't think to do it, and then

0:21:04.200 --> 0:21:08.280
<v Speaker 3>you're left without your own record of what you said

0:21:08.320 --> 0:21:10.840
<v Speaker 3>and when and who you sent it to, as you

0:21:10.840 --> 0:21:13.239
<v Speaker 3>would in the case of a normal email. So I

0:21:13.320 --> 0:21:16.520
<v Speaker 3>just think that that's quite disadvantage.

0:21:16.640 --> 0:21:17.480
<v Speaker 2>That's quite.

0:21:18.800 --> 0:21:22.720
<v Speaker 3>But judicial is the word I looking to consumers them anyways,

0:21:24.400 --> 0:21:27.240
<v Speaker 3>And yeah, as you put it, And then she said

0:21:27.320 --> 0:21:32.119
<v Speaker 3>and then you also said, and as for the chat box,

0:21:32.280 --> 0:21:35.280
<v Speaker 3>you went back onto the chato and that correspondence with

0:21:35.320 --> 0:21:38.200
<v Speaker 3>the agent is gone, that history is gone. You said,

0:21:38.240 --> 0:21:40.240
<v Speaker 3>I'd hope to quote her directly so that you could

0:21:40.240 --> 0:21:43.280
<v Speaker 3>see what I mean about the indifferent attitude. But now

0:21:43.320 --> 0:21:46.160
<v Speaker 3>there's no record of that conversation ever happening. And I'm

0:21:46.160 --> 0:21:49.200
<v Speaker 3>not going to be convinced that is that isn't part

0:21:49.240 --> 0:21:53.640
<v Speaker 3>of the intended outcome with both email and chat boxes,

0:21:54.119 --> 0:21:56.200
<v Speaker 3>and I think that's, as I say, I have a

0:21:56.280 --> 0:22:01.560
<v Speaker 3>very dim view of that. So, yeah, we're told that

0:22:01.560 --> 0:22:03.480
<v Speaker 3>they weren't going to be able to get us a

0:22:03.840 --> 0:22:06.880
<v Speaker 3>response in time, but happily, just in the nick of time,

0:22:07.280 --> 0:22:12.399
<v Speaker 3>we've got quite a comprehensive response to some of those issues.

0:22:14.119 --> 0:22:15.480
<v Speaker 2>Do you want me to read one of them?

0:22:15.560 --> 0:22:17.920
<v Speaker 1>Yeah, So, I mean, okay, I'm going to leave out

0:22:17.960 --> 0:22:21.040
<v Speaker 1>the stuff of that relates to the actual dispute itself, which,

0:22:21.200 --> 0:22:24.000
<v Speaker 1>as I said, has been resolved. So I'm not questioning

0:22:24.040 --> 0:22:27.439
<v Speaker 1>that it has been sorted out. But a couple of

0:22:27.440 --> 0:22:30.640
<v Speaker 1>the things and we are receiving here input from Karen Sanderson,

0:22:30.720 --> 0:22:36.040
<v Speaker 1>chief operating Officer of Discovery Health. Okay, firstly, the feedback

0:22:36.040 --> 0:22:39.160
<v Speaker 1>on the call center. Accessibility is important to US. Discovery

0:22:39.160 --> 0:22:42.840
<v Speaker 1>Health meets its service target of answering sixty percent of

0:22:42.920 --> 0:22:48.120
<v Speaker 1>calls within sety seconds, ensuring most members connect promptly with consultants.

0:22:48.440 --> 0:22:51.600
<v Speaker 1>While wait times can extend during peak periods, our data

0:22:51.640 --> 0:22:55.119
<v Speaker 1>confirms that the majority of calls are answered within agreed

0:22:55.200 --> 0:22:58.640
<v Speaker 1>time frames. That said, we are continually working to improve

0:22:58.760 --> 0:23:01.480
<v Speaker 1>accessibility across all our channels.

0:23:02.160 --> 0:23:03.720
<v Speaker 2>I want to just insert there.

0:23:03.760 --> 0:23:08.120
<v Speaker 1>I wonder how they monitor that answering of the call,

0:23:08.160 --> 0:23:10.640
<v Speaker 1>because the call is answered immediately, but you then put

0:23:10.680 --> 0:23:14.959
<v Speaker 1>into a holding pattern and in Discovery case, exactly doesn't

0:23:14.960 --> 0:23:17.480
<v Speaker 1>give you a your seventeenth in the queue expect a

0:23:17.480 --> 0:23:20.440
<v Speaker 1>wait of eight minutes. It just says please continue to hold.

0:23:21.480 --> 0:23:23.600
<v Speaker 1>So if they're tracking it by the answering of the call,

0:23:23.640 --> 0:23:26.200
<v Speaker 1>they're doing brilliantly. But if they're tracking it by the

0:23:26.240 --> 0:23:30.720
<v Speaker 1>actual moment of connection with the consultant, that that's a

0:23:30.720 --> 0:23:31.439
<v Speaker 1>different metric.

0:23:31.560 --> 0:23:33.320
<v Speaker 2>So that's that's not really clear there.

0:23:33.440 --> 0:23:35.480
<v Speaker 1>But Okay, so they do track the issue of how

0:23:35.720 --> 0:23:42.040
<v Speaker 1>quickly those call centers calls are answered. Okay, they've gone

0:23:42.040 --> 0:23:44.480
<v Speaker 1>back and looked at the they could find. Okay, so

0:23:44.520 --> 0:23:47.280
<v Speaker 1>they did receive my online submission. The one that went

0:23:47.320 --> 0:23:50.080
<v Speaker 1>blank obviously did make it to them, so they.

0:23:50.040 --> 0:23:50.719
<v Speaker 2>Had a look at that.

0:23:50.760 --> 0:23:53.199
<v Speaker 1>They've also, on their side, been able to access the

0:23:53.240 --> 0:23:57.160
<v Speaker 1>chat interaction with that agent and the comment is Discovery

0:23:57.160 --> 0:23:59.600
<v Speaker 1>Health review of the interaction between miss Hudson and our

0:23:59.600 --> 0:24:03.240
<v Speaker 1>agent has revealed that our chat agent should have resolved

0:24:03.240 --> 0:24:06.840
<v Speaker 1>the query for her right there during the engagement. Our

0:24:06.840 --> 0:24:09.879
<v Speaker 1>team is currently addressing this matter with the agent directly.

0:24:10.320 --> 0:24:12.960
<v Speaker 1>We hope that interactions such as these keep our teams

0:24:13.000 --> 0:24:17.359
<v Speaker 1>continuously learning and gaining the necessary skills to achieve better

0:24:17.440 --> 0:24:21.919
<v Speaker 1>client servicing outcomes in future. Unfortunately, she encountered issues with

0:24:21.960 --> 0:24:25.760
<v Speaker 1>the online form. We are currently investigating these technical challenges

0:24:26.080 --> 0:24:29.240
<v Speaker 1>by reviewing systems logs to understand what went wrong, and

0:24:29.280 --> 0:24:32.119
<v Speaker 1>we'll give further feedback once that's been done.

0:24:32.280 --> 0:24:33.480
<v Speaker 2>Here's the nub of it.

0:24:33.560 --> 0:24:37.040
<v Speaker 1>Okay, So, Discovery Health has been gradually transitioning away from

0:24:37.160 --> 0:24:40.840
<v Speaker 1>email as a primary service channel over the past two years.

0:24:41.240 --> 0:24:44.360
<v Speaker 1>This decision is based on data showing that email yields

0:24:44.520 --> 0:24:51.040
<v Speaker 1>slower resolution times and lower satisfaction scores. To support this transition,

0:24:52.000 --> 0:24:56.320
<v Speaker 1>proactive auto responses were implemented on selected email channels. So

0:24:56.440 --> 0:25:00.280
<v Speaker 1>that's what I was getting saying, YESUS channels no longer

0:25:00.280 --> 0:25:04.960
<v Speaker 1>in service. The get Help page was redesigned for improved usability,

0:25:05.359 --> 0:25:09.400
<v Speaker 1>and members who frequently used email did receive direct communication

0:25:10.119 --> 0:25:13.960
<v Speaker 1>from US guiding them to alternative digital channels during this

0:25:14.040 --> 0:25:18.359
<v Speaker 1>transition phase. We also understand that email remains necessary in

0:25:18.400 --> 0:25:22.239
<v Speaker 1>certain situations and will continue to support supported where it

0:25:22.280 --> 0:25:26.080
<v Speaker 1>makes practical sense. Some key email addresses are provided on

0:25:26.119 --> 0:25:29.720
<v Speaker 1>our website in the Complaints and Complements section.

0:25:29.720 --> 0:25:30.840
<v Speaker 2>I'm assuming that's meant.

0:25:30.640 --> 0:25:32.840
<v Speaker 1>To say, Okay, well, I wasn't able to find them

0:25:32.920 --> 0:25:36.040
<v Speaker 1>very easily, I'll say that, but okay. We have also

0:25:36.080 --> 0:25:39.159
<v Speaker 1>provided an alternate, an alternate to email in this section

0:25:39.240 --> 0:25:42.320
<v Speaker 1>of the GETTHLP inquiry, which is similar to an email

0:25:42.400 --> 0:25:47.480
<v Speaker 1>type experiencing prompting on the page guides which guide members

0:25:47.480 --> 0:25:50.560
<v Speaker 1>on what information to include to ensure that all necessary

0:25:50.600 --> 0:25:54.760
<v Speaker 1>information is available. This is just available via the app

0:25:54.800 --> 0:25:57.480
<v Speaker 1>and the website as well. Don't even get me started

0:25:57.560 --> 0:26:04.480
<v Speaker 1>on the app, okay, So just read one more line, Wendy,

0:26:04.280 --> 0:26:06.000
<v Speaker 1>and then we can then revert to you.

0:26:06.200 --> 0:26:06.600
<v Speaker 2>They say.

0:26:06.600 --> 0:26:10.399
<v Speaker 1>All member conversations are saved and accessible via the interaction

0:26:10.600 --> 0:26:14.679
<v Speaker 1>timeline on this discovery app. We have received screenshots of

0:26:14.760 --> 0:26:17.760
<v Speaker 1>the chat transcript and are prioritizing a review of her

0:26:17.840 --> 0:26:22.080
<v Speaker 1>profile with system support. So I mean it's fairly obvious.

0:26:22.119 --> 0:26:26.640
<v Speaker 1>It's they're unequivocal. They are digitally transitioning away from email

0:26:26.680 --> 0:26:28.479
<v Speaker 1>as a primary service, and have in fact been doing

0:26:28.560 --> 0:26:32.280
<v Speaker 1>so for quite some time already. My response to that is,

0:26:32.600 --> 0:26:35.760
<v Speaker 1>don't transition away from it until you've set up properly

0:26:36.400 --> 0:26:39.440
<v Speaker 1>the alternative, because the alternative just wasn't working in my case.

0:26:40.880 --> 0:26:44.400
<v Speaker 3>No. And in terms of the chat box history, are

0:26:44.400 --> 0:26:45.760
<v Speaker 3>they saying that they have a.

0:26:45.720 --> 0:26:49.240
<v Speaker 2>Record of it, a record of it? Yeah, that's the point.

0:26:49.359 --> 0:26:52.439
<v Speaker 3>It's like when you take out a contractor in a

0:26:52.520 --> 0:26:55.879
<v Speaker 3>policy over the phone. They've got the care recording and

0:26:55.920 --> 0:26:58.920
<v Speaker 3>you've got a big and plead for it. It's ridiculous.

0:26:59.000 --> 0:27:05.719
<v Speaker 3>And my other comment is on the main policy change

0:27:05.880 --> 0:27:09.640
<v Speaker 3>about gradually transitioning away from email as a primary service

0:27:10.320 --> 0:27:14.480
<v Speaker 3>based data showing that email yields slower resolution times and

0:27:14.560 --> 0:27:17.520
<v Speaker 3>lower satisfaction scores. I'd love to see that data by

0:27:17.640 --> 0:27:21.320
<v Speaker 3>contrast with data on how these new things that set

0:27:21.400 --> 0:27:23.919
<v Speaker 3>up are working for their customers. Bearing in mind that

0:27:24.040 --> 0:27:27.119
<v Speaker 3>the elderly suppit the most claims and have most reason

0:27:27.200 --> 0:27:29.040
<v Speaker 3>to want to interact with the medical scheme.

0:27:29.520 --> 0:27:29.760
<v Speaker 2>Yeah.

0:27:29.960 --> 0:27:34.840
<v Speaker 3>Absolutely, that's just actuarial fact. So I'm seeing a big

0:27:34.840 --> 0:27:37.520
<v Speaker 3>disconnect here, and it's not just discovery.

0:27:37.600 --> 0:27:41.760
<v Speaker 2>Let's be clear, it's not as well, which is to

0:27:41.880 --> 0:27:42.240
<v Speaker 2>my point.

0:27:42.240 --> 0:27:44.880
<v Speaker 1>I don't want this to be about my particular I mean,

0:27:44.880 --> 0:27:46.400
<v Speaker 1>this is an example of a much.

0:27:46.200 --> 0:27:47.920
<v Speaker 2>Bigger issue that's there.

0:27:48.840 --> 0:27:52.080
<v Speaker 1>Let me just share a few more of the responses

0:27:52.080 --> 0:27:54.959
<v Speaker 1>coming in here, Tony saying chatbots are the bane of

0:27:55.000 --> 0:27:57.840
<v Speaker 1>my life. I have yet to interact successfully with these

0:27:57.880 --> 0:28:02.000
<v Speaker 1>awful things. Unless your query is on their pre programmed menu,

0:28:02.400 --> 0:28:03.720
<v Speaker 1>you are wasting your time.

0:28:04.119 --> 0:28:06.480
<v Speaker 2>This is another interesting example of where it goes wrong.

0:28:06.560 --> 0:28:09.880
<v Speaker 1>Tony says, if you ever interact with the Telcom chatbot,

0:28:10.359 --> 0:28:12.919
<v Speaker 1>be prepared to tear your hair art it's called TUSO,

0:28:13.000 --> 0:28:15.360
<v Speaker 1>and eventually Twoso leads you to ask if you want

0:28:15.400 --> 0:28:18.960
<v Speaker 1>to speak to a human, You answer yes, will get

0:28:19.080 --> 0:28:21.280
<v Speaker 1>You're then told you will get an SMS that you sorry,

0:28:21.280 --> 0:28:24.320
<v Speaker 1>You get an SMS that a Talcom consultant will call you,

0:28:24.640 --> 0:28:27.000
<v Speaker 1>and Tony says, they never do. I have about eight

0:28:27.040 --> 0:28:31.320
<v Speaker 1>to ten SMSs. I've never received a call. So there's

0:28:31.359 --> 0:28:33.919
<v Speaker 1>another example. The system gives you the option of speaking

0:28:33.960 --> 0:28:38.320
<v Speaker 1>to a human, but then doesn't connect you to the human.

0:28:39.520 --> 0:28:40.680
<v Speaker 2>What else have we got here?

0:28:40.920 --> 0:28:43.440
<v Speaker 1>Karen saying the Discovery site is the worst to try

0:28:43.480 --> 0:28:48.520
<v Speaker 1>and navigate endless loops. Richard's saying to Discoveries Reply regarding

0:28:48.560 --> 0:28:52.440
<v Speaker 1>a move away from email, faster resolution times doesn't take

0:28:52.480 --> 0:28:56.680
<v Speaker 1>into account the customer's time chasing all of these channels

0:28:56.720 --> 0:28:59.640
<v Speaker 1>and waiting, And that's point made. This is why I

0:28:59.760 --> 0:29:02.680
<v Speaker 1>meant to Wendy Richard, because it took me nineteen minutes

0:29:03.360 --> 0:29:06.480
<v Speaker 1>to finally, you know, find a way to flag the

0:29:06.520 --> 0:29:09.000
<v Speaker 1>issue I was trying to flag. Lisa is saying it's

0:29:09.160 --> 0:29:13.880
<v Speaker 1>indifference and lack of accountability. Zoos's commented digital customer service

0:29:13.920 --> 0:29:17.360
<v Speaker 1>channels are really not great because they give specific prompts

0:29:17.600 --> 0:29:19.560
<v Speaker 1>and sometimes one is not even sure what.

0:29:19.680 --> 0:29:22.800
<v Speaker 2>The issue is to begin with. So I take your point.

0:29:22.840 --> 0:29:26.120
<v Speaker 1>It makes it difficult to get yourself into the correct

0:29:26.160 --> 0:29:29.160
<v Speaker 1>stream if you don't know what the nature of the

0:29:29.160 --> 0:29:31.840
<v Speaker 1>problem is, and that's often a you know, a press

0:29:31.880 --> 0:29:33.920
<v Speaker 1>one for this, press two for that, press three for that,

0:29:34.280 --> 0:29:36.200
<v Speaker 1>and you get to the end of the menu're saying, well,

0:29:36.240 --> 0:29:38.520
<v Speaker 1>you never gave me an option to press X for

0:29:38.600 --> 0:29:42.600
<v Speaker 1>what my problem actually is. Yeah, a couple of ye,

0:29:43.240 --> 0:29:44.760
<v Speaker 1>a couple of voice notes. When didoul we listen to

0:29:44.800 --> 0:29:46.880
<v Speaker 1>a voice note or two before you respond any further?

0:29:47.760 --> 0:29:51.680
<v Speaker 4>Hi, Shop and Wendy, that clicks problem with the sms.

0:29:51.720 --> 0:29:54.479
<v Speaker 4>I had the same issue twenty around and around for

0:29:54.520 --> 0:29:57.600
<v Speaker 4>about seven or eight weeks until I threatened them to

0:29:57.640 --> 0:30:02.240
<v Speaker 4>take them to the Consumer Consume Commission and they somehow

0:30:02.840 --> 0:30:08.920
<v Speaker 4>managed to have men not complete that last section of

0:30:09.040 --> 0:30:16.320
<v Speaker 4>the verification of your credent of your clicks account. It's useless.

0:30:17.000 --> 0:30:20.120
<v Speaker 4>But yeah, same exact, same problem, And I kept telling

0:30:20.240 --> 0:30:22.280
<v Speaker 4>except I never ever got an answer as to why

0:30:22.800 --> 0:30:26.800
<v Speaker 4>my SMS we're never coming through. So they never told me.

0:30:26.880 --> 0:30:29.280
<v Speaker 4>Now it's interesting that because I'm also on the do

0:30:29.360 --> 0:30:34.280
<v Speaker 4>not contact What's what's a list database, and so it's

0:30:34.280 --> 0:30:38.160
<v Speaker 4>interesting that Zuki got an answer from them as to

0:30:38.200 --> 0:30:40.320
<v Speaker 4>why it wasn't coming through. Mind, they just kept saying,

0:30:40.720 --> 0:30:43.760
<v Speaker 4>we've escalated to the IT department, et cetera, et cetera,

0:30:43.800 --> 0:30:46.680
<v Speaker 4>and went on for nearly six or seven weeks.

0:30:47.240 --> 0:30:50.480
<v Speaker 1>Yeah, okay, I'm glad it was resolved in the end, Tony,

0:30:50.520 --> 0:30:52.800
<v Speaker 1>but thanks for that. There is Before we go to

0:30:52.840 --> 0:30:55.160
<v Speaker 1>the next voice note, I want to take a call Wendy,

0:30:55.200 --> 0:30:58.160
<v Speaker 1>because we have a business owner on the line who's

0:30:58.200 --> 0:31:00.600
<v Speaker 1>taken a very very different approach wants to share it

0:31:00.640 --> 0:31:03.800
<v Speaker 1>with us, Ian and US good afternoon. Hi.

0:31:05.200 --> 0:31:07.600
<v Speaker 5>Yeah, so we made the decision. Yeah, And I think

0:31:07.640 --> 0:31:10.520
<v Speaker 5>I share everybody's frustration, so I won't repeat all of

0:31:10.520 --> 0:31:14.719
<v Speaker 5>that that. You know, the impersonal nature of chatbots and

0:31:15.360 --> 0:31:18.680
<v Speaker 5>corresponding by email just drives me absolutely insane. And I

0:31:18.960 --> 0:31:20.880
<v Speaker 5>one thread up quote by well I think it was

0:31:20.920 --> 0:31:24.440
<v Speaker 5>Warren Buffett who said, in a world, in the modern world,

0:31:24.520 --> 0:31:27.120
<v Speaker 5>it's not enough to satisfy your customer, you have to

0:31:27.200 --> 0:31:30.080
<v Speaker 5>delight them. Because everybody is satisfying their customer, you have

0:31:30.120 --> 0:31:31.960
<v Speaker 5>to delight them. And then, certainly in our market, which

0:31:32.000 --> 0:31:35.840
<v Speaker 5>is in the technology space, interestingly enough, is we're finding

0:31:35.840 --> 0:31:40.120
<v Speaker 5>that our customers are actually craving human interaction. They want

0:31:40.280 --> 0:31:42.640
<v Speaker 5>a phone call, they want to speak to somebody, they

0:31:42.680 --> 0:31:45.560
<v Speaker 5>want to know a name, they want to have somebody

0:31:45.560 --> 0:31:47.600
<v Speaker 5>that can call when things aren't going right. And the

0:31:47.640 --> 0:31:51.720
<v Speaker 5>reaction that you get is actually remarkable because they go

0:31:51.880 --> 0:31:54.320
<v Speaker 5>out of their way to say, you know, how refreshing

0:31:54.480 --> 0:31:57.560
<v Speaker 5>is to actually have somebody call us, and to be

0:31:57.640 --> 0:32:00.960
<v Speaker 5>proactive about building a relationship. So I think, for as

0:32:01.040 --> 0:32:03.400
<v Speaker 5>much as we're all getting frustrated by this migration to

0:32:03.520 --> 0:32:06.960
<v Speaker 5>chatbots and AI driven responses, etc. And I get you know,

0:32:06.960 --> 0:32:09.080
<v Speaker 5>if you're a large organization and you're dealing with millions

0:32:09.120 --> 0:32:12.480
<v Speaker 5>and millions of queries, there probably are benefits to going

0:32:12.560 --> 0:32:15.520
<v Speaker 5>that route. But for a smaller business, take the time

0:32:15.640 --> 0:32:18.200
<v Speaker 5>to actually or use this opportunity to say, how do

0:32:18.240 --> 0:32:21.440
<v Speaker 5>you differentiate yourself in a market where everybody else is

0:32:21.440 --> 0:32:23.760
<v Speaker 5>going in the other direction? The age old quote when

0:32:23.760 --> 0:32:26.320
<v Speaker 5>everybody is getting on the bus, it's time to get off,

0:32:26.800 --> 0:32:29.160
<v Speaker 5>and you'll differentiate yourself in the market and offer a

0:32:29.160 --> 0:32:31.800
<v Speaker 5>better personal service and your business will benefit from it.

0:32:32.480 --> 0:32:35.160
<v Speaker 1>I absolutely love that approach, and all I can say

0:32:35.240 --> 0:32:38.200
<v Speaker 1>is I hope it gets you lots of happy customers

0:32:38.280 --> 0:32:40.200
<v Speaker 1>you stay with you and on loyal because of that.

0:32:40.320 --> 0:32:42.840
<v Speaker 1>So thank you so much for calling in to raise that.

0:32:43.160 --> 0:32:45.680
<v Speaker 1>What a fantastic alternative view.

0:32:45.760 --> 0:32:46.080
<v Speaker 2>Wendy.

0:32:47.760 --> 0:32:51.560
<v Speaker 3>Absolutely, and yes, I mean when I ad to customer

0:32:51.640 --> 0:32:54.600
<v Speaker 3>care trading, I say, if you're dealing with, particularly someone

0:32:54.640 --> 0:32:58.080
<v Speaker 3>who's over fifty to fifty five, if you've messed up

0:32:58.600 --> 0:33:00.480
<v Speaker 3>and you want to make it right, pick up the

0:33:00.520 --> 0:33:02.840
<v Speaker 3>phone and phone. The millennials hate that they want to

0:33:02.880 --> 0:33:05.120
<v Speaker 3>talk to you on the phone. It's the worst. But

0:33:05.360 --> 0:33:07.760
<v Speaker 3>for an older person it's going to fix the problem

0:33:07.760 --> 0:33:10.040
<v Speaker 3>and they will forgive you and it will all be good.

0:33:10.080 --> 0:33:12.280
<v Speaker 3>And they all look at me, because it's usually millennials

0:33:12.280 --> 0:33:14.000
<v Speaker 3>in the audience, they look at me wired out like

0:33:14.120 --> 0:33:18.520
<v Speaker 3>they try it. It'll work. I mean, we we and

0:33:18.600 --> 0:33:22.000
<v Speaker 3>I think also even the millennials as they get old.

0:33:22.040 --> 0:33:24.280
<v Speaker 3>I don't know if this will change, but you do,

0:33:24.440 --> 0:33:27.200
<v Speaker 3>especially if your problem is not solvable. It's not Pridge

0:33:27.240 --> 0:33:30.320
<v Speaker 3>and a hoolable that you you know, query one, two, three,

0:33:30.960 --> 0:33:34.560
<v Speaker 3>four five. You just want to have that human interaction

0:33:34.600 --> 0:33:36.600
<v Speaker 3>where he said, this is the problem, please help me,

0:33:37.160 --> 0:33:40.280
<v Speaker 3>without spending ninety minutes going round and round and trying

0:33:40.280 --> 0:33:43.040
<v Speaker 3>to do it the digital way and ending up really

0:33:43.080 --> 0:33:47.520
<v Speaker 3>frustrated and not feeling very warm and fuzzy towards that

0:33:47.560 --> 0:33:49.160
<v Speaker 3>company at all. Yeah.

0:33:49.320 --> 0:33:49.640
<v Speaker 2>Yeah.

0:33:49.960 --> 0:33:53.400
<v Speaker 1>The result is you get a customer like Lisa raising

0:33:53.640 --> 0:33:57.680
<v Speaker 1>digital customer service with the Woolworth's My Difference app saying

0:33:57.720 --> 0:33:59.760
<v Speaker 1>trying to deal with one person who knows all the

0:33:59.800 --> 0:34:03.760
<v Speaker 1>des is impossible. You end up getting multiple responses from

0:34:03.840 --> 0:34:07.120
<v Speaker 1>various people trying to follow up on different platforms, and

0:34:07.160 --> 0:34:09.759
<v Speaker 1>all that happens is the customer gets more irritated at

0:34:09.800 --> 0:34:13.200
<v Speaker 1>the end of it instead of just having their issue resolved.

0:34:13.840 --> 0:34:14.960
<v Speaker 2>So thanks for that, Lisa.

0:34:15.080 --> 0:34:16.880
<v Speaker 1>I think we've got time to squeeze in one more

0:34:16.960 --> 0:34:18.719
<v Speaker 1>voice note as well before we must wrap up.

0:34:18.760 --> 0:34:24.680
<v Speaker 6>Let's take a listen, Andre, I just find Discoveries apps

0:34:25.080 --> 0:34:29.400
<v Speaker 6>utterly user unfriendly, and I'm surprised that our user on

0:34:29.520 --> 0:34:32.160
<v Speaker 6>friendly is seeing that it's one of the best technological

0:34:32.200 --> 0:34:36.560
<v Speaker 6>companies in the country. Yeah, so I don't know if

0:34:36.560 --> 0:34:39.840
<v Speaker 6>they know it, but it's really bad and unfriendly bye bye.

0:34:41.360 --> 0:34:41.640
<v Speaker 3>Yeah.

0:34:42.520 --> 0:34:43.799
<v Speaker 1>If they don't know it by the end of the

0:34:43.880 --> 0:34:48.280
<v Speaker 1>savord read here, there'll be something wrong now, I must

0:34:48.560 --> 0:34:50.960
<v Speaker 1>they did acknowledge they are having because one of the

0:34:51.000 --> 0:34:52.680
<v Speaker 1>other issues we didn't even get to was when I

0:34:52.719 --> 0:34:56.120
<v Speaker 1>then went onto the app to try and find an

0:34:56.160 --> 0:34:59.120
<v Speaker 1>alternative supplier to move away from the one I'd had

0:34:59.160 --> 0:35:03.320
<v Speaker 1>problems with the sort of geographical settings we're not working.

0:35:03.400 --> 0:35:05.400
<v Speaker 1>So you go in to find a pharmacy near me,

0:35:05.840 --> 0:35:07.840
<v Speaker 1>and it offered me the runts By Pharmacy, which was

0:35:07.880 --> 0:35:10.240
<v Speaker 1>at the time about one hundred and sixty five kilometers away,

0:35:10.640 --> 0:35:12.600
<v Speaker 1>So there clearly are some issues that still need to

0:35:12.600 --> 0:35:15.640
<v Speaker 1>be resolved on the app, and they've acknowledged that in

0:35:15.680 --> 0:35:18.440
<v Speaker 1>their email correspondence. See we are aware of a recent

0:35:18.520 --> 0:35:22.160
<v Speaker 1>issue affecting the Finder Provider feature on the Discovery app

0:35:22.200 --> 0:35:26.240
<v Speaker 1>and WhatsApp where the results have been inaccurate. We apologize

0:35:26.600 --> 0:35:29.160
<v Speaker 1>we're working on a resolution for that. So at Lease

0:35:29.120 --> 0:35:31.400
<v Speaker 1>they're acknowledging awareness of the fact that there is a

0:35:31.440 --> 0:35:34.640
<v Speaker 1>problem there. Wendy, I mean, it's a topic today for

0:35:34.680 --> 0:35:38.880
<v Speaker 1>which we have no fix, no answers, other than to

0:35:38.960 --> 0:35:41.719
<v Speaker 1>hope that customers are listening, and the people listening to

0:35:41.760 --> 0:35:44.080
<v Speaker 1>this interview who are involved in customer service are going

0:35:44.120 --> 0:35:46.719
<v Speaker 1>to feedback to the companies they work for that there

0:35:46.760 --> 0:35:49.640
<v Speaker 1>is a need to balance both. And I don't dispute

0:35:49.680 --> 0:35:52.759
<v Speaker 1>that for some cases moving to digital is brilliant and

0:35:52.800 --> 0:35:55.759
<v Speaker 1>that you can take a large sort of workload off

0:35:55.760 --> 0:35:59.920
<v Speaker 1>your desk and digitize simple functions like issuing the tax certificate,

0:36:00.120 --> 0:36:03.879
<v Speaker 1>the membership confirmation or whatever it is. But I hope

0:36:04.000 --> 0:36:06.759
<v Speaker 1>you know customer service people are paying attention to the

0:36:06.840 --> 0:36:09.960
<v Speaker 1>kind of complaints we've heard today about how that experience

0:36:10.000 --> 0:36:13.640
<v Speaker 1>of forcing people into the digital environment is making them

0:36:13.640 --> 0:36:17.280
<v Speaker 1>feel and Wendy what I'm hearing. It's making people feel unheard,

0:36:18.440 --> 0:36:22.120
<v Speaker 1>unimportant to the company, and ultimately not listened to, and

0:36:22.160 --> 0:36:24.840
<v Speaker 1>it's leaving them more frustrated at the end of the

0:36:24.920 --> 0:36:27.760
<v Speaker 1>experience than they were when the problem first occurred.

0:36:29.120 --> 0:36:31.600
<v Speaker 3>Yeah, I think Alice put it very well as Alice

0:36:31.640 --> 0:36:35.759
<v Speaker 3>when she said it seems like customer invoidance rather than

0:36:36.200 --> 0:36:39.759
<v Speaker 3>a willingness to engage with customers. And that's really I mean,

0:36:40.160 --> 0:36:43.760
<v Speaker 3>I can't even the synicon me doesn't want to believe

0:36:43.760 --> 0:36:49.200
<v Speaker 3>that that's the intention. But that's for many people, the reality,

0:36:49.320 --> 0:36:53.439
<v Speaker 3>the lived experience. So I think we should all keep

0:36:53.480 --> 0:36:55.399
<v Speaker 3>talking about this. They might be people who think it's

0:36:55.440 --> 0:36:59.480
<v Speaker 3>just them I'm old, and no, it is a general experience,

0:36:59.680 --> 0:37:03.279
<v Speaker 3>and we should keep it in the public discourse, use

0:37:03.320 --> 0:37:05.880
<v Speaker 3>social media, talk about it and shows like this, and

0:37:06.000 --> 0:37:10.560
<v Speaker 3>hold the service providers to account because sometimes they just

0:37:10.719 --> 0:37:13.000
<v Speaker 3>don't have enough of a read on what it's like

0:37:13.480 --> 0:37:15.799
<v Speaker 3>on their receiving end. As a customer, you know, it's

0:37:15.840 --> 0:37:18.160
<v Speaker 3>great technology and it's the latest, greatest, and the end

0:37:18.280 --> 0:37:21.600
<v Speaker 3>misted a lot, but is it actually working for the

0:37:21.640 --> 0:37:23.480
<v Speaker 3>customer and the way they think it is.

0:37:24.200 --> 0:37:27.239
<v Speaker 1>Wendy, thanks so much for a really interesting segment today.

0:37:27.280 --> 0:37:29.680
<v Speaker 1>We look forward to chatting to you again next week Wednesday.

0:37:29.719 --> 0:37:31.759
<v Speaker 1>And reminder to listeners if you want to flag a

0:37:31.800 --> 0:37:35.200
<v Speaker 1>case with Wendy, she does respond to her online form

0:37:35.239 --> 0:37:39.000
<v Speaker 1>at Wendynona dot co dotz chat next week, Wendy