Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the redux-framework domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/u863362410/domains/godial.cc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the loginizer domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/u863362410/domains/godial.cc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/u863362410/domains/godial.cc/public_html/wp-includes/functions.php on line 6114
Call Log Duration Mismatch? - Godial

Call Log Duration Mismatch?

Why Does The Duration Not Match The Actual Call Log Always?

GoDial keeps track of the time the call has been initiated till the time the call has been put to an end and the user has returned back to the application. Hence the Call duration is indicative and an experimental feature.

GoDial currently does not call read logs on the phone, as there are restrictions from Android and iOS.
*Note : There may be issues on some devices regarding call duration
We are working to enable actual call logs from the devices soon.