Skip to main content
Connected GoHighLevel contacts can receive tags derived from a call’s disconnection reason. The account needs a working connection and the call must resolve to a contact for the tag write to occur.

​
Understand the result

A detailed disposition is converted to a readable tag. For example, user_hangup becomes contact hangup, and agent_hangup becomes assistant hangup. Where answered tagging is enabled, a separate answered or not answered classification is also written. The answered set includes contact hangup, assistant hangup, transfer, inactivity, and maximum-duration endings. Other or unknown dispositions are classified as not answered by that mapping. These are call classifications. They do not prove a person completed the conversation, an appointment was booked, or a payment was collected.

​
Disposition values

These are the normalized dispositions produced by the current phone-call aggregation path. The readable GHL tag replaces underscores with spaces and changes user to contact and agent to assistant. The binary answered-tag mapping additionally recognizes inactivity as answered if that value is supplied. Missing or unrecognized dispositions map to not answered. Treat provider and future values you do not recognize as unknown in your own workflow rather than discarding the event.

​
Create a tested follow-up

  1. Complete a test call to a contact you can inspect in GoHighLevel.
  2. Open that contact and record the exact tags added by your setup.
  3. Create the follow-up workflow using the observed tag and the intended contact criteria.
  4. Run a second call to the same contact while the tag is already present.
  5. Confirm whether your workflow ran again and whether that is the intended behavior.
If you need a distinct event for every call, use a post-call webhook and its call ID. Do not depend on re-adding an existing tag to create a new event.

​
Troubleshooting

  • No tag: check the linked contact, the GoHighLevel connection, and the completed call result.
  • Unexpected tag: compare it with the normalized disconnection reason and inspect other workflows that may add their own tags.
  • Follow-up did not repeat: inspect the CRM trigger’s behavior when the contact already has the tag.
  • Tag says answered but outcome is missing: review the recording, transcript, and actual business record.
Save call results · GHL connection troubleshooting