Zendesk never sleeps. Updates and new features are constantly rolling out, and this week brings a subtle but incredibly powerful change for administrators. Here’s our expert take.
More Context, Fewer Headaches: Zendesk’s New Lookup Field Limits Are a Game-Changer
What We Think: This is a fantastic quality-of-life improvement for any organisation using multiple ticket forms. By shifting the Zendesk lookup relationship field limit from a global cap to a per-form basis, Zendesk is empowering administrators to create richer, more context-specific support experiences. It’s a subtle change on the surface, but it removes a major administrative bottleneck for scaling companies. We see this as a huge win.
The Reality Check: What’s Actually Changing?
Let’s cut through the jargon. Previously, your Zendesk plan came with a hard limit on the number of lookup relationship fields you could have active. For example, if your plan limit was 10, you could only use 10 of these fields across your *entire* Zendesk instance, regardless of how many different ticket forms you had. This forced a lot of tough choices for businesses with diverse departments using the same platform.
The new reality is much more flexible. The limit is no longer applied globally but is now enforced on a *per-ticket-form* basis. That same plan limit of 10 lookup fields now means you can have up to 10 on your IT Support form, another 10 on your HR Onboarding form, and yet another 10 on your Customer Billing form. You can create a master pool of up to 40 lookup fields in total and then pick and choose which ones appear on each form, up to your plan’s limit for each one. This only applies to plans with multiple ticket forms, but for those customers, it’s a massive unlock.
Our Expert Opinion: Why This Matters More Than You Think
Our team sees this as more than just a simple limit increase; it’s a fundamental shift that addresses a critical scaling pain point. As companies grow, they inevitably bring more business functions into Zendesk—IT, HR, Facilities, Sales Ops, and so on. Each of these teams has unique contextual data needs. The old model created a bottleneck where an admin might have to choose between adding a lookup field for “Network Asset” for the IT team versus a “Supplier Contract” for the procurement team.
This change solves three key operational challenges:
- Reduces Agent Friction: Agents now only see the context that is relevant to their specific workflow. An HR agent handling a payroll query doesn’t need to be distracted by a lookup field for “Product SKU” or “Data Centre Location”. A cleaner, more focused interface means faster resolution times and fewer errors.
- Enables True Workflow Specialisation: You can now properly customise each ticket form to be a purpose-built tool for a specific task. Your IT form can link to assets, software licences, and users. Your customer service form can link to products, subscriptions, and orders. This deep customisation was difficult, if not impossible, under the old system.
- Improves Data Integrity: By ensuring the right data connections are available on the right forms, you guarantee that agents are linking tickets to the correct external objects. This makes your reporting more accurate, your automations more reliable, and your overall data structure much healthier. A clean data model is a cornerstone of a high-performing instance, something we always focus on during a Zendesk health check. This update makes maintaining that integrity much easier.
The ability to create a central library of up to 40 lookup fields provides a generous amount of flexibility, allowing you to build out a comprehensive data model and then apply it precisely where it’s needed. This is a mature approach to platform administration that we’re thrilled to see.
How We’d Handle the Rollout: A Strategic Checklist
Here is what we’re advising our clients to do. Don’t just start adding fields randomly. A strategic approach will ensure you get the maximum benefit from this new flexibility with the Zendesk lookup relationship feature.
| Phase | Action Items | Our Advice |
|---|---|---|
| 1. Audit & Strategise |
| This is the most critical step. Get stakeholders from each team in a room and ask them: “In a perfect world, what information would you want to link to this type of ticket?” Use this wishlist to build your master plan. |
| 2. Build & Test |
| Pay close attention to how these new fields interact with your existing business rules, triggers, and automations. A new field, even if optional, can have downstream effects. Testing is non-negotiable. |
| 3. Train & Deploy |
| Focus on the benefits for the agent. Don’t just say “there’s a new field,” but “now you can instantly see the user’s assigned laptop right from the ticket.” If you need help structuring this rollout, contact your alboz. Solution Consultant. |
In summary, this update to the Zendesk lookup relationship field is a powerful enabler for businesses looking to scale their operations within the platform. It removes an artificial barrier and allows for a more sophisticated, tailored approach to capturing the context needed to provide excellent service, both internally and externally. It’s a move that prioritises administrative flexibility and agent efficiency—two things we always love to see.
