Here at ZipDX our aim is to provide you the tools to make it easy to hold the most productive conference calls possible. Elsewhere on this site we’ve detailed tools for creating conferences via various means. Also, the conference dashboard for managing a conference in-progress. This page introduces reporting on completed conferences.
When a conference ends the system automatically sends a summary email to the conference organizer. That information, and more, is available to the conference organizer in Completed Conferences section of the web portal. Simply click on the conference title to access the conference summary.
Conference Summary |
|
|---|---|
| Topic | The title given when the conference was created. |
| Account | The ZipDX account charged for the conference. Note that an organizer can have access to multiple accounts. |
| Actual Start | The date & time when the first connection was established, causing the conference to be created. |
| Manner of conference creation | Instant meeting, Web scheduled or Created by a calendar application |
| Duration | |
| Number of connections | (if appropriate) number of concurrent connections |
| Transcription | If the conference was transcribed, there will be a link to access the transcript. Also, a link to share transcript access with others. |
| Recording | If the conference was recorded, there will be a link to access the recording. Also, a further to share access with others. |
ZipDX Meeting ID
The Meeting ID (pictured below) is a number starting with Z (ex Z12345678.) This is especially useful should you need to request assistance from our support team. It’s the one piece of information that allows us to immediately access the call details.
Connections |
|
|---|---|
| Start time | When this connection was established. |
| Minutes | Connection duration. Includes amount they were noted as “talking” expressed as both minutes and % of connection time. |
| Phone ID | Could include: - Participant caller ID – when available. - City or Country – if specific caller ID is not available we try to geo locate the call. - VoIP ID – indicating the generic use of the web phone. - The name they entered when if prompted when accessing the web phone. - Dial to User – when the system called the participant. |
| Phone Number | Could include: - The participants telephone number. - VoIP ID – indicates connection via web phone. - SIP Call – indicates connection via SIP phone. |
| Access Method | Indicates how they connected: - Dial In Free = used toll free access line. - Dial In Toll = used regular (non-toll free) access line. - The access number they dialed. - /M indicates they connected using a mobile phone. |
| Total | The total number of connection/minutes involved in the conference. |
From Information to Insight
Let’s consider the example shown above. There are three connections, each lasting over 70 minutes, including one participant who was on a mobile phone. No-one hung-up and rejoined.
All three are listed as “Other Participants.” This tells us that they all connected using the same, shared conference code.
The first connection shown above is indicated as “talking” for 82% of 72 minutes. That has certain implications.
In normal conversation between two participants we would expect each to be “talking” 40-60% of the time.
In a lecture or other one-way presentation, we expect only one participant to be shown as talking most of the time.
When one participant is shown as talking >80% of the time, we begin to wonder if there was a problem with background noise.
The /M tells us this participant was connected via mobile phone. Perhaps they were in a noisy location? Or had the phone in speakerphone mode, which always introduces more background noise.
- Introduction to Conference Diagnostics
- Introduction to the Conference Summary (this page)
- Introduction to Conference Event Logs
- Introduction to QA Reporting