Pulse

About TL;DR

TL;DR builds simple, no-nonsense Zendesk apps and integrations — technology without the runaround, straight to the point. Pulse is one of our tools built for support teams who need customer context beyond just tickets.

What Pulse does

Pulse shows the event history of a ticket requester or a user profile, right in the sidebar. It highlights activity that happens outside of Zendesk — purchases, logins, phone calls, cancellations — alongside native Zendesk events, so agents don't have to piece together context from multiple systems.

• Hide the noise. One toggle filters out native Zendesk events (tickets, etc.) so you can focus on external customer activity.
• Recognize events at a glance. A consistent icon system (no emoji) makes event types easy to scan.
• Search and filter. Find a specific event by type, description, or any detail inside it.
• Jump to the related ticket. If an event references a ticket, open it with one click.
• Log events without writing code. A simple form lets any agent record what happened — no JSON required.
• Works in English, Portuguese, and Spanish. The interface automatically matches the agent's language.
• Built for developers too. A quick-access panel links straight to the Zendesk Events API docs for teams that want to send events directly from other systems.

Data we access, use, and store

Pulse reads and writes Zendesk user events through the Zendesk Events API, using the same authenticated session as the agent viewing the ticket or user profile. Every request goes through the Zendesk Apps framework's built-in request proxy, directly between the agent's browser and Zendesk's own servers — Pulse has no server of its own in this data path.

• What it accesses: the events already associated with the ticket requester or the user profile being viewed (native Zendesk events and any custom events your organization tracks), and, only when an agent uses the 'Log event' feature, the requester's name and email — used solely as profile identifiers on the event being created.
• What it stores: nothing. Pulse has no database or backend of its own, and does not persist, cache, or transmit Zendesk data anywhere outside of Zendesk. No analytics or third-party services are used.
• Purpose: strictly to display and record customer activity events inside the Zendesk interface, as configured by your organization.

Requirement: Pulse is built on the Zendesk Events API, which is available on Suite Team plans and above and must be enabled by an admin in Admin Center before use.