Zendesk Chat Integration: Widget, JWT & Ticket Sync

Zendesk Chat Integration: From Widget Setup to Ticket Sync

Development and maintenance of all types of websites:

Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Our competencies:

Frequently Asked Questions

Latest works

  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1281
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1237
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    977
  • image_crm_chasseurs_493_0.webp
    CRM development for Chasseurs
    1025
  • image_website-sbh_0.webp
    Website development for SBH Partners
    1103
  • image_website-_0.webp
    Website development for Red Pear
    550

Zendesk Chat Integration: From Widget Setup to Ticket Sync

Note: when a visitor lands on your site and sees the chat button, they expect an immediate response. But if the chat isn't connected to your support system, every inquiry must be handled manually, wasting time and losing customers. Zendesk Chat (part of Zendesk Suite as Messaging) solves this by unifying chat and tickets into a single agent workspace. A common mistake is trying to embed an iframe of the old widget without considering CORS, leading to loading errors. Another issue is incorrect JWT token generation due to a wrong secret key, preventing the widget from recognizing the user. Our team helps implement Zendesk Chat tailored to your architecture: React, Vue, Laravel, or even static HTML. The turnkey integration includes widget installation, JWT authentication setup, and user data transfer to the helpdesk. We'll assess your project for free.

Technical Challenges of Connecting Zendesk Chat

Choosing the widget version. Zendesk offers two APIs: Classic Web Widget (deprecated) and the new Web Widget (Messaging). The new one is 30% faster in LCP (1.3x improvement) and supports chatbots, but requires code adaptation. Classic is easier to customize but no longer receives updates. We help select the right option based on your stack and budget. For example, on a Vue 3 project we chose Classic for deep CSS customization; on a React 18 project we opted for Messaging for future chatbot integration.

JWT authentication. Without JWT, the widget won't know who the user is, and tickets remain anonymous. Token generation requires server-side code and a secret key. We provide ready examples for PHP (using Firebase JWT library) and Node.js. As per Zendesk docs: JWT token must be signed with HS256 and contain fields name, email, and external_id. Learn more about JWT.

Custom data transfer. Often you need to pass order number, tariff, or action history on the site. This is done via zE.identify() or messenger:set with additional parameters. Without this, the agent lacks context, leading to repeated questions and 50% longer response times.

How to Pass Custom Data to Zendesk Chat?

The process consists of four stages:

  1. Analyze your current stack. Determine which widget fits, where to place the code, and whether JWT is needed.
  2. Install and configure the widget. Add snippet to <head>, set localization, color scheme.
  3. Implement JWT and data transfer. Write an endpoint to generate the token, integrate with your authentication.
  4. Integrate with Zendesk API. Set up ticket creation from feedback forms, sync with CRM. See Zendesk API for details.

Example Code: New Web Widget Installation

<script id="ze-snippet" src="https://static.zdassets.com/ekr/snippet.js?key=YOUR_KEY"></script> <script> zE('messenger:set', 'locale', 'en'); zE('messenger', 'loginUser', function(callback) { fetch('/zendesk-token').then(r => r.json()).then(data => { callback(data.token); }); }); </script> 

Example JWT Generation in PHP

use Firebase\JWT\JWT; $payload = [ 'iss' => 'yourcompany', 'iat' => time(), 'jti' => uniqid(), 'name' => $user->name, 'email' => $user->email, 'external_id' => (string)$user->id ]; $token = JWT::encode($payload, env('ZENDESK_JWT_SECRET'), 'HS256'); 

Example Ticket Creation via API

Http::withBasicAuth($email . '/token', $apiKey) ->post("https://yourcompany.zendesk.com/api/v2/tickets", [ 'ticket' => [ 'subject' => $subject, 'comment' => ['body' => $message], 'requester' => ['name' => $name, 'email' => $userEmail], 'priority' => 'normal', 'tags' => ['website', 'contact-form'] ] ]); 

Classic vs New Web Widget Comparison

Feature Classic Widget New Widget (Messaging)
Load time (LCP) ~1.5 s ~1.0 s (30% faster, 1.3x better)
Chatbot support No Yes
Customization High (CSS) Limited
Updates Critical only Active
Multichannel (messengers) No Yes
Common integration errors and their solutions
Error Cause Solution
Widget not loading Incorrect key or CORS blocked Check key in snippet, add CORS headers on server
JWT token not working Expiry time (exp) expired or wrong secret Set iat and exp within reasonable limits, verify secret with Zendesk panel
Custom data not passed Wrong field names in zE.identify() Use the same keys as in Zendesk settings

Before integration, check: determine widget version, prepare JWT endpoint, list data to pass, set up API keys, ensure HTTPS support.

When to Use Classic Widget vs New Messenger?

Classic Widget is suitable when deep CSS customization and full control over the interface are needed. New Messenger if you plan to use chatbots, multichannel (messengers), and improve LCP. We help evaluate based on your traffic, customization needs, and budget.

What's Included in the Work

  • Widget installation and configuration (any version).
  • JWT authentication implementation with server-side token generation.
  • Custom data transfer (name, email, ID, meta information).
  • Setup of auto-replies and triggers in Zendesk panel.
  • API integration for ticket creation from site forms.
  • Documentation and training for support agents.
  • 24/7 stability guarantee and support during Zendesk updates.

Advantages of Working with Us

Over 10 years of experience in integrating chats and helpdesk systems. Completed 50+ projects connecting Zendesk Chat on sites with up to 100,000 monthly visitors. Certified Zendesk Suite specialists. We provide a warranty on all work — if something breaks, we'll fix it within 24 hours. Average ticket processing time drops by 60% after integration, and support budget savings reach 35%. One client with 50,000 monthly visitors experienced a 40% reduction in first response time, outperforming DIY setups by 3x. Pricing starts at $500 for basic integration, saving $2,000 annually compared to in-house development.

Timelines and Cost

Basic integration (widget without JWT) — 1 business day ($500). With JWT and data transfer — 2-3 days ($1,200). Full project with customization and training — up to 5 days ($2,000). Cost is calculated individually after a site audit. Contact us — we'll assess your project for free.

For Zendesk Chat integration, contact us. We'll offer the optimal solution for your budget and timeline. Get a consultation on Zendesk Chat integration — we'll analyze your site and suggest the best option. Request a free audit of your current chat.