Calls not logging to timeline

A completed call normally shows up two ways on the contact: as a call entry in the Conversations timeline, and as a note with the outcome and duration. These are written separately, so it is possible for one to appear without the other.

The two things that get written

• The call log entry (the timeline bubble). This needs both the caller’s and the callee’s phone numbers to have been captured correctly. If either is missing, the call is never logged, silently, with no retry, since there is nothing to match it to a contact with.
• The call note (outcome, duration, status, any note text a rep added). This is written separately, after the call log entry, and its own failure never rolls back or retries the call log entry, so it will not cause a duplicate.

Note: A note-write failure is silent by design, so it doesn’t risk re-posting the same call. If a call shows up in the timeline but the note or outcome looks missing, that is the more likely half to have failed quietly, not the timeline entry itself.

Check these in order

1. Was the call blocked by the firewall?

A blocked caller is rejected before anything is recorded: no timeline entry, no note, no missed-call badge. If a specific number’s calls never show up at all, check whether it is on the block list. See SMS firewall: block and allow lists (voice blocking shares the same allow/block lists).

2. Did the call actually complete on both ends?

Both the caller’s and the recipient’s numbers need to be captured for a call to be logged. A call that dropped before it fully connected, or that had an unusual routing path, can be missing one of the two numbers, which stops the timeline entry from being written.

3. Give it a little time

If the first attempt to write the call to GHL fails (for example, a temporary GHL API problem), a background job retries it automatically. A call that is missing right after it ends may still appear shortly after. If it is still missing after a while, that points to a failure on retry too, and is worth reporting to support with the approximate time of the call.

4. Check Notes, not just Conversations

If you are specifically looking for a missed-call text-back, it does not appear as a message bubble in Conversations. It is written as a note on the contact instead, because of how GHL’s own API exposes this kind of automated reply. Look at the contact’s Notes, not the conversation thread, and expect wording like “Missed call from <caller> to <your number>. Texted back automatically.”

5. Confirm the contact match is what you expect

Phone Clover matches an inbound or outbound number to a contact using GHL’s own phone-number matching. It does not run its own separate duplicate-detection on top of that. If a call landed on a different contact than you expected, or created a contact you didn’t expect, that reflects how GHL matched the number, not a Phone Clover-specific bug.

What a logged call’s note contains

When the note write succeeds, it includes the call time, whether it was answered, missed, busy, failed, went to voicemail, or was cancelled, the direction (inbound/outbound), the duration, the outcome you picked, and any note text you added.

Troubleshooting checklist

1. Confirm the number wasn’t blocked by the firewall (nothing is logged for a blocked call).
2. Wait a few minutes; a failed first attempt retries automatically.
3. Check Notes as well as Conversations, especially for missed-call text-back.
4. If a call is still missing after a while, report it to support with the number and approximate time, since a retry that keeps failing needs a look at what’s blocking it.

Related

• SMS firewall: block and allow lists
• No incoming call popup
• Post-call outcomes