Campaign Summary - Call/Chat Result
This report shows the summary of campaign contacts status grouped by call result/ message delivery notifications as synced /stored in scheduled activities. (further discussed with @a user, notion of channels missing)
Field Name / Group Name | Sub Field | Description | Comments |
Campaign Name |
| Name of the Campaign. | Data source: CX Scheduled Activities |
Total Loaded |
| Number of contacts uploaded into a campaign. | This data is not available in the scheduled activities. @a user to comment/ facilitate. |
Dialled (Unique) | Total number of dialled (unique) contacts. | ||
Dialled (Attempts) |
| Total number of dialled (attempted) contacts, e.g. there are 3 contacts dialled, each at least 1 time, but the first contact was re-dialled a second time as well. So the total number in this column will be 4. | All Attempts (can be multiple per contact). |
Connected NORMAL_CLEARING |
| Successfully connected (code: 10) / | CX Scheduled Activities Jawad Hassan: redialling the same customer (already connected) should be restricted. |
No Answer |
| The number of attempts where the dialer outcome was detected as "No Answer". However, the contact might not still be closed (rescheduled by the campaign strategy) | CX Scheduled Activities |
Busy USER_BUSY |
| The number of attempts where the dialer outcome was detected as "Busy". However, the contact might still not be closed (rescheduled by the campaign strategy) | CX Scheduled Activities |
Not Connected |
| The number of contacts where the contact was dialed and was not connected due to any reason. Note that this is relevant only for voice calls and does not apply to SMS attempts. | CX Scheduled Activities JH: Customer Abandon in Queue, once connected is inbound abandoned, not outbound JH: Dialer Abandon, same as customer abandoned? We should ONLY consider this one instead. |
Problem |
| All status codes in this group indicate instances where there was a problem contacting the customer. | CX Scheduled Activities |
|
|
| JH: Should be a separate report |
|
|
| JH: no difference between connected and agent connected |
|
|
|
|
Dialer Abandoned |
|
| JH will check the list of Other dispositions that go here. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
…. similar for other text channels |
|
|
|
Filters & Layout
Campaign (only one can be selected)Instead show a list of flows (only one can be selected)
Type
Daily + Hourly (Consolidation Hourly)
Yesterday (will show 24 rows)
Date Range (e.g. 1st Jan - 2nd Jan will have 48 rows, …)
Daily
Yesterday (1 row)
Today (1 row)
Date Range (1 row for each date, with a summary count for all days at the bottom)
Weekly (1 row in total for all weekly options)
Last Week
This Week
Dropdown of weeks (e.g. Week 1st: 1-7, Jan 2024, Week 2nd: 8-16 Jan 2024, … , Week 28th: 8-16, July 2024)
Monthly (1 row for each month selected)
Dropdown of Months (e.g. Jan 2024, Feb 2024, … , June 2024)
Discovery
Points agreed,
The summary report should include the summary of each channel, not just voice. There should be no separate reports for each channel.
Any changes to the decided template will taken up after the basic reports are available. We will try to incorporate all the customer requirements first, in the existing reports (if it made sense), 2ndly may create new reports but package them with the standard reports, 3rd, we develop custom reports for customers if it cannot be avoided (these reports will not become part of the standard reports).
EFCC and Cisco: We will have one template for both, some columns may be empty based on the data availability depending on the contact centre.