Every support agent knows the pain: you’re in Zendesk, responding to a ticket, and you need context about the organization behind the requester. You open a new tab, dig through the profile, maybe ping a teammate. It’s time-consuming, disruptive, and inefficient.

What if you had all the key organization data, right there in the ticket view?

Organization Cards is a Zendesk app that gives your agents instant access to essential organization details directly in the ticket sidebar. No clicks. No distractions. Just instant clarity.

👉 Install Organization Cards on Zendesk Marketplace

What is Organization Cards?

Organization Cards is a lightweight but powerful app that adds a contextual information panel to every Zendesk Support ticket. It pulls and displays data from the ticket’s associated organization — like name, domain, custom fields, or whatever you decide is most useful.

💡 You define the fields.

📍 It shows up where it matters.

⏱️ Agents save time. Everyone wins.

Why Your Team Will Love It

Context at a glance — Agents instantly know who they’re helping: industry, location, service tier, etc.

Faster responses — No more digging around to understand the organization’s profile or history.

Fewer mistakes — Avoid treating a high-value customer like a free-tier user — or vice versa.

Highly customizable — You choose which organization fields are displayed in the sidebar.

Works in all environments — No dependencies, no code, just plug-and-play.

Real-World Scenarios

• Priority Support Tiers: See instantly whether the organization has a premium SLA so your agents can escalate faster.
• Industry-Specific Policies: Tailor your tone and replies based on the customer’s segment or location.
• Sales & Success Handoff: Sales closes the deal, and your support team immediately has context to deliver a great first experience.

Setup in Minutes, Value from Day One

✅ Free 14-day trial — No credit card required

💲 Only $15/month after trial

🛠️ Zero development required — Install and go

🔒 Secure & native — Built for Zendesk, with Zendesk APIs

How to Get the Most Out of Organization Cards

1. Map your critical org-level fields: Identify what your agents really need to see (e.g. contract status, support tier, client type).
2. Ensure org data hygiene: Make sure those org fields are reliably filled during onboarding or sync from your CRM.
3. Incorporate into workflows: Train agents to glance at the card before replying to ensure context-driven communication.
4. Iterate and improve: Adjust the displayed fields based on feedback from support leaders and QA.

Curious Yet?

If you’re running a support operation at scale, even small inefficiencies snowball. Organization Cards is about solving one of the most subtle yet costly friction points: the lack of immediate organization-level context.

Let your team focus on solving problems — not searching for details.

➡️ Try it now — 14-day free trial

Built with care by vaide.app, experts in scalable Zendesk solutions.

Zendesk Tips — How to Schedule Message Delivery in Tickets

While it may seem like a basic feature, the Zendesk platform still doesn’t offer a native solution for this type of automation. This can be frustrating for companies that operate in shifts or when agents need to handle tasks outside of regular business hours. Often, we prefer customers not to be aware of this or simply want them to receive our messages during normal working hours. After all, no one appreciates being disturbed by an email in the middle of the night, right?

Our solution is designed to be both simple and efficient, easily adaptable to the needs of any Zendesk administrator, and can be implemented using the following steps:

1. Configuring a schedule
2. Creating custom ticket statuses
3. Setting up triggers
4. Implementing automation

Here’s how to implement this strategy step by step!

Objective

Our goal is to create a native solution that ensures messages are sent as soon as the company’s operating hours begin. In designing this strategy, we also wanted to give agents the flexibility to choose between sending the message immediately or scheduling it for the most appropriate time. This approach allows us to maintain operational efficiency while enhancing the customer experience, ensuring communication aligns with optimal timing.

How it Works

Let’s say your working hours are from 09:00 to 17:00, but for some reason, you need to add a public comment on a ticket at 18:00. However, you don’t want the customer to receive the notification outside of business hours and prefer it to be sent the next working day at 09:00. To achieve this, we’ll implement a set of rules that hold the notification until the ticket re-enters business hours. As a result, the message will be sent between 09:00 and 10:00, while adhering to certain limitations set by the business rules in place.

1. Configuring the Schedule

The first step is to ensure that all tickets in your Zendesk account are linked to a schedule. Even if your company doesn’t use SLAs, having operating hours configured provides several benefits, especially in cases like this.

If you haven’t set up operating hours yet, go to the “Admin Center”, navigate to Objects and rules > Business rules > Schedules, and create a schedule. In our example, we’ve established standard operating hours from 09:00 to 17:00, Monday to Friday.

2. Configuring Custom Ticket Status

Although this step is straightforward, some companies have yet to adopt the custom ticket status functionality. Ensure this feature is enabled in your account, or activate it by going to Objects and rules > Tickets > Settings.

Once the feature is enabled, navigate to Objects and rules > Tickets > Ticket statuses. Click on “Create ticket status” to add a new option specifically for scheduling message delivery. To follow Zendesk’s best practices and ensure proper application of rules, such as SLAs, we recommend classifying this status under the “Pending” category, although it’s not mandatory. Choose a name and description that best suit your needs.

Here’s an example of how we configured ours:

We want to ensure the default rule stays active so we can track when the notification is sent. As a result, your status list under the “Pending” category should resemble the image below.

3. Setting the Triggers

First, we need to ensure that a trigger is set up to apply the desired schedule to the ticket. If you haven’t created one yet, now is the ideal time to do so. Typically, we recommend that each schedule has its own dedicated trigger, based on the group the ticket belongs to. However, we understand that some companies have more complex structures and may require more advanced rules.

For the rule to function properly, it is crucial that a schedule is applied to the ticket. Keep this in mind when configuring your business rules. Below is a simple example of a trigger to apply a schedule (we recommend keeping this trigger dedicated solely to this purpose, avoiding mixing it with other rules).

Now, let’s get to the core of the setup. First, we need to modify the existing notification triggers to ensure the scheduling works correctly. To do this, we’ll add two new conditions:

1. Ticket status is not “Schedule Notification”

2. Current user is (agent)

These conditions ensure that the trigger won’t send notifications automatically unless it’s activated by an automation — which is exactly what we’ll set up next.

Now, let’s dive into the key step: configuring the triggers that will ensure messages are sent according to schedule. We’ll begin with the rule responsible for sending messages at the scheduled time. The following conditions will be used:

1. Ticket status is Schedule notification

2. Privacy is Ticket has public comments

3. Within business hours is Yes

For the actions, we’ll set up the following:

1. Ticket status = Pending

2. Notify by User email = Ticket (requester and CCs)

Email subject = Re: {{ticket.title}}

Email body = {{ticket.latest_comment_html}}

To clarify what we’ve done so far: we’ve essentially instructed Zendesk to send the last comment on the ticket when it reaches status "Schedule notification" and the schedule indicates that operating hours are active. In the actions, we also included changing the status back to the default “Pending,” ensuring that the trigger doesn’t send duplicate notifications.

You might be wondering: what about the other notification trigger? Won’t it fire as well? The answer is no. We added the rule “Current user is (agent)” specifically to prevent this. A trigger that changes a ticket’s status is never recognized as an agent action, thus preventing unwanted notifications.

Now, let’s set up the trigger that will place the ticket on hold if the notification is created outside of operating hours. The rules for this will be simpler:

1. Ticket status is Schedule notification

2. Privacy is Ticket has public comments

3. Within business hours is Yes

4. Tags Contains none of the following "wait_schedule"

For the actions, we’ll configure the following:

1. Add tags = wait_schedule

4. Setting up the Automation

Finally, we reach the last step to get our solution fully operational. As you may know, automations in Zendesk run every hour, checking for tickets that meet specific conditions and applying the necessary actions. We’ll leverage this functionality by creating an automation rule that prompts Zendesk to check, every hour, whether the ticket is within operating hours.

As mentioned at the beginning of this article, this rule has some limitations, meaning we can’t guarantee the exact time the message will be sent. Typically, the message will be sent during the early hours of the operating schedule, such as between 09:00 and 10:00, but it could extend to 11:00. In instances with a high volume of tickets, automations may hit their execution limit, resulting in a longer delay.

Now, let’s get to the practical part: configuring the rule, which is straightforward.

1. Ticket status is Schedule notification

2. Hour since update (business) Greater than 0

3. Tag Contains at least one of the following "wait_schedule"

For the actions, we’ll simply remove the tag we created. This will allow the two triggers we’ve set up to re-evaluate the conditions when the automation runs, ensuring the rule’s criteria are met.

1. Remove tags = "wait_schedule"

Testing the Solution

Now for a simple task: if you want to test the solution immediately, adjust your ticket’s schedule so that operating hours begin an hour after you add your comment. This way, you can send the message and check within an hour if it was delivered. Don’t forget to revert the settings to their correct values after testing.

In a ticket, preferably one opened by an end user, write a comment. When selecting the status for sending, choose “Pending” to send the message immediately (we recommend testing this to ensure your changes haven’t caused any unintended issues) and select “Schedule notification” to test our solution.

Remember to wait 1 to 2 hours to confirm the automation has run successfully, as automations do not execute instantly. If any issues arise during execution, review the procedures outlined above or check the ticket events to determine the cause of any irregular behavior.

We hope this solution helps you further optimize your Zendesk support. At vaide.app, we believe simplicity and efficiency are the keys to business success. If you’re looking for smart ways to streamline your processes and elevate the customer experience, we invite you to explore our solutions.

Visit vaide.app and discover how we can transform the way your company operates.