New Merchant Dashboard Tour Webinar

0 - 00:00:00.700 –> 00:00:03.900 All right. I think we’ll go ahead and kick

1 - 00:00:03.900 –> 00:00:06.300 things off really excited to

2 - 00:00:06.300 –> 00:00:09.700 have everyone here today to talk

3 - 00:00:09.700 –> 00:00:12.100 about Bolt’s new Merchant dashboard.

4 - 00:00:13.900 –> 00:00:16.500 Get started here. So by

5 - 00:00:16.500 –> 00:00:19.300 way of introductions. Hello. I’m Natalie. I’m the

6 - 00:00:19.300 –> 00:00:22.500 Senior Manager of Customer Education here at Bolt. I’ve been

7 - 00:00:22.500 –> 00:00:24.800 at Bolt for about three and a half years and I’ve spent

8 - 00:00:26.500 –> 00:00:29.500 the better part of 10 years in B2B SAAS

9 - 00:00:29.500 –> 00:00:30.000 Customer Education

10 - 00:00:30.600 –> 00:00:34.000 So this is by my bread and butter for quite a while and I’m

11 - 00:00:33.100 –> 00:00:37.400 really excited to be leading you through this content today additionally

12 - 00:00:36.400 –> 00:00:40.400 today. We have Taronay Roohafzaii. Taronay

13 - 00:00:39.400 –> 00:00:42.900 is the Product Manager who led the

14 - 00:00:42.900 –> 00:00:45.500 redesign of the Merchant Dashboard. So I’m

15 - 00:00:45.500 –> 00:00:48.600 feeling really grateful that we have an absolute expert

16 - 00:00:48.600 –> 00:00:51.300 here who can help answer any questions. She’s gonna be

17 - 00:00:51.300 –> 00:00:54.500 our special guest star helping us

18 - 00:00:54.500 –> 00:00:57.800 out mostly via chat. So feel free

19 - 00:00:57.800 –> 00:01:00.200 to drop questions you have in chat. We’ll do a

20 - 00:01:00.200 –> 00:01:03.300 lot of the responding in chat from Taronay

21 - 00:01:03.300 –> 00:01:06.400 directly and from a couple other experts who are on the line. So that’s

22 - 00:01:06.400 –> 00:01:07.100 the two of us.

23 - 00:01:08.300 –> 00:01:11.800 Let’s talk a little bit about our agenda. So for

24 - 00:01:11.800 –> 00:01:14.700 today for our time together, we’re going to start with our introductions.

25 - 00:01:14.700 –> 00:01:17.300 We are already halfway through that. So we’re

26 - 00:01:17.300 –> 00:01:18.200 making great progress today.

27 - 00:01:19.500 –> 00:01:22.300 Then we’re going to talk a little bit about the background of this

28 - 00:01:22.300 –> 00:01:25.400 project. What brought us here? Why did we want to make the changes that

29 - 00:01:25.400 –> 00:01:28.400 we made? How did we think about this? We’re gonna

30 - 00:01:28.400 –> 00:01:31.200 go through a couple of slides with that. So we’ll talk high level about

31 - 00:01:31.200 –> 00:01:34.500 what changed and then we’re gonna dive into a live demo.

32 - 00:01:34.500 –> 00:01:37.100 So I’ll be going through the Merchant Dashboard in a

33 - 00:01:37.100 –> 00:01:40.800 demo environment or a demo Merchant rather so that

34 - 00:01:40.800 –> 00:01:43.100 we can actually see it together. We’ll have some

35 - 00:01:43.100 –> 00:01:46.400 time dedicated for Q&A at the end. But please feel

36 - 00:01:46.400 –> 00:01:49.700 free to drop in questions anytime within the

37 - 00:01:49.700 –> 00:01:52.300 chat. We’ll be monitoring that and if you see me

38 - 00:01:52.300 –> 00:01:55.200 looking this direction awkwardly, it’s because I’m looking

39 - 00:01:55.200 –> 00:01:58.700 at chat so we’ll be sure to monitor chat monitor

40 - 00:01:58.700 –> 00:02:01.200 Q&A to answer any questions that you might

41 - 00:02:01.200 –> 00:02:05.800 have and then at the end we do have a survey fun

42 - 00:02:04.800 –> 00:02:07.600 fact. This webinar was

43 - 00:02:07.600 –> 00:02:10.000 a direct result of survey feedback that we

44 - 00:02:10.300 –> 00:02:13.400 had gotten before asking for more Merchant dashboard content.

45 - 00:02:13.400 –> 00:02:16.600 So we do take your survey results responses very

46 - 00:02:16.600 –> 00:02:18.500 seriously. We want that feedback. We want to know.

47 - 00:02:19.400 –> 00:02:22.400 Not just what you liked and what you didn’t like but also what you want to see more of so

48 - 00:02:22.400 –> 00:02:26.000 that we can give you the best programming possible to help

49 - 00:02:25.300 –> 00:02:28.800 you enjoy using Bolt as much as possible. So

50 - 00:02:28.800 –> 00:02:30.600 that’s what we’re in for today.

51 - 00:02:31.600 –> 00:02:35.200 With that we’re gonna do a round of introductions. So

52 - 00:02:34.200 –> 00:02:37.400 for my folks who are joining

53 - 00:02:37.400 –> 00:02:40.400 for all the merchants joining. I would love it if you could take about

54 - 00:02:40.400 –> 00:02:43.300 30 seconds or so and drop your name your

55 - 00:02:43.300 –> 00:02:46.800 company and what Drew you to this session in to

56 - 00:02:46.800 –> 00:02:49.300 the chat. We’ve got a couple folks who already did

57 - 00:02:49.300 –> 00:02:52.200 so Nathaniel Nadine Susan. Thank you all for that

58 - 00:02:52.200 –> 00:02:54.000 if you want to introduce yourselves again.

59 - 00:02:54.900 –> 00:02:57.800 You’re more than welcome to but for everyone else let

60 - 00:02:57.800 –> 00:03:00.600 us know who you are. Let us know where you come from and why

61 - 00:03:00.600 –> 00:03:02.200 you decided to join us today?

62 - 00:03:04.900 –> 00:03:07.300 Bernardo’s awesome. Thank you

63 - 00:03:07.300 –> 00:03:08.200 for joining.

64 - 00:03:13.200 –> 00:03:15.300 Susan thanks for coming by.

65 - 00:03:20.600 –> 00:03:21.300 Gabby

66 - 00:03:22.100 –> 00:03:25.800 Love to see you here, Claudia Forever 21. Awesome.

67 - 00:03:25.800 –> 00:03:27.800 Very excited to show you the new portal.

68 - 00:03:28.800 –> 00:03:31.800 Great. Well, thank you everyone for introducing yourselves. I’m

69 - 00:03:31.800 –> 00:03:34.900 really excited to have you all here today very excited

70 - 00:03:34.900 –> 00:03:37.800 to go through the new dashboard. So without further

71 - 00:03:37.800 –> 00:03:38.100 ado.

72 - 00:03:39.100 –> 00:03:40.500 Let’s talk about the dashboard.

73 - 00:03:41.300 –> 00:03:43.400 First up we’re going to do a little bit of background.

74 - 00:03:45.100 –> 00:03:48.300 For those of you who have used our Legacy dashboard, which I’m assuming

75 - 00:03:48.300 –> 00:03:51.300 is most if not, all of you. You may have found that it didn’t

76 - 00:03:51.300 –> 00:03:54.300 exactly need your meet your needs in the most intuitive way.

77 - 00:03:54.300 –> 00:03:57.300 We got reports of folks having

78 - 00:03:57.300 –> 00:04:00.500 a hard time finding information not really driving

79 - 00:04:00.500 –> 00:04:03.700 with our navigation and just finding the UX to

80 - 00:04:03.700 –> 00:04:06.600 be a little bit unwieldy. So we wanted to fix

81 - 00:04:06.600 –> 00:04:09.300 that for all of you that is really what led

82 - 00:04:09.300 –> 00:04:12.400 us to this overhaul project and in this

83 - 00:04:12.400 –> 00:04:15.300 because we got to completely overhaul our Merchant dashboard.

84 - 00:04:15.300 –> 00:04:18.600 It also gave us the opportunity to optimize our backend code

85 - 00:04:18.600 –> 00:04:21.400 to decrease latency. So we think we’ve provided

86 - 00:04:21.400 –> 00:04:24.600 you with something that is beautiful functional and also faster

87 - 00:04:24.600 –> 00:04:27.300 than ever before so we’re very excited that you

88 - 00:04:27.300 –> 00:04:28.300 get to experience it.

89 - 00:04:29.300 –> 00:04:32.200 Our end goal here was to increase the value of the

90 - 00:04:32.200 –> 00:04:35.200 dashboard so that it can become a tool that you use every day

91 - 00:04:35.200 –> 00:04:38.800 to optimize your business and ultimately help you drive revenue.

92 - 00:04:38.800 –> 00:04:40.600 So that’s how we got here.

93 - 00:04:41.500 –> 00:04:44.200 A couple key highlights that will go over today.

94 - 00:04:45.200 –> 00:04:47.300 We have a new homepage and navigation.

95 - 00:04:48.300 –> 00:04:49.800 We have streamlined Analytics.

96 - 00:04:50.700 –> 00:04:54.600 We have transaction updates and those include improved

97 - 00:04:53.600 –> 00:04:56.900 filtering revamped transaction

98 - 00:04:56.900 –> 00:04:57.600 timeline.

99 - 00:04:58.500 –> 00:05:00.000 quick access to disputes

100 - 00:05:00.600 –> 00:05:03.400 for those using disputes not all of our Merchants make

101 - 00:05:03.400 –> 00:05:07.000 use of our dispute service, but for those using disputes and then at

102 - 00:05:06.100 –> 00:05:09.800 a glance risk scoring for transactions, those

103 - 00:05:09.800 –> 00:05:12.500 are some of the things we’ll dive into in more detail.

104 - 00:05:12.500 –> 00:05:15.600 So starting with our homepage

105 - 00:05:15.600 –> 00:05:18.500 and navigation again, for those of you who have

106 - 00:05:18.500 –> 00:05:21.800 used our Merchant dashboard of fair bit. You probably remember logging

107 - 00:05:21.800 –> 00:05:24.100 in and immediately seeing the transactions page.

108 - 00:05:24.800 –> 00:05:27.400 Transactions page is very useful. It’s where

109 - 00:05:27.400 –> 00:05:30.500 most of our users spend most of their time. But we wanted to

110 - 00:05:30.500 –> 00:05:33.400 give you something a little bit higher level

111 - 00:05:33.400 –> 00:05:36.400 a little more meaningful when you first sign in so we’ve added

112 - 00:05:36.400 –> 00:05:39.500 this new homepage which has an executive summary

113 - 00:05:39.500 –> 00:05:42.600 so that way when you log in you’re immediately greeted

114 - 00:05:42.600 –> 00:05:45.800 with an overview of how your business is doing. We’ve also

115 - 00:05:45.800 –> 00:05:48.300 made some navigational changes. So you’ll

116 - 00:05:48.300 –> 00:05:51.600 notice that instead of our navigation being along the top we’ve shifted

117 - 00:05:51.600 –> 00:05:54.600 that to the left hand side. That’s just going to make everything a

118 - 00:05:54.600 –> 00:05:57.600 little bit easier to find and a little bit more responsive.

119 - 00:05:59.300 –> 00:06:02.600 On analytics what we’ve done here is really tried

120 - 00:06:02.600 –> 00:06:05.700 to optimize for usability and readability. So we’ve

121 - 00:06:05.700 –> 00:06:08.300 removed a few reports that we found just weren’t really

122 - 00:06:08.300 –> 00:06:11.200 pulling their weight and we’ve added a few new

123 - 00:06:11.200 –> 00:06:14.500 reports as well to help illuminate Bolt value. So

124 - 00:06:14.500 –> 00:06:17.700 here Focus was on streamlining to

125 - 00:06:17.700 –> 00:06:20.300 make sure you’re getting the right information as quickly as

126 - 00:06:20.300 –> 00:06:20.800 possible.

127 - 00:06:22.100 –> 00:06:25.100 Next up we have the transactions page. Like I said,

128 - 00:06:25.100 –> 00:06:28.700 this is where most of our users spend most of their time. So

129 - 00:06:28.700 –> 00:06:31.300 we wanted to make this as useful as possible for all

130 - 00:06:31.300 –> 00:06:34.200 of you what we’ve done to that end as we’ve added in

131 - 00:06:34.200 –> 00:06:37.800 a transactions timeline. This allows you to see at

132 - 00:06:37.800 –> 00:06:40.700 a glance where a transaction is within the transaction lifecycle.

133 - 00:06:40.700 –> 00:06:44.100 And then for those of you using our disputes

134 - 00:06:43.100 –> 00:06:46.800 service, we also have self-service disputes

135 - 00:06:46.800 –> 00:06:49.100 right within transactions. We’ll take

136 - 00:06:49.100 –> 00:06:50.900 a closer look at that in a little bit.

137 - 00:06:52.600 –> 00:06:55.800 And we have a couple new bonus features as well. So we

138 - 00:06:55.800 –> 00:06:58.700 will cover this one in action,

139 - 00:06:58.700 –> 00:07:01.500 but everyone can now enable Merchant specific block

140 - 00:07:01.500 –> 00:07:04.900 lists in their fraud settings. And then for our M2 users

141 - 00:07:04.900 –> 00:07:07.200 who are using the subscriptions product you’re able to

142 - 00:07:07.200 –> 00:07:10.200 configure manage the configure and manage your

143 - 00:07:10.200 –> 00:07:13.800 offers and view subscription performance within the dashboard. So

144 - 00:07:13.800 –> 00:07:14.100 we’ve got

145 - 00:07:14.900 –> 00:07:17.300 a couple fun extras that we threw in there as

146 - 00:07:17.300 –> 00:07:17.300 well.

147 - 00:07:18.600 –> 00:07:21.900 With that let’s dive in. So here

148 - 00:07:21.900 –> 00:07:24.200 we are in the Merchant Dashboard.

149 - 00:07:25.900 –> 00:07:28.600 This is what you see when you first log in couple things

150 - 00:07:28.600 –> 00:07:31.000 that I want to point out. So first up at the

151 - 00:07:31.100 –> 00:07:34.500 top in this blue banner. We have a tour button if you

152 - 00:07:34.500 –> 00:07:37.300 walk away from this and you’re saying to yourself Natalie you talked about

153 - 00:07:37.300 –> 00:07:40.400 too much. I don’t remember you can always go back to the tour and that’ll

154 - 00:07:40.400 –> 00:07:43.300 give you a guided walkthrough of our dashboard so that

155 - 00:07:43.300 –> 00:07:44.300 you have that handy anytime.

156 - 00:07:45.300 –> 00:07:49.000 We’re going to scroll past that and look at our executive summary

157 - 00:07:48.600 –> 00:07:51.700 instead now our executive

158 - 00:07:51.700 –> 00:07:54.400 summary in this particular demo store

159 - 00:07:54.400 –> 00:07:57.400 looks I hope not as nice

160 - 00:07:57.400 –> 00:08:00.500 as your executive summary because we only have four

161 - 00:08:00.500 –> 00:08:03.000 cents of GMV in the last seven days. So one thing

162 - 00:08:03.200 –> 00:08:06.200 I do want to call out is this summary is looking at the last seven days

163 - 00:08:06.200 –> 00:08:06.900 specifically

164 - 00:08:08.300 –> 00:08:10.700 so as we go through today’s demo just

165 - 00:08:11.600 –> 00:08:14.900 ignore the hard data points. Your

166 - 00:08:14.900 –> 00:08:17.500 environment is going to make a lot more sense than ours because

167 - 00:08:17.500 –> 00:08:20.400 you will do a lot more business than we do in this demo store.

168 - 00:08:20.400 –> 00:08:23.700 But you know, the meat

169 - 00:08:23.700 –> 00:08:26.400 of this is still the same we’ve got four key data

170 - 00:08:26.400 –> 00:08:29.100 points that I want to show you here in the executive summary. So we’ve

171 - 00:08:29.100 –> 00:08:32.400 got our GMV percentage of GMV from Bolt

172 - 00:08:32.400 –> 00:08:35.100 Shoppers check out conversion rate and fraud order

173 - 00:08:35.100 –> 00:08:38.400 approval rate. Those are the four key metrics that we’ve pulled out for

174 - 00:08:38.400 –> 00:08:41.300 you here, but if you want to dig in a

175 - 00:08:41.300 –> 00:08:44.400 little deeper, you can do that by either see clicking see more

176 - 00:08:44.400 –> 00:08:44.800 Analytics.

177 - 00:08:45.800 –> 00:08:48.200 Or analytics on the left hand side. Both of

178 - 00:08:48.200 –> 00:08:50.100 these are going to take you to the same place.

179 - 00:08:50.800 –> 00:08:53.600 And while we’re talking about this left-hand navigation, I

180 - 00:08:53.600 –> 00:08:56.200 do want to call out that the way we’ve built a new

181 - 00:08:56.200 –> 00:08:59.800 dashboard is a responsive design which means it’s going to shift slightly.

182 - 00:08:59.800 –> 00:09:02.000 It’s going to change what you see based on

183 - 00:09:02.100 –> 00:09:06.100 the size of your browser window. So if at any point, you’re like Natalie,

184 - 00:09:05.100 –> 00:09:08.700 I pull mine up and it looks different. It’s probably

185 - 00:09:08.700 –> 00:09:11.300 because you need to expand your browser window make

186 - 00:09:11.300 –> 00:09:14.700 it a little bit wider or zoom out so that you can see everything

187 - 00:09:14.700 –> 00:09:17.300 in action. So just keep that in

188 - 00:09:17.300 –> 00:09:20.200 mind. If ever you’re like hold up again. This doesn’t

189 - 00:09:20.200 –> 00:09:20.900 look quite the same.

190 - 00:09:22.200 –> 00:09:26.000 All right. So with that let’s double

191 - 00:09:25.300 –> 00:09:28.200 click into analytics. I’m going to use the left

192 - 00:09:28.200 –> 00:09:30.100 hand nav here and click on Analytics.

193 - 00:09:31.300 –> 00:09:33.800 To take a look at our new analytics page.

194 - 00:09:35.100 –> 00:09:38.400 Now as you’ve already noticed my account doesn’t

195 - 00:09:38.400 –> 00:09:41.600 have a lot of data. So the first thing I’m going to do is click on

196 00:09:41.600 –> 00:09:42.500 this top bar.

197 - 00:09:43.400 –> 00:09:46.800 To adjust the start date of my data set.

198 - 00:09:46.800 –> 00:09:49.400 So I’m going to just go back. Let’s go with October.

199 - 00:09:49.400 –> 00:09:52.400 That’ll give me more interesting data

200 - 00:09:52.400 –> 00:09:55.100 for you all to look at so I’ll collapse that

201 - 00:09:55.100 –> 00:09:58.900 so I can see a little bit better and now here I have a visualization

202 - 00:09:58.900 –> 00:10:01.600 within each of these charts

203 - 00:10:01.600 –> 00:10:04.500 and graphs if you click on anyone you’ll

204 - 00:10:04.500 –> 00:10:08.000 see that it’s going to be highlighted with this black border that

205 - 00:10:07.300 –> 00:10:10.200 then allows you to right click

206 - 00:10:10.200 –> 00:10:13.100 and by right-clicking or command click on a Mac

207 - 00:10:13.100 –> 00:10:16.200 you are able to see the data. So the

208 - 00:10:16.200 –> 00:10:19.800 actual data point and then you can also drill up or drill down to

209 - 00:10:19.800 –> 00:10:22.200 see more information so I can drill up to

210 - 00:10:22.200 –> 00:10:22.600 quarter.

211 - 00:10:24.200 –> 00:10:27.200 I can right-click again and I can drill down to the

212 - 00:10:27.200 –> 00:10:29.000 months of that quarter.

213 - 00:10:29.700 –> 00:10:33.200 So it just gives you a little bit more flexibility to adjust

214 - 00:10:32.200 –> 00:10:35.400 how you’re seeing your data and then for

215 - 00:10:35.400 –> 00:10:38.100 anyone here who’s in Excel wizard. If you want

216 - 00:10:38.100 –> 00:10:41.100 to take this data, pull it into your own system and do

217 - 00:10:41.100 –> 00:10:44.600 a little bit more manipulation. You can click this

218 - 00:10:44.600 –> 00:10:47.500 three dot button and Export to CSV

219 - 00:10:47.500 –> 00:10:50.600 or you can view the summary of your data here as well. So

220 - 00:10:50.600 –> 00:10:53.400 that will allow you if you export to CSV to input

221 - 00:10:53.400 –> 00:10:56.400 that data in whatever tool you like best to adjust your

222 - 00:10:56.400 –> 00:10:58.800 **visualizations. However, you see fit. ** 223 - 00:11:00.300 –> 00:11:03.300 I’m going to come up here to payments along the

224 - 00:11:03.300 –> 00:11:03.600 top.

225 - 00:11:04.400 –> 00:11:07.300 Give that a second to load and I’m going to show off one of

226 - 00:11:07.300 –> 00:11:09.400 our Merchants favorite charts.

227 - 00:11:10.200 –> 00:11:13.100 Once again for the sake of getting a little bit more

228 - 00:11:13.100 –> 00:11:16.300 interesting data, I’m going to back this up just get a slightly

229 - 00:11:16.300 –> 00:11:17.600 wider date range.

230 - 00:11:18.800 –> 00:11:21.400 And then scrolling down. I have

231 - 00:11:21.400 –> 00:11:24.700 GMV by payment type. This is a fan favorite

232 - 00:11:24.700 –> 00:11:27.700 visualization that we offer in the Analytics Tab

233 - 00:11:27.700 –> 00:11:30.600 and what this is going to show you is exactly that

234 - 00:11:30.600 –> 00:11:33.600 your GMV broken down by payment type.

235 - 00:11:33.600 –> 00:11:36.300 So here you’ll be able to see the percentage of

236 - 00:11:36.300 –> 00:11:39.900 orders coming through via Visa Mastercard

237 - 00:11:39.900 –> 00:11:42.000 Amex discover, you know, we’ve got

238 - 00:11:42.100 –> 00:11:45.600 our big four credit cards here. But also if you’re using any

239 - 00:11:45.600 –> 00:11:48.100 alternative payment methods or APMs you’ll see

240 - 00:11:48.100 –> 00:11:51.600 those listed as well. So for most of our Merchants they

241 - 00:11:51.600 –> 00:11:54.700 are using at least one APM, you might see AfterPay

242 - 00:11:54.700 –> 00:11:57.500 or Affirm or Klarna listed here as well

243 - 00:11:57.500 –> 00:12:00.200 and our users find this to be a really useful way

244 - 00:12:00.200 –> 00:12:02.300 to just see where their business is coming from.

245 - 00:12:03.100 –> 00:12:06.400 Okay, so we’ve covered a lot I’m going

246 - 00:12:06.400 –> 00:12:09.800 to pause here really quickly if you have any questions so far now is

247 - 00:12:09.800 –> 00:12:11.500 a great time to drop them into the chat

248 - 00:12:21.100 –> 00:12:24.300 Not seeing any questions yet. So I’m hoping

249 - 00:12:24.300 –> 00:12:24.900 you’re all with me.

250 - 00:12:27.900 –> 00:12:30.900 Funding history and accumulation. All

251 - 00:12:30.900 –> 00:12:33.300 right. So for funding history, we’re going

252 - 00:12:33.300 –> 00:12:34.900 to see that in just a couple of

253 - 00:12:36.600 –> 00:12:39.100 sections so we will come back to that. But Taronay if

254 - 00:12:39.100 –> 00:12:42.500 you want to answer Jason’s question in chat, that would be awesome.

255 - 00:12:43.900 –> 00:12:46.100 All right, so moving down the line.

256 - 00:12:47.200 –> 00:12:48.000 Don’t worry, Jason.

257 - 00:12:49.100 –> 00:12:49.800 That’s you’re plenty patient.

258 - 00:12:50.500 –> 00:12:53.100 I’m glad that you’ve got questions that makes me

259 - 00:12:53.100 –> 00:12:56.600 happy. It means people are listening to me and I’m not just screaming into

260 - 00:12:56.600 –> 00:13:00.100 a void. So, thank you. All right.

261 - 00:13:01.100 –> 00:13:03.600 API failure notifications

262 - 00:13:06.100 –> 00:13:09.100 Nathaniel I’m gonna have Taronay also respond to

263 - 00:13:09.100 –> 00:13:12.300 your question via chat. I can show

264 - 00:13:12.300 –> 00:13:14.900 you where the APIs are.

265 - 00:13:17.300 –> 00:13:20.900 Later on in the presentation that’s going to be under admin. But

266 - 00:13:20.900 –> 00:13:23.300 I’m gonna let tear and I take that question just

267 - 00:13:23.300 –> 00:13:26.300 to make sure that we’re getting you exactly the right answer.

268 - 00:13:27.400 –> 00:13:30.600 Okay, so we’re gonna move on then to

269 - 00:13:30.600 –> 00:13:33.300 check out. So using the left hand

270 - 00:13:33.300 –> 00:13:36.800 now here again clicking on checkout. This takes us to our

271 - 00:13:36.800 –> 00:13:37.800 checkout configuration.

272 - 00:13:39.700 –> 00:13:40.100 and

273 - 00:13:41.100 –> 00:13:44.400 here we’re able to do a handful of things. So on this first page

274 - 00:13:44.400 –> 00:13:47.400 check out configuration. I’m able to adjust the look

275 - 00:13:47.400 –> 00:13:50.700 and feel of the checkout UI itself. So if

276 - 00:13:50.700 –> 00:13:53.100 you like us have gone through for example

277 - 00:13:53.100 –> 00:13:56.700 a Rebrand you can click replace here drop in

278 - 00:13:56.700 –> 00:13:59.400 a new logo and you’ll have a new

279 - 00:13:59.400 –> 00:14:02.100 logo ready to roll whenever you do make a

280 - 00:14:02.100 –> 00:14:05.700 change within this UI you’re gonna see we’ve got a little

281 - 00:14:05.700 –> 00:14:08.300 bar up here that shows that we have one

282 - 00:14:08.300 –> 00:14:11.300 unsaved change and then we’ve got two buttons to

283 - 00:14:11.300 –> 00:14:14.500 choose to save or discard that change. I love

284 - 00:14:14.500 –> 00:14:17.200 the Giant Bolt logo, but I’m not going to save it because this is

285 - 00:14:17.200 –> 00:14:20.500 not technically my store to play around with so I’ll

286 - 00:14:20.500 –> 00:14:23.500 go ahead and discard that change but it’s a great feature to let

287 - 00:14:23.500 –> 00:14:26.400 you know if you have made any changes that haven’t yet been saved.

288 - 00:14:27.900 –> 00:14:30.300 Scrolling down then we’ve got some

289 - 00:14:30.300 –> 00:14:33.300 checkout UI options. So do you want the lock

290 - 00:14:33.300 –> 00:14:36.300 icon display? Do you want discount codes or

291 - 00:14:36.300 –> 00:14:39.200 the side cart, which would allow users to

292 - 00:14:39.200 –> 00:14:42.600 preview their cart details while they’re browsing their storefront. All

293 - 00:14:42.600 –> 00:14:45.700 of those are available is toggles on and off within checkout

294 - 00:14:45.700 –> 00:14:46.000 UI.

295 - 00:14:46.900 –> 00:14:48.700 under shipping options we’ve got

296 - 00:14:49.700 –> 00:14:52.300 All of the expected shipping options. Do you want to ship

297 - 00:14:52.300 –> 00:14:55.000 outside of the US or only to us PO Boxes?

298 - 00:14:55.800 –> 00:14:58.900 Military post offices etc. Those options

299 - 00:14:58.900 –> 00:14:59.500 are all here.

300 00:15:00.500 –> 00:15:03.300 We’ve got delivery note order notes input

301 - 00:15:03.300 –> 00:15:06.200 and SMS shipping updates and then

302 - 00:15:06.200 –> 00:15:09.500 payment here we’ve got things like terms and conditions or

303 - 00:15:09.500 –> 00:15:10.900 require billing zip code.

304 - 00:15:11.600 –> 00:15:15.000 So we’ve got all of those ready for

305 - 00:15:14.100 –> 00:15:18.000 you to adjust here within this

306 - 00:15:17.300 –> 00:15:20.400 view. You’re also able to adjust your

307 - 00:15:20.400 –> 00:15:23.300 abandoned or view your abandoned carts and adjust them Shopper

308 - 00:15:23.300 –> 00:15:26.400 notifications. We’re going to skip those for today and instead

309 - 00:15:26.400 –> 00:15:28.800 we’re going to hop over to analytics and tracking.

310 - 00:15:29.600 –> 00:15:32.900 Most of our Merchants use another

311 - 00:15:32.900 –> 00:15:35.500 third-party Analytics tool of some sort

312 - 00:15:35.500 –> 00:15:38.300 to track traffic across their website.

313 - 00:15:38.300 –> 00:15:41.600 So here is where you would input either a Google analytics

314 - 00:15:41.600 –> 00:15:44.400 tracking ID or Facebook pixel to track

315 - 00:15:44.400 –> 00:15:47.400 the users on their journey and gather your metrics

316 - 00:15:47.400 –> 00:15:47.700 here.

317 - 00:15:48.700 –> 00:15:49.100 All right.

318 - 00:15:50.400 –> 00:15:53.300 I’m gonna take another quick pause just review

319 - 00:15:53.300 –> 00:15:54.100 the chat.

320 - 00:15:58.100 –> 00:16:01.700 Alright, so it looks like we’re doing some DM

321 - 00:16:01.700 –> 00:16:02.900 follow-up on.

322 - 00:16:03.800 –> 00:16:05.300 old system Analytics

323 - 00:16:09.100 –> 00:16:12.100 All right, but I think we’re good to

324 - 00:16:12.100 –> 00:16:14.500 continue on so with that.

325 - 00:16:15.500 –> 00:16:17.200 Let’s look at transactions.

326 - 00:16:18.600 –> 00:16:21.100 Transactions is my favorite page. I think we’ve done a really

327 - 00:16:21.100 –> 00:16:24.100 great job of refreshing this a lot

328 - 00:16:24.100 –> 00:16:27.400 of the same functionality that you’re used to is still here. So things

329 - 00:16:27.400 –> 00:16:30.500 like being able to sort by clicking column headers

330 - 00:16:30.500 –> 00:16:33.200 that’s still in place the filters that you would

331 - 00:16:33.200 –> 00:16:36.400 expect to see by status. I order total by dates

332 - 00:16:36.400 –> 00:16:39.500 created or by payment type those are still in place. And then

333 - 00:16:39.500 –> 00:16:42.300 we do have this button here to create payment for a

334 - 00:16:42.300 –> 00:16:43.900 back office order if you need to use that.

335 - 00:16:44.800 –> 00:16:46.100 We also have our search bar.

336 - 00:16:46.900 –> 00:16:48.100 So I’m going to search for.

337 - 00:16:49.700 –> 00:16:52.300 An order from Taronay and just like

338 - 00:16:52.300 –> 00:16:55.600 before if you want more details on a specific transaction. All you

339 - 00:16:55.600 –> 00:16:58.200 have to do is click on that transaction. So I’ll

340 - 00:16:58.200 –> 00:17:00.100 go ahead and pull this one up.

341 - 00:17:00.900 –> 00:17:03.800 And here we have first of all our timeline,

342 - 00:17:03.800 –> 00:17:06.900 we talked a little bit about the timeline before this timeline

343 - 00:17:06.900 –> 00:17:07.700 is going to show you.

344 - 00:17:08.900 –> 00:17:11.300 Most recent at the top what’s happening with

345 - 00:17:11.300 –> 00:17:14.100 this transaction and where it is within its cycle. So in

346 - 00:17:14.100 –> 00:17:17.200 this case this transactions from the end of last year,

347 - 00:17:17.200 –> 00:17:20.900 so it’s pretty stale pretty old, but we can see this

348 - 00:17:20.900 –> 00:17:23.400 was payment was captured both settled

349 - 00:17:23.400 –> 00:17:27.300 the order and then both funded the order in that

350 - 00:17:26.300 –> 00:17:29.500 order. So we have that information here.

351 - 00:17:30.300 –> 00:17:33.500 We can scroll down and then see a little bit of our payment method

352 - 00:17:33.500 –> 00:17:36.500 and we have our order summary including the coupon code

353 - 00:17:36.500 –> 00:17:38.200 that was used for this particular order.

354 - 00:17:39.500 –> 00:17:43.000 Then when we come down to the very bottom we

355 - 00:17:42.100 –> 00:17:45.400 have what is my favorite feature of the

356 - 00:17:45.400 –> 00:17:48.200 dashboard? I think probably my favorite feature which

357 - 00:17:48.200 –> 00:17:51.500 is our risk scoring risk scoring is available to

358 - 00:17:51.500 –> 00:17:54.500 all of our Merchants whether you’re using our risks product

359 - 00:17:54.500 –> 00:17:57.200 or not, whether you’re using fraud protection with

360 - 00:17:57.200 –> 00:18:01.000 Bolt or not, you will always have access to our risk score and our

361 - 00:18:00.300 –> 00:18:03.100 risk score is exactly that it is a

362 - 00:18:03.100 –> 00:18:06.300 numerical value that we assign to indicate how

363 - 00:18:06.300 –> 00:18:09.800 risky we think is particular order is so

364 - 00:18:09.800 –> 00:18:12.100 in this case we can see Taronay is sitting here

365 - 00:18:12.100 –> 00:18:15.500 at a nice green 39. We do not think Taronay as

366 - 00:18:15.500 –> 00:18:18.200 a risky order which is great for her and we can

367 - 00:18:18.200 –> 00:18:22.300 see that this scale runs from zero up to 999. So,

368 - 00:18:22.300 –> 00:18:25.200 of course the higher the number the higher the risk we think

369 - 00:18:25.200 –> 00:18:28.700 is associated with that order. So this one

370 - 00:18:28.700 –> 00:18:30.500 was in the green we’re feeling pretty confident.

371 - 00:18:32.300 –> 00:18:35.100 And Nathaniel, I

372 - 00:18:35.100 –> 00:18:37.600 will click on The View to details in just one second.

373 - 00:18:38.500 –> 00:18:41.800 Thank you for that reminder. So moving down

374 - 00:18:41.800 –> 00:18:44.800 in this view we do see this was indemnified

375 - 00:18:44.800 –> 00:18:47.600 for Fran. So we’ve got a green check there. We did

376 - 00:18:47.600 –> 00:18:50.600 not issue a micro authorization. That is normal. Very

377 - 00:18:50.600 –> 00:18:53.500 very few of our transactions have Micro

378 - 00:18:53.500 –> 00:18:54.700 off listed or

379 - 00:18:55.500 –> 00:18:58.500 Sent so this is normal

380 - 00:18:58.500 –> 00:19:01.600 to see that it was not issued. And

381 - 00:19:01.600 –> 00:19:04.300 then the reason that we didn’t issue that micro off is

382 - 00:19:04.300 –> 00:19:07.100 because it was approved. So we knew that this was a good order we felt

383 - 00:19:07.100 –> 00:19:08.700 very confident. There was no need to do that.

384 - 00:19:09.500 –> 00:19:11.400 Then down below we have three.

385 - 00:19:13.300 –> 00:19:16.100 Kind of three data points if you

386 - 00:19:16.100 –> 00:19:20.000 will and those three data points are three reasons

387 - 00:19:19.100 –> 00:19:22.600 that we gave this order the score that we did. So

388 - 00:19:22.600 –> 00:19:25.200 we’ve got address verification card verification and

389 - 00:19:25.200 –> 00:19:28.200 email last used now every order that you

390 - 00:19:28.200 –> 00:19:31.800 click into is likely going to have a different set of three listed here.

391 - 00:19:31.800 –> 00:19:34.600 We’ve got over 200 signals that we evaluate when

392 - 00:19:34.600 –> 00:19:37.100 determining the risk associated with a particular

393 - 00:19:37.100 –> 00:19:40.100 transaction. So you’re just gonna see the things that we think

394 - 00:19:40.100 –> 00:19:43.700 we’re most important in our decision. Now we

395 - 00:19:43.700 –> 00:19:46.200 give this information to you as Merchants because we want you

396 - 00:19:46.200 –> 00:19:49.200 to feel informed we want you to feel empowered we want you to know what

397 - 00:19:49.200 –> 00:19:53.200 we’re taking in and how we’re thinking about orders. However, we

398 - 00:19:52.200 –> 00:19:55.500 do ask that you not share this

399 - 00:19:55.500 –> 00:19:58.100 with your Shoppers directly. We have

400 - 00:19:58.100 –> 00:20:02.200 seen plenty of examples of very Charming Shoppers calling

401 - 00:20:01.200 –> 00:20:05.100 in writing in say hey, why

402 - 00:20:04.100 –> 00:20:07.900 was my order declined? I think it’s legit and

403 - 00:20:07.900 –> 00:20:10.500 they can be very convincing but ask some pretty

404 - 00:20:10.500 –> 00:20:12.400 specific questions and ultimately

405 - 00:20:13.300 –> 00:20:16.700 I just be someone who’s attempting to social engineer you to get

406 - 00:20:16.700 –> 00:20:19.600 insight into how our fraud decisioning works so

407 - 00:20:19.600 –> 00:20:22.800 that they can sneak past the guards next time. So

408 - 00:20:22.800 –> 00:20:25.100 if you do have a shopper that reaches out to you

409 - 00:20:25.100 –> 00:20:28.600 about specifics, please do not share any specifics.

410 - 00:20:28.600 –> 00:20:31.400 You can just indicate our systems

411 - 00:20:31.400 –> 00:20:32.700 felt that this order was

412 - 00:20:33.800 –> 00:20:37.200 either safe or not safe to pass through but don’t

413 - 00:20:36.200 –> 00:20:39.100 give them any details on what we

414 - 00:20:39.100 –> 00:20:42.300 list here, please all right,

415 - 00:20:42.300 –> 00:20:44.100 so that’s risk scoring.

416 - 00:20:45.100 –> 00:20:48.900 We were asked to view details. So when

417 - 00:20:48.900 –> 00:20:50.900 I click into view details I can see.

418 - 00:20:52.800 –> 00:20:55.100 the items that tyranny ordered

419 - 00:20:56.100 –> 00:20:59.600 I don’t know if charity was ready for this level

420 - 00:20:59.600 –> 00:21:02.700 of information, but we

421 - 00:21:02.700 –> 00:21:05.500 had some holiday swag that

422 - 00:21:05.500 –> 00:21:08.400 we were able to order. So this is what tyranny chose

423 - 00:21:08.400 –> 00:21:11.800 to order and then if you scroll down there’s a

424 - 00:21:11.800 –> 00:21:14.300 little bit more, you know, the total

425 - 00:21:14.300 –> 00:21:17.800 customer payment fees assessed and then net Merchant

426 - 00:21:17.800 –> 00:21:19.100 payout listed as well.

427 - 00:21:20.700 –> 00:21:23.300 And then last thing I want to call out

428 - 00:21:23.300 –> 00:21:26.300 on this page is the actions button. So this order as

429 - 00:21:26.300 –> 00:21:29.400 we mentioned is pretty old is from late last year. So there isn’t

430 - 00:21:29.400 –> 00:21:32.200 a lot available to us under actions. But if

431 - 00:21:32.200 –> 00:21:35.900 you haven’t ordered that for example was recently rejected you’re

432 - 00:21:35.900 –> 00:21:39.300 going to see different actions available here that you

433 - 00:21:39.300 –> 00:21:42.200 can take. So an example here might be you could see

434 - 00:21:42.200 –> 00:21:45.200 an option for re-review or if there are disputes you

435 - 00:21:45.200 –> 00:21:48.500 might have dispute actions listed as well in this case based

436 - 00:21:48.500 –> 00:21:51.300 on the age of this transaction. All the options are are

437 - 00:21:51.300 –> 00:21:54.300 simply duplicating issue every issuing a refund or

438 - 00:21:54.300 –> 00:21:57.200 resending emails, but it’s an important way to

439 - 00:21:57.200 –> 00:22:00.400 see what’s available to you and act on whatever

440 - 00:22:00.400 –> 00:22:03.400 you mean may need to do for a specific transaction.

441 - 00:22:05.700 –> 00:22:08.300 All right. I’m going to take a quick second to review the

442 - 00:22:08.300 –> 00:22:11.300 chat. Looks like we’ve got a lot going in here. So I want to make sure that I’m

443 - 00:22:11.300 –> 00:22:12.100 caught up.

444 - 00:22:16.700 –> 00:22:19.400 okay, so Nathaniel it was looking for

445 - 00:22:19.400 –> 00:22:22.100 the skew but it looks like Taronay

446 - 00:22:22.100 –> 00:22:22.400 is

447 - 00:22:24.200 –> 00:22:25.700 taking that feedback.

448 - 00:22:27.300 –> 00:22:30.500 Which is one of the lovely things about having the product manager

449 - 00:22:30.500 –> 00:22:32.200 here in the session.

450 - 00:22:33.300 –> 00:22:37.100 You’re getting you know direct line to a

451 - 00:22:36.100 –> 00:22:38.000 decision maker, which is great.

452 - 00:22:39.700 –> 00:22:42.200 The recommended questions we should have a

453 - 00:22:42.200 –> 00:22:44.300 customer answer if their order is under re-review.

454 - 00:22:45.100 –> 00:22:46.900 interesting question Claudia, so

455 - 00:22:48.500 –> 00:22:51.400 I’m gonna give you my best

456 - 00:22:51.400 –> 00:22:54.100 answer and then I’m

457 - 00:22:54.100 –> 00:22:57.700 gonna let Taronay chime in if there’s anything else that

458 - 00:22:57.700 –> 00:23:00.600 she wants to add generally speaking when

459 - 00:23:00.600 –> 00:23:04.000 it comes to order re-review what we expect when

460 - 00:23:03.100 –> 00:23:06.500 you’re submitted an order for re-review is that you’ve gotten

461 - 00:23:06.500 –> 00:23:09.600 some other validating information some other like

462 - 00:23:09.600 –> 00:23:12.800 information that provides confirmation to you that the

463 - 00:23:12.800 –> 00:23:16.000 Shopper is who they say they are so for example, if

464 - 00:23:15.700 –> 00:23:18.400 you know that it’s a shopper that you’ve seen before

465 - 00:23:18.400 –> 00:23:21.800 but this time they’re ordering a gift for a friend and

466 - 00:23:21.800 –> 00:23:24.800 they write in and they tell you that kind of information then that

467 - 00:23:24.800 –> 00:23:27.300 would be a good reason to do a review if

468 - 00:23:27.300 –> 00:23:30.300 they’re if they had Shopper history prior to you joining

469 - 00:23:30.300 –> 00:23:33.500 Bolt, that would be a good reason to write in for review.

470 - 00:23:35.300 –> 00:23:38.300 That’s kind of what we’re looking for. If there’s

471 - 00:23:38.300 –> 00:23:41.500 just anything that you know about that Shopper and

472 - 00:23:41.500 –> 00:23:44.800 why you think they’re legitimate outside of

473 - 00:23:44.800 –> 00:23:47.300 what the system and what our data signals would

474 - 00:23:47.300 –> 00:23:50.700 show us. That’s the kind of information. We love to see in a

475 - 00:23:50.700 –> 00:23:51.400 Brief Review request.

476 - 00:23:52.500 –> 00:23:55.100 I hope that helps turn if you have any other details that

477 - 00:23:55.100 –> 00:23:57.700 you want to add in in chat, please feel free to do so.

478 - 00:23:59.400 –> 00:24:02.800 All right. So that’s it for transaction details. We’re

479 - 00:24:02.800 –> 00:24:05.800 going to back out and there had been a question earlier as

480 - 00:24:05.800 –> 00:24:08.200 well about.

481 - 00:24:09.400 –> 00:24:12.000 I think funding and statements.

482 - 00:24:13.200 –> 00:24:15.100 So, let me just pull this up.

483 - 00:24:16.200 –> 00:24:17.000 bunny in history

484 - 00:24:18.800 –> 00:24:21.900 when we’re looking for funding history that’s going to be under Bank transfers.

485 - 00:24:21.900 –> 00:24:24.500 I’m not going to click on that because I don’t actually

486 - 00:24:24.500 –> 00:24:26.700 know what that might show you that could be, potentially.

487 - 00:24:29.800 –> 00:24:32.400 A confidential sensitive that might

488 - 00:24:32.400 –> 00:24:35.500 be potentially sensitive here. And then we also have our statements

489 - 00:24:35.500 –> 00:24:38.400 available for you here. So with statements you

490 - 00:24:38.400 –> 00:24:41.400 can click in on this Arrow to see the daily statements.

491 - 00:24:42.600 –> 00:24:45.400 And then you can also download via PDF

492 - 00:24:45.400 –> 00:24:48.400 or CSV for monthly statements and

493 - 00:24:48.400 –> 00:24:51.800 then our drop down here allows you to select the year.

494 - 00:24:55.500 –> 00:24:57.600 accumulated funds that haven’t been transferred

495 - 00:24:58.600 –> 00:24:59.200 yet.

496 - 00:25:00.100 –> 00:25:02.200 I’m gonna let Taronay take this one as well.

497 - 00:25:04.400 –> 00:25:07.100 Because I’m not I’m not

498 - 00:25:07.100 –> 00:25:10.000 sure on that particular. I don’t have a quick answer for you.

499 - 00:25:10.800 –> 00:25:13.400 So I’ll let her and I take that question on where to

500 - 00:25:13.400 –> 00:25:16.700 find accumulated funds that have not yet been transferred.

501 - 00:25:18.200 –> 00:25:21.300 All right, we’re gonna take another beat here if anyone has

502 - 00:25:21.300 –> 00:25:24.300 any other questions about the transactions page now is

503 - 00:25:24.300 –> 00:25:25.900 a great time to drop them in.

504 - 00:25:41.600 –> 00:25:41.900 Okay.

505 00:25:43.900 –> 00:25:46.200 With that we’ll go ahead and move on

506 - 00:25:46.200 –> 00:25:48.000 to fraud to protection.

507 - 00:25:49.400 –> 00:25:49.700 So

508 - 00:25:51.400 –> 00:25:54.500 Most of what you’re going to see in this screen is only relevant to

509 - 00:25:54.500 –> 00:25:57.200 users to Merchants who are using our fraud protection

510 - 00:25:57.200 –> 00:26:00.300 services. However, there is one feature that is

511 - 00:26:00.300 –> 00:26:03.800 available to everyone so we’ll start there to make it broadly applicable

512 - 00:26:03.800 –> 00:26:06.600 and that is our block list. So

513 - 00:26:06.600 –> 00:26:10.000 down here at the bottom. You can add either IP

514 - 00:26:09.400 –> 00:26:12.400 addresses or email addresses to your block list.

515 - 00:26:12.400 –> 00:26:15.200 When you add either of those data points to your

516 - 00:26:15.200 –> 00:26:18.100 block list, what that’s going to do is indicate to us that as soon

517 - 00:26:18.100 –> 00:26:21.300 as we see that email or IP address pop up. We’re going

518 - 00:26:21.300 –> 00:26:24.300 to reject that transaction so we won’t be going through

519 - 00:26:24.300 –> 00:26:27.800 a fraud decisioning. We won’t be doing authorization. We’re

520 - 00:26:27.800 –> 00:26:30.200 not going to check to see if the card has sufficient funds.

521 - 00:26:30.200 –> 00:26:33.600 We’re just going to immediately bypass all of that and stop

522 - 00:26:33.600 –> 00:26:36.400 the transaction. Now the use case here would

523 - 00:26:36.400 –> 00:26:39.400 be if for example you have someone who is coming in

524 - 00:26:39.400 –> 00:26:42.300 and buys up all of your sale merchandise and

525 - 00:26:42.300 –> 00:26:45.800 then resells it on a resale site and you’re not

526 - 00:26:45.800 –> 00:26:48.300 happy about that. You might choose

527 - 00:26:48.300 –> 00:26:50.200 to block list them here.

528 - 00:26:51.200 –> 00:26:54.400 So again, this is a feature that’s available whether or not you’re using

529 - 00:26:54.400 –> 00:26:56.700 our fraud services. That’s the block list.

530 - 00:26:57.700 –> 00:27:00.300 Coming back up to the top. We have two other things that

531 - 00:27:00.300 –> 00:27:03.300 I want to call out for users who do use our fraud protection

532 - 00:27:03.300 –> 00:27:07.700 services. So this first box is our order rejection. If

533 - 00:27:06.700 –> 00:27:09.500 you want your team to

534 - 00:27:09.500 –> 00:27:12.300 be able to override Bolt’s decisioning to

535 00:27:12.300 –> 00:27:15.500 say you said it was fraud, but I’m going to push it through. Anyways,

536 00:27:15.500 –> 00:27:19.100 you can go ahead and toggle this button on and

537 00:27:18.100 –> 00:27:21.600 that will give your within the

538 00:27:21.600 –> 00:27:26.100 account that will give access to override rejected

539 00:27:24.100 –> 00:27:27.500 transactions. And then

540 00:27:27.500 –> 00:27:30.200 the rejection override window is simply an indication of

541 00:27:30.200 –> 00:27:33.800 how much time you want your team to have to make that decision. So

542 00:27:33.800 –> 00:27:36.400 this has to be between zero and 96 hours.

543 00:27:36.400 –> 00:27:39.300 It really just depends on how much time you

544 00:27:39.300 –> 00:27:42.600 want your team to be able to have to look at an order

545 00:27:42.600 –> 00:27:44.300 and make that assessment on their own.

546 00:27:45.400 –> 00:27:49.000 And then we have our allow list opposite of

547 00:27:48.100 –> 00:27:51.500 the block list are allow list is a list

548 00:27:51.500 –> 00:27:55.500 of email addresses and IP addresses that you want to always every

549 00:27:54.500 –> 00:27:57.200 time approve. So there are

550 00:27:57.200 –> 00:28:01.000 two important things to keep in mind with an allow list first

551 00:28:00.200 –> 00:28:03.400 thing because we’re not going to run our

552 00:28:03.400 –> 00:28:06.200 fraud decisioning algorithms. We’re not going through any of

553 00:28:06.200 –> 00:28:09.500 that process that does mean you do not pay the

554 00:28:09.500 –> 00:28:13.100 Bold fraud fee, but second thing

555 00:28:12.100 –> 00:28:15.600 because you’re we’re not using our

556 - 00:28:15.600 –> 00:28:18.700 fraud engine to determine the likelihood of

557 - 00:28:18.700 –> 00:28:21.300 fraud of that transaction from an allow

558 - 00:28:21.300 –> 00:28:24.200 list that also means we’re not going to indemnify for

559 - 00:28:24.200 –> 00:28:27.400 front. So in the unlikely event that you’ve added someone

560 - 00:28:27.400 –> 00:28:30.700 to an allow list that does end up charging back

561 - 00:28:30.700 –> 00:28:33.900 or disputing that transaction. We

562 - 00:28:33.900 –> 00:28:36.100 won’t be able to indemnify that for fraud because

563 - 00:28:36.100 –> 00:28:39.500 we haven’t been able to run that fraud engine gather those

564 - 00:28:39.500 –> 00:28:42.500 signals and make a determination. So this is a very useful

565 - 00:28:42.500 –> 00:28:44.300 tool but use it with care.

566 - 00:28:45.400 –> 00:28:46.600 those two things in mind

567 - 00:28:49.500 –> 00:28:50.900 all right, we’ve got

568 - 00:28:51.800 –> 00:28:54.500 a couple questions that

569 - 00:28:54.500 –> 00:28:57.100 popped up so cloudy will we still need

570 - 00:28:57.100 –> 00:29:00.200 to chat in if a declined order was reported as fraud already

571 - 00:29:00.200 –> 00:29:04.300 simply blocked the email so if

572 - 00:29:03.300 –> 00:29:05.000 you want

573 - 00:29:06.700 –> 00:29:07.900 Make sure I’ve got this right.

574 - 00:29:12.100 –> 00:29:13.800 if you want

575 - 00:29:18.500 –> 00:29:19.600 Sorry thinking.

576 - 00:29:23.900 –> 00:29:26.000 If an order was reported as fraud, you don’t

577 - 00:29:26.500 –> 00:29:29.100 have to block the email you can if you

578 - 00:29:29.100 –> 00:29:31.300 want to make sure that they just don’t come up again.

579 - 00:29:32.100 –> 00:29:32.300 but

580 - 00:29:34.300 –> 00:29:37.100 that’s my personal recommendation. Taronay please

581 - 00:29:37.100 –> 00:29:40.600 chime in here if you have a different take. Taronay: My personal recommendation

582 - 00:29:40.600 –> 00:29:43.300 would be not to block someone just because they’ve come

583 - 00:29:43.300 –> 00:29:46.700 up as fraudulent once because they’re always is the very

584 - 00:29:46.700 –> 00:29:49.400 slight but technically still possible chance that that

585 - 00:29:49.400 –> 00:29:53.100 may have been, you know a mistake. Maybe

586 - 00:29:52.100 –> 00:29:55.900 they did have a card that was legitimately lost

587 - 00:29:55.900 –> 00:29:58.300 or stolen and then because that was a saved

588 - 00:29:58.300 –> 00:30:01.400 card number. They tried to make another purchase with that card because it

589 - 00:30:01.400 –> 00:30:04.200 was just what was saved and we wouldn’t want something like that

590 - 00:30:04.200 –> 00:30:07.200 stopping them from ever purchasing on your site. It’s really

591 - 00:30:07.200 –> 00:30:10.300 if you got like repeated bad behavior that we would want

592 - 00:30:10.300 –> 00:30:13.600 you to add someone to that block list. But in

593 - 00:30:13.600 –> 00:30:16.500 that case you do not have to use the chat functionality. You

594 - 00:30:16.500 –> 00:30:19.100 don’t have to open a support ticket to add someone

595 - 00:30:19.100 –> 00:30:22.000 to the block list. You can do so directly yourself. Let me

596 - 00:30:22.100 –> 00:30:25.200 know and chat if that did not answer your question. I’m hoping that

597 - 00:30:25.200 –> 00:30:25.300 did.

598 - 00:30:26.700 –> 00:30:29.200 All right. Next question

599 - 00:30:29.200 –> 00:30:32.500 of the credit card is entered manually in Bolt has the transaction been

600 - 00:30:32.500 –> 00:30:35.700 checked for fraud. I’m going to ask a clarifying

601 - 00:30:35.700 –> 00:30:38.000 question here. Are you referring to

602 - 00:30:38.200 –> 00:30:40.400 the create payment button?

603 - 00:30:42.500 –> 00:30:43.400 If so.

604 - 00:30:45.700 –> 00:30:48.700 If so, I’m gonna actually defer to

605 - 00:30:48.700 –> 00:30:52.200 Taronay. Anyways, my

606 - 00:30:51.200 –> 00:30:54.700 understanding is that we do

607 - 00:30:54.700 –> 00:30:56.900 have some level of

608 - 00:30:58.700 –> 00:31:01.300 so generally speaking what we’re looking at

609 - 00:31:01.300 –> 00:31:02.700 when a user is

610 - 00:31:03.600 –> 00:31:06.400 Submitting a transaction. It’s not just you know

611 - 00:31:06.400 –> 00:31:09.200 the credit card or does the CVV match. We’re actually

612 - 00:31:09.200 –> 00:31:12.200 looking at a whole bunch of different things. Like are they copying and

613 - 00:31:12.200 –> 00:31:15.500 pasting and so we don’t have the same fraud signals when

614 - 00:31:15.500 –> 00:31:18.500 you use a back office order and just click the create

615 - 00:31:18.500 –> 00:31:19.000 payment button?

616 - 00:31:20.100 –> 00:31:20.500 however

617 - 00:31:23.100 –> 00:31:26.700 I believe that there is some level of indemnification. I’m

618 - 00:31:26.700 –> 00:31:29.400 not positive will circle back with an

619 - 00:31:29.400 –> 00:31:30.000 answer on that one.

620 - 00:31:31.900 –> 00:31:32.600 All right.

621 - 00:31:34.900 –> 00:31:36.600 anything else

622 - 00:31:38.600 –> 00:31:41.900 on transactions or on fraud

623 - 00:31:41.900 –> 00:31:42.000 protection

624 - 00:31:43.300 –> 00:31:46.600 and give folks another couple of seconds to answer to ask not

625 - 00:31:46.600 –> 00:31:48.900 to answer to ask any other questions that they might have in chat.

626 - 00:31:59.600 –> 00:32:02.100 Okay, I think we’re good

627 - 00:32:02.100 –> 00:32:05.300 for now. So we will move on going down the line on

628 - 00:32:05.300 –> 00:32:07.300 the left hand side to payments.

629 - 00:32:08.300 –> 00:32:11.300 Here we are in payments. This is where you will be able to see

630 - 00:32:11.300 –> 00:32:14.400 and manage your payment stock. So

631 - 00:32:14.400 –> 00:32:17.300 we’ve got our standard Bolt payments here. I would

632 - 00:32:17.300 –> 00:32:20.400 be able to click in and manage payments there. And then also

633 - 00:32:20.400 –> 00:32:23.600 we have our APMs (our alternative payment methods) listed

634 - 00:32:23.600 –> 00:32:26.100 Out Below now in the case of My Demo store.

635 - 00:32:26.100 –> 00:32:29.100 I’m not using any of those. But if I wanted to I would be

636 - 00:32:29.100 –> 00:32:32.900 able to Simply click on any one and configure

637 - 00:32:32.900 –> 00:32:33.600 those here.

638 - 00:32:35.100 –> 00:32:38.500 And then finally, we have Administration. This is

639 - 00:32:38.500 –> 00:32:40.700 an important time to call out that.

640 - 00:32:41.500 –> 00:32:44.300 each and every one of you has some level of access to your own

641 - 00:32:44.300 –> 00:32:47.100 Merchant dashboard that may be admin access where you

642 - 00:32:47.100 –> 00:32:50.300 can see absolutely and free thing or maybe a more

643 - 00:32:50.300 –> 00:32:53.200 restricted level of access in which case you may

644 - 00:32:53.200 –> 00:32:56.700 not see all of the features that we have listed here because

645 - 00:32:56.700 –> 00:32:59.400 you may not have permission to see those

646 - 00:32:59.400 –> 00:33:02.200 so keep that in mind

647 - 00:33:02.200 –> 00:33:03.000 as we go through this

648 - 00:33:04.300 –> 00:33:07.600 If you don’t see everything, it’s probably with good reason first up.

649 - 00:33:07.600 –> 00:33:11.000 We have our business info. This is just going to be you know, General name

650 - 00:33:10.400 –> 00:33:12.800 address support contact information.

651 - 00:33:14.100 –> 00:33:17.200 Then under Access Control users and permissions. This is

652 - 00:33:17.200 –> 00:33:20.400 where you would add new users to your Merchant dashboard account.

653 - 00:33:20.400 –> 00:33:23.800 So if a new team member joins and you want them to access you

654 - 00:33:23.800 –> 00:33:25.700 would do so by using the invite button here.

655 - 00:33:27.100 –> 00:33:31.100 And then down at the bottom, we have our developers. So all

656 - 00:33:30.100 –> 00:33:34.600 of this information APIs and webhooks.

657 - 00:33:33.600 –> 00:33:37.100 This is all developer information

658 - 00:33:36.100 –> 00:33:39.400 for most of

659 - 00:33:39.400 –> 00:33:42.700 our users. This isn’t going to be something that

660 - 00:33:42.700 –> 00:33:45.300 they spend much time with but it is

661 - 00:33:45.300 –> 00:33:46.000 there for you.

662 - 00:33:47.200 –> 00:33:49.600 Claudia is there a way to export the user list?

663 - 00:33:51.300 –> 00:33:54.200 That’s a great question. I do not see an easy way.

664 - 00:33:55.500 –> 00:33:58.800 But Taronay if

665 - 00:33:58.800 –> 00:34:01.500 there’s something that I’ve missed on exporting the user list, let

666 - 00:34:01.500 –> 00:34:01.600 me know.

667 - 00:34:02.500 –> 00:34:03.000 and then

668 - 00:34:04.700 –> 00:34:05.400 Claudia I do have

669 - 00:34:06.300 –> 00:34:09.900 One exciting feature that I’m gonna flag to

670 - 00:34:09.900 –> 00:34:12.100 you when we get back to our slides in just

671 - 00:34:12.100 –> 00:34:15.300 a second that isn’t exporting a user list,

672 - 00:34:15.300 –> 00:34:18.300 but is sort of related in terms of user control.

673 - 00:34:19.800 –> 00:34:22.500 Okay, the last thing that

674 - 00:34:22.500 –> 00:34:25.400 I want to call out within the UI here

675 - 00:34:25.400 –> 00:34:28.400 is down at the very bottom. We do have two

676 - 00:34:28.400 –> 00:34:31.400 key buttons available to us. So first

677 - 00:34:31.400 –> 00:34:35.800 of all, we have a link to our documentation as the

678 - 00:34:35.800 –> 00:34:38.600 manager of the customer education team. I feel really strongly

679 - 00:34:38.600 –> 00:34:41.200 that our documentation that my team writes is excellent if you

680 - 00:34:41.200 –> 00:34:44.200 have feedback, I welcome it certainly but if you’re

681 - 00:34:44.200 –> 00:34:47.400 walking away from this thinking okay, that was a lot of changes that

682 - 00:34:47.400 –> 00:34:50.700 we talked about. I need a refresher you can always click here to

683 - 00:34:50.700 –> 00:34:53.600 open up our documentation and learn about the new dashboard

684 - 00:34:53.600 –> 00:34:56.200 there. And then also we have our button to

685 - 00:34:56.200 –> 00:34:59.300 switch to the Legacy dashboard. So this will

686 - 00:34:59.300 –> 00:35:02.500 allow you to toggle back to our Legacy dashboard. We’re planning

687 - 00:35:02.500 –> 00:35:05.300 on keeping our Legacy dashboard alive for good few months.

688 - 00:35:05.300 –> 00:35:08.500 So if there is anything that’s not working quite the way you expect it

689 - 00:35:08.500 –> 00:35:12.400 to certainly give us that feedback. We’re really very

690 - 00:35:11.400 –> 00:35:14.200 eager to hear your feedback to understand

691 - 00:35:14.200 –> 00:35:17.100 what’s not working with the new experience, but you

692 - 00:35:17.100 –> 00:35:19.600 do still have that backup with the

693 - 00:35:19.800 –> 00:35:22.900 legacy dashboard for a little while yet.

694 - 00:35:25.700 –> 00:35:29.300 So with that we’re going to talk very briefly about

695 - 00:35:28.300 –> 00:35:31.400 what’s next as I

696 - 00:35:31.400 –> 00:35:34.400 mentioned Bolt is going to continue to maintain both versions of

697 - 00:35:34.400 –> 00:35:37.100 the dashboard for the next few months. So you

698 - 00:35:37.100 –> 00:35:41.000 can revert whenever you need to that Legacy experience to

699 - 00:35:40.100 –> 00:35:44.300 get anything accomplished that you may need. There are

700 - 00:35:44.300 –> 00:35:47.400 currently three key features that we have called out.

701 - 00:35:48.300 –> 00:35:51.400 That are only available in the Legacy dashboard

702 - 00:35:51.400 –> 00:35:54.400 and do require that reversion in

703 - 00:35:54.400 –> 00:35:57.800 order to use. So those are the route integration store

704 - 00:35:57.800 –> 00:36:00.600 highlights and add-ons. Now when you

705 - 00:36:00.600 –> 00:36:04.500 have these within your store using

706 - 00:36:03.500 –> 00:36:06.400 the Merchant Dashboard the new version

707 - 00:36:06.400 –> 00:36:09.700 versus the old version will not affect your Shopper experience.

708 - 00:36:09.700 –> 00:36:12.400 If you have it set up your Shoppers continue to

709 - 00:36:12.400 –> 00:36:15.600 see everything in the same way nothing should change but if

710 - 00:36:15.600 –> 00:36:18.700 you want to manage any configuration make any

711 - 00:36:18.700 –> 00:36:21.300 changes to these features, you will want to revert to

712 - 00:36:21.300 –> 00:36:24.600 the Legacy dashboard to do that work for now. We

713 - 00:36:24.600 –> 00:36:27.100 have all of these things on our roadmap. So we

714 - 00:36:27.100 –> 00:36:29.700 will be adding those to the new dashboard very soon.

715 - 00:36:30.400 –> 00:36:33.200 And then in terms of some things that

716 - 00:36:33.200 –> 00:36:36.900 are on the horizon that we’re really excited about we do have subscription

717 - 00:36:36.900 –> 00:36:39.400 analytics that will be coming out for our

718 - 00:36:39.400 –> 00:36:41.400 M2 subscription merchants.

719 - 00:36:42.800 –> 00:36:45.600 Because subscriptions are currently only available for M2

720 - 00:36:45.600 –> 00:36:48.100 Merchants. This isn’t going to be for everyone but if you are using

721 - 00:36:48.100 –> 00:36:51.800 subscriptions analytics are coming and then Claudia, the

722 - 00:36:51.800 –> 00:36:54.200 thing that I wanted to call it for you is the

723 - 00:36:54.200 –> 00:36:57.900 dashboard activity log. So this is something that we’ve heard requested

724 - 00:36:57.900 –> 00:37:00.200 from our Merchants for a long time. We’re really excited

725 - 00:37:00.200 –> 00:37:03.300 to roll this out. The dashboard activity log is going

726 - 00:37:03.300 –> 00:37:06.600 to allow you to see who is making what changes when

727 - 00:37:06.600 –> 00:37:09.600 it’ll be an entire log of activity within

728 - 00:37:09.600 –> 00:37:13.000 the dashboard so that you have a lot more transparency into

729 - 00:37:12.100 –> 00:37:15.200 what’s happening in the Merchant Dashboard from the

730 - 00:37:15.200 –> 00:37:18.400 perspective of how your team uses it. So we’re really

731 - 00:37:18.400 –> 00:37:22.000 excited to roll that out. I think that’s gonna be yes. It’s

732 - 00:37:21.300 –> 00:37:24.100 very exciting. We’ve had

733 - 00:37:24.100 –> 00:37:27.800 a lot of folks ask for this and I can’t wait for it to go live. So

734 - 00:37:27.800 –> 00:37:29.900 that is coming soon.

735 - 00:37:32.100 –> 00:37:32.400 Okay.

736 - 00:37:33.700 –> 00:37:36.500 With that we have our survey.

737 - 00:37:37.300 –> 00:37:40.500 So as I mentioned at the start, we take your feedback

738 - 00:37:40.500 –> 00:37:43.600 really seriously, we use this to decide what content we’re

739 - 00:37:43.600 –> 00:37:46.700 going to bring to you next to make changes to give

740 - 00:37:46.700 –> 00:37:49.300 you the best experience possible. So I would love if

741 - 00:37:49.300 –> 00:37:52.200 you could take one minute. I promise no more than one

742 - 00:37:52.200 –> 00:37:55.400 minute to fill out our quick survey. And while we

743 - 00:37:55.400 –> 00:37:58.400 are doing that and this is a QR code just scan it

744 - 00:37:58.400 –> 00:38:01.200 with your phone. Well, we’re doing that. We’re also going to move on to

745 - 00:38:01.200 –> 00:38:04.400 our open Q&A. So at this point any other

746 - 00:38:04.400 –> 00:38:07.100 questions that haven’t been addressed feel free to pop them

747 - 00:38:07.100 –> 00:38:10.700 into the chat Taronay and I are both here to answer

748 - 00:38:10.700 –> 00:38:13.400 whatever questions you might have

749 - 00:38:13.400 –> 00:38:14.000 lingering.

750 - 00:38:15.100 –> 00:38:15.500 so

751 - 00:38:16.600 –> 00:38:19.100 and it looks like we’ve got one follow-up answer.

752 - 00:38:23.400 –> 00:38:26.600 Great. So on the indemnification for back office orders

753 - 00:38:26.600 –> 00:38:28.500 check in with your CSM.

754 - 00:38:30.300 –> 00:38:30.700 That’s

755 - 00:38:31.800 –> 00:38:34.200 almost always a good answer check in with

756 - 00:38:34.200 –> 00:38:37.900 your CSM. Our CSM team is pretty phenomenal and

757 - 00:38:37.900 –> 00:38:40.400 they are very valuable resources to all

758 - 00:38:40.400 –> 00:38:40.600 of you.

759 - 00:38:41.900 –> 00:38:44.200 I’m just gonna do a quick scroll through make sure there wasn’t

760 - 00:38:44.200 –> 00:38:44.900 anything else.

761 - 00:38:55.500 –> 00:38:58.100 Oh, Susan. Thank you for joining. I’m glad that you

762 - 00:38:58.100 –> 00:38:59.100 had a good time.

763 - 00:39:20.100 –> 00:39:23.400 It looks like there were a couple questions answered in

764 - 00:39:23.400 –> 00:39:24.600 chat directly.

765 - 00:39:26.600 –> 00:39:30.000 not seeing anything else so we’ll stay on the line and for

766 - 00:39:30.900 –> 00:39:33.100 Let’s see. What time is it? We’ll stay on

767 - 00:39:33.100 –> 00:39:36.300 the line for at least another five minutes. If any other questions come through, please

768 - 00:39:36.300 –> 00:39:39.600 ask we are definitely here for you. But if

769 - 00:39:39.600 –> 00:39:42.400 you don’t have any other questions, I just want to thank you for spending

770 - 00:39:42.400 –> 00:39:45.400 your afternoon slash maybe morning

771 - 00:39:45.400 –> 00:39:48.300 with us, depending on where you are in the world. We’re really

772 - 00:39:48.300 –> 00:39:51.600 grateful for your attention your participation in

773 - 00:39:51.600 –> 00:39:54.900 the session and I’m in advance

774 - 00:39:54.900 –> 00:39:57.200 appreciative for the feedback that you left for us. So

775 - 00:39:57.200 –> 00:40:00.200 please if you haven’t finished that survey do so.

776 - 00:40:01.100 –> 00:40:03.600 And we’ll see you next time.