Some call logs appear delayed, or are created later than other call logs.
A common cause of discrepancy in how quickly a call logs in an integration is the logic behind when Aircall sends your call data to an integration.
For several of our integrations, call logs are triggered by either the call being answered, or the call ending:
- For answered calls, the call log will be created as soon as the call is answered, then updated with the
call.endedevent which occurs 30 seconds after the call is hung up.
- For unanswered calls, the call must wait for the
call.endedevent to log, which will occur 30 seconds after the caller hangs up.
Because of this, answered calls will be logged more quickly in your integration.
At the moment there is no way to adjust this timing of call logging, so it is important that members of your team, and anyone using the integration, is aware of this behavior.