Why Do Discrepancies Occur in Boostlingo Call Logs and Durations?
Boostlingo users may occasionally notice discrepancies in call logs, such as mismatched timestamps or differences between call durations and recording lengths. These discrepancies are typically caused by technical factors related to how calls are managed and recorded.
Common Causes of Call Log Discrepancies
1. Dropped Connections
When an interpreter's connection drops unexpectedly, their side of the session may close earlier than the client's. In such cases, the interpreter's presence in the call log will show an earlier end time, while the client's line remains active until they manually end the call. This results in different timestamps for the interpreter's presence and the overall call end time.
2. Lack of Hangup Signals
If the requestor's device does not send an official hangup signal, the call may remain active even after the interpreter has stopped providing interpretation. In these situations, the interpreter is expected to end the call on their side. However, the call duration in the log may reflect the extended time the call remained active, even if no interpretation was occurring.
Impact on Call Duration and Recording Length
Call recordings are designed to capture only the active interpretation portion of the session. If a call remains active but no audio is transmitted (e.g., due to dead air), the recording will automatically trim this silent period. As a result, the recording length may be significantly shorter than the total call duration shown in the logs.
Best Practices to Avoid Discrepancies
To minimize discrepancies in call logs and durations:
Ensure Proper Call Termination: Both interpreters and clients should ensure they properly end the call on their respective devices.
Monitor Connection Stability: Use a stable internet connection to reduce the likelihood of dropped calls.
Report Persistent Issues: If discrepancies occur frequently, report them to Boostlingo support for further investigation.
By understanding these common causes and following best practices, users can better interpret call logs and avoid confusion.