Snyk says its AI support agent resolves over 85% of sessions without a ticket
A new case study explains the staged rollout into Snyk’s core product. The reported resolution rate covers customer use since April, not just the September deployment.
Loading page…
A new case study explains the staged rollout into Snyk’s core product. The reported resolution rate covers customer use since April, not just the September deployment.
Listen to this story
Snyk Assist can answer troubleshooting questions, inspect vulnerabilities and read organization data, but it cannot alter settings, run scans or modify projects; each request receives tools limited by the signed-in user’s permissions. After roughly a year supporting Snyk staff and an April customer-portal launch, Snyk embedded the agent in its core product on September 1. The company reports more than 60,000 queries since April and over 85% of sessions resolved without tickets, making support automation an in-product feature with bounded account authority.
A shared LangGraph runtime serves the assistant through Slack, a web app and direct API access.
Snyk says Assist detected and routed more than 250 support cases to the appropriate teams.
Proposed agent changes must pass evaluation thresholds, including tests for answer quality, instruction-following and secret disclosure.
Snyk’s AI support agent is now inside its core product, rather than confined to a separate support portal. In an October 8 case study published by LangChain, Snyk details the September 1 rollout to every paying customer. It also reports more than 60,000 customer queries handled since April, with over 85% of sessions resolved without a support ticket.
The starting problem was scattered information. Customers’ answers lived across documentation, support articles, release notes, learning materials and account systems. Meanwhile, Snyk’s support team handled thousands of cases every couple of weeks, each requiring classification and routing by product, severity and owner.
Snyk Assist spent roughly a year serving only the company’s support staff. Snyk says that kept early errors internal and exposed edge cases missed by offline tests. Customer access followed in the support portal in April 2026. An August 18 early-access announcement preceded the September move into the core product.
The assistant answers setup and troubleshooting questions, looks up package vulnerabilities and retrieves account information. It can also create a support case or capture a feature request. But Snyk describes access to existing account data as read-only: Assist cannot change settings, ignore issues, run scans or modify projects.
Snyk says it attaches tools to each request according to the signed-in user’s permissions. Account access is limited to the organization and group currently in use. Behind the interfaces, one LangGraph runtime—the software coordinating the agent’s work—serves a Slack app, a web app and direct API access. The team retained that runtime through each rollout phase.
Snyk says Assist detected more than 250 cases and escalated them to the appropriate team.
Snyk records model calls, tool calls and decision points in LangSmith, its agent-monitoring and testing system. Every proposed code change runs the real agent against evaluation suites. Changes that miss agreed thresholds are blocked. The checks cover both answer quality and attempts to make the assistant break its rules.
The reported usage spans more than 500 customer accounts since the April launch. Conversations are categorized by product area, topic, programming ecosystem and error type, giving product managers a map of customer confusion and helping the company improve documentation.
Loading discussion...
Join the conversation
Explain what would convince you that the customer actually got help.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.