How logging works
At the end of a call, the embedded dialer:- determines the outcome from the finished call session
- looks up the current HighLevel contact in widget state
- sends the outcome, call identifier, and duration back through the HighLevel bridge
- writes that activity to the contact record in HighLevel
What gets sent back
The embedded logging flow is built around the current contact and the completed call state.| Value | Source |
|---|---|
| contact id | current HighLevel contact in widget state |
| outcome | derived from the finished call |
| call id | active call session |
| duration | call duration after hangup |
When logging succeeds best
Call logging works best when:- the call started from a HighLevel contact context
- the contact exists in the current HighLevel location
- the widget stays open until the call has fully ended
Common reasons logs do not appear
- the call was a manual dial with no mapped HighLevel contact
- the app lost the embedded session before the call finished
- the location did not grant the permissions required for writing activity
Notes and other follow-up details appear in the contact activity flow after the call finishes. If you close the widget too early, you can interrupt that writeback.