Full-Time
Updated on 9/3/2026
Subscription CRM software for customer service
$182k - $272k/yr
Madison, WI, USA + 2 more
More locations: San Francisco, CA, USA | Austin, TX, USA
Hybrid
In-office part of the week; schedule determined by the hiring manager.
See people who can refer or advise you
Zendesk provides cloud-based customer service and support software that helps businesses manage customer interactions. It offers a suite of tools (ticketing, live chat, analytics) as part of a subscription-based CRM platform designed to streamline support workflows across industries. The product works as a scalable cloud solution: organizations choose pricing tiers, implement ticketing and chat in their support channels, track performance with analytics, and use training and certification resources to maximize use. What sets Zendesk apart is its broad, adaptable platform tailored for companies from startups to enterprises, extensive integrations, and a clear focus on service-first CRM, with a recurring revenue model built on subscriptions. The company’s goal is to help organizations improve customer service operations, boost efficiency, and enhance customer satisfaction and loyalty by making support processes easier to manage.
Company Size
5,001-10,000
Company Stage
IPO
Headquarters
San Francisco, California
Founded
2007
See people who can refer or advise you
Help us improve and share your feedback! Did you find this helpful?
Hybrid Work Options
Flexible Work Hours
NetSuite-Zendesk sync: eliminate credit memo reconciliation errors. Manual credit memo reconciliation between NetSuite and Zendesk costs enterprises 15+ hours weekly. Automating this sync reduces errors by 95% and cuts audit time from days to minutes. Every month, finance teams at mid-market enterprises waste 15-20 hours reconciling credit memos between NetSuite and Zendesk. The process begins with exporting CSV files from both systems, cross-referencing ticket IDs against refund records, and manually adjusting GL entries when discrepancies arise. A single misaligned credit memo - whether due to a typo in NetSuite's refund application or a Zendesk agent's incorrect ticket closure - can trigger a 3-day audit cycle to trace the root cause. For companies processing 500+ refunds monthly, this isn't just tedious; it's a systemic bottleneck that delays month-end close by an average of 2.3 days, according to NetMint's connector documentation. The breakdown isn't just in the volume. It's in the handoffs: NetSuite's refund application module doesn't natively track Zendesk ticket statuses, while Zendesk's credit memo fields lack NetSuite's GL impact granularity. When a customer disputes a refund in Zendesk, agents often create duplicate tickets or mislabel credit memos, forcing finance to reconcile the same transaction twice. The result? A spreadsheet maze where 1 in 5 credit memos requires manual intervention, per SyncApps' integration case studies. For a company with $50M in annual revenue, the labor cost of manual reconciliation alone exceeds $18,000 annually - assuming $35/hour for a mid-level accountant and 15 hours weekly. But the real expense is opportunity cost. Each hour spent firefighting credit memo discrepancies delays financial reporting, eroding investor confidence and complicating tax filings. In industries like SaaS or e-commerce, where refund velocity correlates with churn risk, delayed reconciliations can mask cash flow leaks until they're severe enough to trigger an audit. The secondary costs are harder to quantify but no less damaging. Spreadsheet errors propagate into NetSuite's revenue recognition reports, risking SOX compliance violations. Meanwhile, Zendesk agents waste 8-10 minutes per ticket resolving refund disputes that could've been auto-closed with accurate credit memo data. Multiply this by 1,200 tickets monthly, and the cognitive overhead alone justifies automation. As Zapier's NetSuite-Zendesk integration guide notes, even 'minor' discrepancies can cascade into compliance risks when left unchecked. Bear Systems' integration leverages NetSuite's SuiteTalk REST API and Zendesk's Support API to create a bidirectional sync that propagates credit memo statuses in real time. The workflow begins when a refund is processed in NetSuite: the system pushes the credit memo's ticket ID, amount, and GL impact to a middleware queue (AWS SQS), where Bear's AI agent validates the data against Zendesk's ticket status. If the ticket is closed with a 'refund issued' tag, the agent triggers a confirmation in NetSuite's refund application module, eliminating the need for manual GL adjustments. For Zendesk-side updates, the process reverses: when an agent marks a ticket as 'credit memo issued,' the AI agent cross-references the ticket ID with NetSuite's refund records. If no matching credit memo exists, the agent flags the discrepancy for finance review via Slack/Teams. This eliminates the 'orphaned refund' problem, where credit memos sit unapplied in NetSuite for weeks. The integration also enforces data schema alignment - NetSuite's refund fields map directly to Zendesk's custom credit memo attributes, ensuring consistency without manual mapping. For a $75M revenue company processing 800 refunds monthly, Bear's integration delivers $42,000 in annual labor savings - assuming $40/hour for finance staff and 20 hours of weekly reconciliation time. The error rate drops from 20% to under 1%, cutting audit cycles from 3 days to under 30 minutes. More critically, the integration reduces month-end close delays by 2.1 days on average, enabling faster financial reporting and board presentations. The strategic value extends beyond cost savings. With credit memo data flowing seamlessly between systems, finance teams can now generate real-time refund analytics - e.g., tracking refund velocity by product line or agent - to identify churn risks proactively. Compliance teams benefit from automated audit trails, as every credit memo sync is logged with timestamps and user attribution. Compared to generic connectors like Zapier's NetSuite-Zendesk integration - which lacks AI-driven discrepancy resolution - Bear's solution reduces false positives in reconciliation by 70%, per internal benchmarks. A full rollout takes 6-8 weeks, starting with a 2-week discovery phase to map NetSuite's refund workflows and Zendesk's custom fields. Prerequisites include NetSuite's Advanced Financials module (for GL-level credit memo tracking) and Zendesk's Professional tier (to enable custom credit memo attributes). The integration requires API rate limit adjustments in both systems - NetSuite's SuiteTalk API caps at 5,000 calls/hour, while Zendesk's Support API allows 100 calls/minute - so throttling logic is baked into the middleware. Common pitfalls include unstandardized ticket IDs (e.g., NetSuite's refund ID vs. Zendesk's ticket number) and misaligned refund amounts due to currency conversions. Bear Systems mitigates this with a pre-sync validation step that flags mismatches before they propagate. Another risk is agent pushback: Zendesk teams may resist adopting new credit memo workflows if the UI changes aren't intuitive. To counter this, Bear provides a pre-built Zendesk macro that auto-populates credit memo fields based on NetSuite's refund data, reducing agent friction by 60%. Generic connectors like SyncApps or Zapier can sync NetSuite and Zendesk, but they lack the AI-driven discrepancy resolution and compliance logging required for credit memo reconciliation. NetMint's connector, for example, handles basic data sync but doesn't enforce GL-level accuracy or provide real-time audit trails. For enterprises where refund errors can trigger compliance audits or investor scrutiny, a purpose-built integration isn't just faster - it's lower-risk. Bear Systems' approach combines NetSuite's financial rigor with Zendesk's operational agility, ensuring that credit memo data is both accurate and actionable. If your team is still wrestling with spreadsheets or firefighting refund disputes, the next step isn't another tool - it's a conversation about how to eliminate the manual loop entirely. Audit your current credit memo reconciliation process this quarter; if it's costing more than $15,000 annually in labor or delaying financial close, it's time to talk. Free Business Automation Audit Discover how much time and money your team can save by automating manual workflows and integrating enterprise systems.
Building securely from day one: Palo Alto Networks partners with the Zendesk Startup Program. Sep 02, 2026 A secure workspace for your team - so you can focus on building, not on what could go wrong. Every customer support agent starts their day the same way: opening a browser, logging into Zendesk, and handling sensitive customer interactions. For most early-stage teams, that workspace is completely unprotected. The browser is where your people work, where your customer data lives, and where most security incidents begin - yet it's the layer that gets secured last, if at all. AI is now part of everyday work. Your team is using agents and AI-powered workflows to move faster. But as your AI usage scales, so does your exposure: sensitive customer data, keys, source code, credentials, and proprietary information can flow into unvetted AI tools without anyone noticing - including you. And the browser is where all of it happens. The startup ecosystem thrives when founders can focus on building. That's Palo Alto Networks partners with the Zendesk Startup Program to provide early-stage teams access to the same browser security used by large enterprises - so startups are not forced to choose between preserving runway and protecting their customers' data. A secure workspace, not just a secure browser. Picture this: a support agent on your team gets a convincing phishing email that looks like a familiar notification. They click the link, land on a spoofed login page, and enter their credentials. Within hours, an attacker has access to your support system, and every customer conversation, ticket, and piece of sensitive data inside it. You find out when a customer calls to ask why your support team reached out, asking for payment details. This isn't a hypothetical. It's how many small business breaches actually play out - and it's exactly what PBB stops. Palo Alto Networks, Inc. use Palo Alto Networks's Precision AI-powered security to recognize the destination as malicious and block it before the page ever loads. No credentials entered. The agent sees a warning and moves on with their day. That's the core idea behind Prisma Browser for Business: a secure workspace that sits at the intersection of work, AI use and threats - the browser. PBB wraps your entire browser session in enterprise-grade security, protecting every app, every tab, and every interaction, without requiring your team to change how they work. For Zendesk users specifically, PBB can be configured with Zendesk as a dedicated workspace app - automatically applying the right security policies to everything Zendesk-related the moment your team opens it. Phishing attempts are blocked. Data leakage from support conversations is prevented. And your agents work inside a protected environment without any extra steps on their end. The result: your team gets a seamless experience, and you get end-to-end visibility and control over how Zendesk is accessed across every device on your team. The security gap startups can't afford to ignore. When you're building a company, security can feel like something to tackle later - after the product ships, after the team grows, after the next funding round. But phishing, malware, and data leakage are not enterprise problems. They're startup problems too - and they can be significantly more damaging when you don't have a dedicated security team to catch them. Three risks in particular are growing fast for early-stage teams: * AI tools without guardrails. Your team is almost certainly using AI tools - Claude, ChatGPT, Copilot, and others - to move faster. But without controls in place, sensitive customer data, internal documents, and proprietary information can flow into these tools without anyone noticing. PBB lets you set guardrails around how AI tools are used in the browser, so your team can stay productive without inadvertently exposing data they shouldn't. * Unvetted browser extensions. Extensions are one of the most overlooked attack surfaces in any organization. A single malicious or compromised extension can silently capture credentials, intercept data, or give an attacker persistent access to your environment. PBB gives you control over which extensions can be installed across your team's browsers, and alerts you when a suspicious or malicious extension is detected - before it can do damage. * Phishing and malware. The browser is the primary delivery mechanism for both. PBB blocks malicious sites and stops malware downloads in real time, protecting your team and your customer data at the point of risk. PBB brings all of this together in a way that is simple to deploy and easy to manage - no security expertise required, no complex infrastructure to stand up. Built for where startups actually are. The Zendesk Startup Program is designed to support founders from their earliest stages through scale - including when security becomes a core business priority. Startups eligible for the program can access PBB as a practical way to evaluate enterprise-grade workspace security without a large upfront commitment. It's a way to build securely from the start, preserve runway, and scale your operations with confidence. As a rapidly growing startup, you shouldn't have to choose between moving fast and staying secure. * The browser is your biggest security gap - and it's where startups get hit first. Phishing, credential theft, malicious extensions: these aren't enterprise problems. They're startup problems, and they land in the browser before you even have a security team to respond. * Security doesn't have to slow your team down. PBB applies enterprise-grade protection automatically - no behavior change required from agents, no complex infrastructure to stand up. Your team works exactly as they do today, just inside a protected environment. * Build securely from day one, without the day-one security budget. Leverage protection large enterprises rely on - so you don't have to choose between your runway and your customers' trust. Ready to get started? Startups participating in the Zendesk Startup Program are eligible to apply for PBB as part of their program benefits. Visit the Prisma Browser for Business dedicated landing page for Zendesk to take advantage of its partner's promotion.
Claret Capital Partners has invested in EdgeTier, a Dublin-based AI-powered customer service intelligence platform, through its Fund IV. Founded in 2017, EdgeTier employs over 70 people and serves more than 50 enterprise clients across Europe and the US, including TUI, Abercrombie & Fitch, Ryanair and Wolt. EdgeTier's platform analyses customer conversational data in real time, providing insights into emerging issues and agent performance trends. The agentic AI-powered system integrates with major customer support platforms such as Salesforce, Zendesk, Genesys, NICE, Intercom and LivePerson. CEO Shane Lynn said the investment will help EdgeTier scale its platform and expand globally. EdgeTier's existing investors include Smedvig, ACT Ventures and Episode 1.
Amplify your strengths not your sins - Sealy on the reality of AI in CX. When Michael Chen joined premium Australian mattress manufacturer Sealy Posturepedic nearly 7 years ago, centralising the fragmented CX function was his first priority. Laying the right foundations with the CX team, before introducing process automation tech, was most important. "People, culture, processes, come first and then and only then the technology. If you have people problems, gaps in your existing teams and culture, AI will only help you to experience those things faster," says Michael Chen. Sealy's Head of Digital and CX. "But if you have helped your team to understand that the technology will help to make them more efficient, that AI is a tool to help them, not replace them, then your CX people will deliver measurably better customer service outcomes." Sealy's AI journey. Sealy's AI journey began during the Covid lockdowns. Incoming customer calls and messages "skyrocketed" and response times blew out. The Executive Team initially considered hiring more people but movement restrictions meant that was not doable. "So we landed on tech solutions, including co-pilot agents, that allowed us to do more with our existing team. From there, our vision broadened from just wanting to clear the backlog to creating a solution for our operating model that we can scale up and down as required and make us more efficient," Chen explained. "It wasn't all about what technology are we buying, more about how we can take our team with us on the journey because the CX model that had worked for us for the previous 20 years no longer did. We went looking for a strategic solution that was going work for us for the next 20 years." That led Sealy to adopting the Zendesk platform and its co-pilot agents before, very recently, integrating Zendesk's AI agents into their customer-facing operations. "Sealy's initial results with Zendesk's AI agents are very encouraging. Customer retention is up 100%. Our team capacity is up 30% and we maintained a 90% CSAT score while rolling out AI," according to Michael. Judgement and empathy. The judgement, empathy, the high values skills of the human agents, are central to this success, he believes. "It's human agents with the right mindset who have the ability to really connect with customers, solve problems, reassure them and build trust. Our people kept our CSAT at 90%. People who can really focus on people and understanding customer needs, they're going to become more important to us in future." The company is still relying heavily upon CSAT to track customer satisfaction. "Immediate data is less important because we have a lot of data points in the past, so we look at the overall trend data going through but its early days for us so we will see," Chen notes. Sealy have deliberately pursued AI implementation in small steps, making it easier for the Executive team to measure ROI and manage operational adaptation, including training. "Start small, don't do everything at once," is Chen's advice. "Focus on good process culture. Launch one or two things. Get your agents comfortable, get the business comfortable, get some runs on the board, this will help you do the rest of the implementation a lot better too," Michael says. Sealy are currently using AI agents for chat customer engagement. Voice enquiries are still going to a 100% human contact centre, less than a month into the implementation phase. Chen appreciated having a technology service partner who played an active role in Sealy's journey. "When we started deploying AI tools, we wanted to see how they could help us with our existing processes. You want to make sure the tools are helping the human agent. Getting wins at the beginning, gets the human buy-in you need to succeed." "Co pilots have many, many capabilities. So what we initially selected was what we thought would benefit the agents. When we launched co pilots, we did not have a clear expectation but with call times immediately reduced by 2-3 minutes this allowed us to redeploy those extra resources. We were able to show the Executive Team 'yeah we've spent this money on technology but we're going to get a return on it," Chen recalls. "With a co pilot, everything is shared with human agents but with AI the machines will respond to customers without a human watching over them. So, for the two weeks of AI implementation, we closely monitored what the AI agents were doing during the day and turned them off at night. We've only just moved to leaving the AI agents on over the weekend." "It's constant learning. Constantly adjusting, optimising, the technology while you are learning about it and the technology itself is improving so quickly," Chen says. "Initially, implementation is very resource intensive but we are already seeing 40% to 50% of chats are automated which is better than we initially anticipated. If people want to know 'do you have stock of an item' or how is their ticket progressing, our AI chatbots can give customers that information right away at 3am. Or they can get that information from our website, whichever they prefer." Adopting a hybrid-AI system has also highlighted the importance of having accurate, detailed and up to date information on the website and other company digital information channels that AI agents rely upon to generate answers for customers.
CX-News: August 13, 2026 - smarter channel routing withless management. Posted by: Brett Rush August 13, 2026 Customer Experience News is a weekly newsletter about the most important news and discussions for Customer Experience and Customer Support Leaders. Intercom adds channel routing and Telegram support. News Summary Intercom, a customer service platform combining shared inbox, ticketing, and AI powered Agents, announced two updates. Teammates can now route work by channel without splitting their inbox, choosing exactly which channels they handle, including email, Messenger, SMS, and phone, in any combination. Telegram is also now a supported channel, letting teams connect a Telegram bot and manage Telegram conversations alongside every other channel in the inbox. Operational Impact Support Specialists can specialize in the channels they know best while the team keeps one shared queue with assignments balanced across every channel, cutting down the coordination work of managing separate inboxes per channel. The Telegram addition extends that same shared inbox to one more channel, and Fin can resolve Telegram questions automatically, extending automated deflection to a channel that previously required a manual workaround. Implementation Considerations Each teammate needs to set their own channel selection from their profile or the Inbox Dashboard Teammate View, so rollout benefits from a short internal announcement. Teams with layered routing rules, such as language or product based specialization, should confirm the new channel selection interacts correctly with those rules. Teams that already run automated workflows and CSAT collection on other channels need to confirm those workflows also apply correctly to Telegram, and brands with a meaningful Telegram audience should weigh setup time against actual message volume before prioritizing it over other backlog work. Zendesk adds live transcription for Voice Agents. News Summary Zendesk, a customer service platform used across support, sales, and IT teams, announced live call transcription for Voice Agents. Agents can now view real time transcripts during voice calls, with speaker labels, searchable text, timestamps, and language switching. Operational Impact Support Specialists no longer need to rely on memory or post call notes to capture what a customer said, since the transcript is visible while the call happens. Searchable, timestamped transcripts also make it easier to pull up a specific moment in a call for coaching or dispute resolution instead of re-listening to a full recording. Implementation Considerations Live call transcription is available for Zendesk Voice with the Copilot add-on, so teams without that add-on need to confirm licensing before planning around this feature. Teams operating in multiple languages should test the language switching behavior on real calls, since transcription accuracy on accented speech or mixed language conversations varies and is worth verifying before frontline reliance. Gorgias ships chat discovery and agent statuses. News Summary Gorgias, a customer service platform built for ecommerce and Shopify brands, announced two updates. Shoppers can now explore similar products with one tap inside chat, seeing a More Like This option when the Agent recommends a product. Admins and team leads can also add custom agent unavailable statuses, such as Lunch, Break, In A Meeting, or In Training, instead of a single generic offline status. Operational Impact Support Specialists benefit indirectly from the product discovery feature, since shoppers can browse alternatives themselves within the conversation instead of asking an agent for more options or leaving the chat to search the site separately. The custom statuses give team leads visibility into why someone is unavailable rather than only that they are offline, which helps with staffing decisions during high volume periods. Implementation Considerations The product discovery feature depends on the Agent already having accurate product catalog data, so brands with incomplete or outdated product feeds may see irrelevant suggestions. Teams should review a sample of recommendations after rollout to confirm they match brand merchandising intent. For custom statuses, admins need to create them in Settings under Agent Unavailability before teams see any difference from the current single offline status, and teams should agree on a consistent status list across the organization before rollout. Help Scout adds Twilio SMS support. News Summary Help Scout, a shared inbox platform built for SaaS and growing support teams, announced support for connecting a Twilio number directly to Help Scout. Teams can now manage two way SMS conversations alongside email, chat, and social channels from the same shared inbox. Operational Impact Support Specialists can reply to SMS conversations from the same interface they already use for email and chat, rather than switching to a separate SMS tool and losing conversation history in the process. Live character counts show exactly how many messages a reply will send as before hitting send, which helps avoid the extra cost or fragmented delivery of an unexpectedly long SMS reply. Implementation Considerations Teams need their own Twilio account and number before connecting the channel, so this is not a zero setup integration. Organizations relying heavily on SMS for time sensitive updates should confirm their existing automation, tagging, and reporting rules extend correctly to the new channel rather than assuming SMS behaves identically to email inside Help Scout. Kustomer streamlines company hierarchy editing in sidebar. News Summary Kustomer, a customer support platform built around a unified customer timeline, announced an update that lets Support Specialists edit a company's hierarchy directly from the sidebar. Assigning and managing company relationships now happens without navigating away from the sidebar's current view. Operational Impact Support Specialists working with multi entity accounts, such as franchises or parent and subsidiary organizations, can update relationship data in the moment a conversation surfaces it, rather than stepping out of the ticket to make the change elsewhere. Keeping hierarchy edits inside the sidebar also reduces the chance of losing context on the company a Support Specialist was originally viewing. Implementation Considerations This update matters most to teams that actively maintain company hierarchies as part of their support workflow, such as B2B support teams tracking parent accounts and subsidiaries. Teams that do not use the Hierarchy tab today will not see a meaningful change, so this is a smaller quality of life update rather than a workflow overhaul. Gleap brings AI Agents into ticket conversations. News Summary Gleap, a customer support and product feedback platform, announced that AI Agents now work directly inside support tickets rather than in a separate panel. Support Specialists can mention an Agent in the composer to hand off a task, watch its steps appear in the conversation timeline, and step in if the Agent needs input. Operational Impact Support Specialists no longer need to leave the ticket to see what an Agent tried or asked, since agent runs now appear as messages in the same timeline as human replies. A full activity log for any run, available in one click, also makes it easier to catch an Agent that is heading in the wrong direction and stop it before it responds incorrectly to a customer. Implementation Considerations The update also introduces reply threading, a rebuilt conversation view, and a keyboard driven command palette, so teams should expect a short adjustment period alongside the AI Agent changes. Teams with existing automations or Agent permission rules should confirm those carry over as expected before rolling this out broadly, since a redesign this size touches most of the day to day inbox experience. Now this is: Strategic support for CX Leaders. You've got ambitious Support targets and new metrics but you're not sure what to prioritize first. The list is long, the queue is getting longer, and you don't have time to step back and think about CX strategically. What if you could pressure test your thinking with someone who has spent 20 years building Customer Support operations? No pitch, just a conversation.