CRM tags: the 13 events and what they trigger

GodSetter signals your CRM through tags. Thirteen distinct events — nine call outcomes, one appointment event and three "call skipped" events — each apply a tag to the contact involved, and your CRM workflows key their automations on those tags: stop a nurture sequence when an appointment is booked, alert a human on "callback requested", exclude Do-Not-Call leads from future triggers.

The tag is the signal, not the mechanism. The behavior that matters — blocking, retries, cancelling scheduled redials — lives in GodSetter and fires on the event itself, whether or not a tag is applied.

Exactly one tag goes the other way: the disconnect tag, which GodSetter reads in your CRM to take a contact out of the platform. It has its own section at the end of this article.

Where do I configure tag names?

Settings → CRM tags. The card lists all 13 events in three groups — Call outcomes, Appointments and Skipped calls — with one text field each, and under every field the UI explains when that event fires and what it implies. Edit the names and save. Tag names are per-agency and apply to all your agents and clients.

What are the default tag names?

Until you change them, these names are applied (the defaults are Italian — a product-history detail; rename them freely, up to 100 characters each):

What happens if I leave a tag field empty?

No tag is applied for that event — that's the off switch, per event. Everything else is unchanged: the outcome is still recorded, notes and custom fields are still written, and blocking or retry behavior still applies. Empty only means "don't signal this event to my CRM".

Do I need to create the tags in my CRM first?

No. Tags are created in your CRM on first use. Point your workflows at the exact names you configured (or the defaults) and they match as soon as the first event fires.

What does "Appointment booked" imply for future calls?

Applied when the agent books an appointment — in-call or detected at call end. GodSetter also cancels any redials already scheduled for that contact, so a retry planned before the booking never fires. A new workflow trigger would still call them again, though: use this tag in your workflow to exclude booked contacts from further triggers. A new trigger also restarts the whole cycle: the attempt counter goes back to zero and the retries still parked for that lead are dropped (a callback the lead asked for survives).

What happens after "Not interested" or "Outcome to review"?

Not interested is applied when the contact clearly declines during the call. It does not block the contact: no automatic redial is scheduled, but a future workflow trigger would call them again — key on the tag in your workflow if they should not be recontacted. Outcome to review is applied when the call ends without a classifiable outcome; it has no automatic effect on future calls — review the transcript and summary in Calls.

What does "Callback requested" trigger?

Applied when the contact asks to be called back. The time they give is indicative, never refused: the callback is scheduled at that moment, or slid to the first moment the agent is allowed to call — and the agent confirms that time out loud. A callback replaces every other call already queued for that contact: the lead's latest word wins. If the agreed callback goes unanswered, the agent's callback policy decides what happens next (a few more tries, or the retry plan started over) — see Retry cadence, callbacks and transfer. If the moment stayed vague, the platform still plans the call a couple of days later (the agent says so); a lead who promised to call back gets a courtesy call a week later unless they did. The planned date can also land in two custom fields of the contact — see Settings → Follow-up in the CRM.

Which outcomes can trigger an automatic retry?

No answer (the call rang out or the number was busy), Voicemail (voicemail answered — the agent hangs up or leaves the configured message, it never talks to the machine) and Call failed (technical failure, line issue or unreachable number). For each of these, a new attempt is scheduled automatically only if the agent's retry cadence is enabled with that outcome included — see Retry cadence, callbacks and transfer.

When is "Retry plan exhausted (unreached)" applied?

When the agent has used every attempt of its retry plan without ever talking to the contact. GodSetter applies the tag once and adds a CRM note summarising the cycle: how many attempts, over how many days, and the last outcome. Nothing else is scheduled for that lead — hook a recovery workflow (SMS, email) on this tag.

What does "Do not contact (DNC)" mean?

The strongest event: applied when the contact asks never to be contacted again. GodSetter blocks the lead — future triggers are discarded, scheduled redials never fire, and their inbound calls are not answered. Unblocking is a deliberate, manual action from the Leads page — see Do-Not-Call: blocking and unblocking.

When is "Appointment cancelled" applied?

When the agent cancels an existing appointment at the contact's request during a call. It has no automatic effect on future calls — its typical use is triggering a re-booking workflow. See Cancel and reschedule on inbound calls.

When are the three "Skipped" tags applied?

Each one marks a workflow trigger that arrived but did not produce a call:

• Skipped: missing consent — strict mode is on and the trigger carried no valid consent proof. A new trigger with valid consent proceeds normally.
• Skipped: no active number — the agent has no assigned active numbers. Assign one in the agent's Numbers tab and subsequent triggers proceed.
• Skipped: blocked lead — the contact is already blocked (DNC). It stays that way until an operator unblocks the lead from the Leads page.

Only these three skips reach your CRM. GodSetter records the other reasons a lead was not called — no assigned number at dispatch time, a missing phone number, a deleted client or agent, a trigger pointed at an inbound agent — on the lead itself: you see them as a Skipped badge on the Leads page, but no tag is written.

The disconnect tag: taking a contact out of GodSetter

This one is the exception: GodSetter does not write it, it reads it. Add the disconnect tag to a contact in GoHighLevel and that contact leaves the platform at once — the lead is blocked (DNC), every call queued or scheduled for them is deleted (retries and agreed callbacks included), and no future workflow trigger can dial them. It is the CRM-side off switch for one contact.

Configure it in Settings → CRM tags, in the Disconnection section. The field is prefilled with the default disconnect-godsetter; rename it to whatever your team already uses (matching ignores capitalisation and surrounding spaces). Leaving the field empty switches the feature off — an empty field means "no tag disconnects anyone", while a field you never touched means the default is active.

It needs the GodSetter Marketplace app installed: the tag change arrives as a platform event, with no workflow to wire. And, like every CRM-side block, it only ever blocks — removing the tag later does not put the contact back in the cycle; only Unblock lead on the lead page does. See Do-Not-Call: blocking and unblocking.

Does removing a tag in the CRM change GodSetter's behavior?

No. Future-call behavior depends on the event GodSetter recorded, not on the tag's presence in your CRM. Deleting the DNC tag from a contact does not unblock the lead — they stay blocked until an operator unblocks them from the Leads page. The reverse is also true: manually adding an outcome tag changes nothing in GodSetter. Tags are output, never input.

Next

• Post-call data write-back
• Wire your CRM workflow to an agent
• Consent, strict mode and proof