Outcome. Tickets created without a linked contact are flagged and routed to a cleanup queue instead of sitting unassignable to any customer record.
flowchart TD
A[Ticket created] --> B{Contact associated?}
B -->|no| C[Flag: Missing contact]
C --> D[Add to review list + create task]
B -->|yes| E[Flag: Has contact]

When to use it, when not to
- UseUse it when tickets arrive through channels that can create a ticket without a contact attached: certain forms, some inbound email configurations, or manual creation by an agent who forgets to link a requester.
- UseUse it as a safety net, not a replacement for configuring your ticket-creation channel to require a contact at the source where that option exists (check in your portal: whether your specific ticket-creation channels, shared inbox, chat, forms, expose a "require a contact" setting directly).
- SkipDo not use it on pipelines where tickets intentionally start without a contact, such as internal, non-customer tickets, unless you also filter by pipeline.
- SkipDo not use it expecting it to guess or create the missing contact. It only flags the gap for a human to resolve.
or the data quality pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.





