WEBVTT

1
00:00:00.190 --> 00:00:00.945
Hi, I'm Sara.

2
00:00:00.945 --> 00:00:06.232
In this walkthrough I'll show you how to read your Flare messaging analytics, step by step.

3
00:00:06.232 --> 00:00:15.352
By the end you'll know which numbers matter, how to tell a delivery problem from a list problem, and how to see whether your team is keeping up with replies.

4
00:00:16.060 --> 00:00:18.361
Let's start by signing in to Switchboard.

5
00:00:21.763 --> 00:00:24.776
Analytics sits under Flare SMS in the sidebar.

6
00:00:24.776 --> 00:00:32.045
Everything on this page is rolled up across your whole account, every campaign and every conversation together.

7
00:00:32.045 --> 00:00:36.237
If you want one campaign on its own, open that campaign instead.

8
00:00:36.237 --> 00:00:38.267
This is the account level view.

9
00:00:38.973 --> 00:00:41.723
Before you read anything, check the window.

10
00:00:41.723 --> 00:00:49.908
The selector in the top right gives you the last 7 days, 30 days, 90 days, or 6 months, and every chart and table moves with it.

11
00:00:49.908 --> 00:00:58.478
Your choice is kept in the address bar, so you can bookmark a view or send the link on and the other person sees exactly what you saw.

12
00:00:59.178 --> 00:01:01.646
These four tiles are your health check.

13
00:01:01.646 --> 00:01:04.683
Messages sent is outbound volume for the window.

14
00:01:04.683 --> 00:01:06.771
Forty nine over the last 30 days.

15
00:01:06.771 --> 00:01:16.072
Underneath it is the change against the period immediately before this one, the same length, so it's a fair comparison rather than a running total.

16
00:01:16.777 --> 00:01:18.969
Delivery rate is the one to watch.

17
00:01:18.969 --> 00:01:25.544
It's the share of messages the carriers confirmed they delivered, and healthy is 95 percent or better.

18
00:01:25.544 --> 00:01:28.252
Acme is at 96, right where you want to be.

19
00:01:28.252 --> 00:01:34.312
If this number starts sliding, something changed, and in a moment I'll show you where to look.

20
00:01:35.014 --> 00:01:39.597
Response rate is inbound replies measured against delivered messages.

21
00:01:39.597 --> 00:01:47.501
It's a two way engagement number, so if you mostly broadcast in one direction, expect it to sit low and don't chase it.

22
00:01:47.501 --> 00:01:51.619
Opt-outs counts the people who texted stop during this window.

23
00:01:51.619 --> 00:01:54.741
The tile is flagged whenever that's above zero.

24
00:01:54.741 --> 00:01:55.671
Acme has five.

25
00:01:56.373 --> 00:02:00.627
The volume chart plots three lines: sent, delivered, and received.

26
00:02:00.627 --> 00:02:03.914
Sent and delivered should track each other closely.

27
00:02:03.914 --> 00:02:12.423
When a gap opens between them, that's your early warning, and it's usually list quality or carriers starting to filter your content.

28
00:02:12.423 --> 00:02:16.870
Received is inbound, so you'll see it lift after a campaign goes out.

29
00:02:16.870 --> 00:02:24.025
One thing to know: the buckets are UTC calendar days, so a late evening send can land in the next day's column.

30
00:02:24.726 --> 00:02:28.515
Campaign performance puts your campaigns side by side.

31
00:02:28.515 --> 00:02:31.533
Sent, delivery, and response, in one place.

32
00:02:31.533 --> 00:02:38.059
It lists the campaigns created inside your window, so on a 30 day view Acme only has the one.

33
00:02:38.764 --> 00:02:41.579
Widen the window and the picture fills in.

34
00:02:41.579 --> 00:02:42.852
Now there are four.

35
00:02:42.852 --> 00:02:49.018
June's flash sale went to 28 people, delivered 87 percent, and pulled a 19 percent response.

36
00:02:49.018 --> 00:02:54.179
The restock alert delivered to everyone it reached but got no replies at all.

37
00:02:54.179 --> 00:02:59.942
The two sitting at zero simply haven't gone out yet: one is a draft, one is scheduled.

38
00:02:59.942 --> 00:03:04.835
Same account, very different results, and this table is where you notice.

39
00:03:05.536 --> 00:03:07.741
Campaigns are only half the story.

40
00:03:07.741 --> 00:03:13.900
Underneath, Sipstack measures how fast your team actually replies to the people who write back.

41
00:03:13.900 --> 00:03:18.698
Median first response is 18 minutes, and that's your typical conversation.

42
00:03:18.698 --> 00:03:26.738
The average is over 9 hours, dragged up by a couple of slow threads, which is exactly why the median is the number to trust.

43
00:03:27.442 --> 00:03:35.140
SLA met is the share of conversations that got their first reply inside the target, which is one hour by default.

44
00:03:35.140 --> 00:03:40.182
67 percent here, across the 3 conversations that had something to measure.

45
00:03:40.182 --> 00:03:42.362
Two landed inside, one ran over.

46
00:03:42.362 --> 00:03:47.267
With a handful of threads, read that as a direction rather than a grade.

47
00:03:47.972 --> 00:03:50.671
Per agent activity attributes the work.

48
00:03:50.671 --> 00:03:56.693
John handled 11 messages across 3 conversations, averaging just under 3 hours to reply.

49
00:03:56.693 --> 00:04:01.676
The automated row is everything your campaigns and auto-responders sent.

50
00:04:01.676 --> 00:04:05.691
No person attached, so there's no response time to report.

51
00:04:06.394 --> 00:04:07.666
So, the short version.

52
00:04:07.666 --> 00:04:10.787
Delivery rate tells you whether the carriers like you.

53
00:04:10.787 --> 00:04:13.331
Opt-outs tell you whether your customers do.

54
00:04:13.331 --> 00:04:17.031
And the response times tell you whether your team is keeping up.

55
00:04:17.031 --> 00:04:22.811
Read all three on the same window, once a week, and you'll catch problems while they're still small.

56
00:04:22.811 --> 00:04:23.967
Thanks for watching.
