1
00:00:00,577 --> 00:00:03,760
Administrator reports help you find calls and investigate what

2
00:00:03,780 --> 00:00:08,640
the system recorded. Open Reports in the administration area.

3
00:00:08,768 --> 00:00:13,281
This requires Teams Business. Our demo has five internal

4
00:00:13,345 --> 00:00:17,201
call records, including two answered calls and three with

5
00:00:17,281 --> 00:00:18,081
no answer.

6
00:00:22,779 --> 00:00:26,186
Choose the reporting period at the top right: seven,

7
00:00:26,243 --> 00:00:30,106
thirty or ninety days. The summary cards cover that

8
00:00:30,186 --> 00:00:34,906
period, showing totals, answered and missed calls, average talk

9
00:00:34,970 --> 00:00:38,906
time, and the split between inbound, outbound and internal

10
00:00:38,999 --> 00:00:39,666
calls.

11
00:00:47,613 --> 00:00:50,983
Use the direction filter to narrow the table. We'll

12
00:00:51,029 --> 00:00:54,503
choose Internal because these test calls were between team

13
00:00:54,568 --> 00:00:58,343
extensions. Change one filter at a time so you

14
00:00:58,383 --> 00:00:59,543
can see its effect.

15
00:01:04,844 --> 00:01:08,636
Next, choose the member involved. We'll select Jamie on

16
00:01:08,692 --> 00:01:12,796
extension one thousand and one. All five records still

17
00:01:12,863 --> 00:01:16,877
match because each of these demo calls involved Jamie.

18
00:01:24,585 --> 00:01:28,015
Choose Answered in the result filter. The table now

19
00:01:28,077 --> 00:01:32,895
contains two matching records. Read the timestamp, calling and

20
00:01:32,964 --> 00:01:38,095
called parties, route, result and duration together. These are

21
00:01:38,148 --> 00:01:42,335
recorded call outcomes; they do not, by themselves, confirm

22
00:01:42,402 --> 00:01:43,375
audio quality.

23
00:01:47,910 --> 00:01:51,309
Select Duration to change the table's sort order. You

24
00:01:51,349 --> 00:01:54,909
can also search by number or name. We'll enter

25
00:01:54,962 --> 00:01:58,509
Jamie's extension, one thousand and one, while keeping the

26
00:01:58,549 --> 00:02:00,029
other filters in place.

27
00:02:05,670 --> 00:02:09,470
Route filters help separate direct calls from calls handled

28
00:02:09,523 --> 00:02:13,950
by a group, queue or flow. Selecting Queue leaves

29
00:02:13,998 --> 00:02:17,311
this table empty because these test calls used the

30
00:02:17,380 --> 00:02:21,151
Direct route. An empty filtered list does not mean

31
00:02:21,171 --> 00:02:22,951
the records have disappeared.

32
00:02:28,613 --> 00:02:31,196
Return the route filter to All routes and the

33
00:02:31,276 --> 00:02:36,077
two answered records reappear. The summary cards still describe

34
00:02:36,097 --> 00:02:39,677
the whole reporting period. Use the count below the

35
00:02:39,744 --> 00:02:43,117
table to see how many records match your filters.

36
00:02:49,780 --> 00:02:53,570
Now change the result to No answer. Three records

37
00:02:53,637 --> 00:02:57,490
match. Use their times and parties to identify the

38
00:02:57,570 --> 00:03:01,330
calls you want to investigate, then compare the intended

39
00:03:01,390 --> 00:03:03,409
destination with the route shown.

40
00:03:12,800 --> 00:03:15,093
Clear the filters when you finish and return to

41
00:03:15,125 --> 00:03:19,333
your preferred date range. Use the page controls below

42
00:03:19,373 --> 00:03:22,773
the table when more results are available. For a

43
00:03:22,833 --> 00:03:26,693
support request, note the time and timezone, calling and

44
00:03:26,750 --> 00:03:31,173
called numbers, expected route, and the behaviour you observed.

45
00:03:31,317 --> 00:03:33,973
Keep passwords out of those notes.