Branching logic in Advanced AI for Email — determining brand from email content first, then falling back to a custom org field | The place for Zendesk users to come together and share
Skip to main content
Natalie36
Natalie36
Newcomer
August 4, 2026
Question

Branching logic in Advanced AI for Email — determining brand from email content first, then falling back to a custom org field

  • August 4, 2026
  • 1 reply
  • 38 views

We have 4 brands set up in Zendesk, each representing a different application we offer. Some customers use multiple applications/brands, but all support requests come into a single general support email address connected to Zendesk.

We're trying to set up Advanced AI for Email to determine which brand a customer's email relates to, using this logic:

  1. First, check the customer's initial email message to see if they explicitly state which brand/application they're referring to. If so, treat that as the brand and follow the corresponding segmented condition.
  2. If the brand isn't stated in the email, fall back to a custom organization field called "Org Application Contracted for" and use that field's value to determine the brand.

I tried building this with segments in the dialogue workflow, but it seems Zendesk isn't pulling in the organization field value before it evaluates the segment condition — it just falls through to the fallback path in the use case dialogue workflow rather than matching on the correct brand.

I also tried adding an action to pull that organization field value when the email is received, but that hasn't worked reliably either — it's inconsistent and often still ends up defaulting to the fallback.

Has anyone set up similar branching logic (check email content first, then fall back to an org field) in a dialogue workflow for Advanced AI for Email? How did you get the field value to populate reliably before the segment/condition is evaluated? Any workarounds, ordering tricks, or best practices would be really helpful.

1 reply

PanKe
PanKe
August 13, 2026

This sounds more like an evaluation-order problem than a matching problem. I’d split it into two steps: first resolve the brand into one normalized ticket value, then let the AI branch read only that value. If the email names a brand, write that result to a ticket field or a scoped tag. Only when that value is still empty should the fallback copy “Org Application Contracted for” into the same field or tag. The segment should check that normalized ticket value, rather than reading the organization field directly.

I’d test it with three otherwise identical emails: one with an explicit brand, one with no brand but the org field populated, and one with neither. After each step, check the ticket and confirm the field or tag exists before the segment runs. That should tell you whether this is a timing issue or whether the org value simply isn’t available to the dialogue workflow at that point.

If the value is still missing in the second case, I’d move the fallback earlier, into ticket creation or routing, instead of trying to force it inside the AI dialogue. I haven’t tested this exact Advanced AI for Email setup, but that normalized-field check is where I’d start.

Panke | Founder, RuleScope | https://rulescope.offshoot-labs.com
    Terms & ConditionsAccessibility statement