Background: A 120-Person B2B SaaS Firm in Munich
This case study is a composite drawn from patterns Forfis has observed across multiple B2B SaaS engagements in Tier-1 European markets. No named customer appears. The company, the metrics, and the timeline are representative of a recurring profile: a mid-size SaaS vendor that has not yet put any AI model into production, runs its support operation on Zendesk, and is under pressure to reduce cost per ticket without adding headcount.
The company in question is a 120-person B2B SaaS vendor based in Munich, selling a project-management tool to mid-market manufacturing and logistics firms across DACH. Its support team of nine handles roughly 400 tickets per week. The CTO had evaluated two AI vendors in the prior quarter but found their pricing models tied to per-ticket volume, which made the unit economics unworkable at the company’s scale. The CFO’s mandate was blunt: cut first-response time by at least 30 percent within one quarter, and keep the solution inside the company’s existing ISO 27001 scope.
Challenge: 4.2-Hour First-Response Time and an ISO 27001 Audit Gap
The support team’s median first-response time was 4.2 hours, with a long tail of tickets sitting 12 to 18 hours because the on-call agent was handling escalations. The root cause was not laziness; it was triage. Every new ticket landed in a single queue. An agent had to read the subject, open the body, check for attachments, determine whether the issue was a bug, a feature request, a billing question, or a data-extraction request, and then reassign the ticket. That manual classification step consumed 6 to 9 minutes per ticket before any substantive work began.
Two operational pressures made the problem urgent. First, the company was in the middle of an ISO 27001 surveillance audit, and the auditor had flagged the support process as a gap: there was no documented, repeatable triage procedure, and no audit trail for how tickets were routed. Second, the company had just closed a Series B and the board expected support cost per ticket to decline year over year, not rise. The CTO needed a solution that was auditable, reversible, and cheap enough to pilot without a six-figure commitment.
Approach: Two-Week n8n Pilot on Zendesk
Forfis ran a two-week fixed-scope pilot. Week one was a process audit: Forfis pulled 30 days of ticket data from Zendesk, coded every ticket by intent, urgency, and attachment type, and identified the three highest-volume categories (password resets, data-export requests, and billing disputes) that together accounted for 62 percent of all tickets. The audit also mapped the existing Zendesk API endpoints, the company’s CRM (HubSpot), and the internal document store where data-export requests were fulfilled.
Week two was build. The n8n workflow ingested new tickets via Zendesk’s webhook, called an OpenAI API for intent classification and urgency scoring, and used a document-extraction model to pull structured fields (customer ID, export date range, file format) from attached PDFs and CSVs. Tickets classified as routine were auto-routed to the correct queue with a draft first-response message. Tickets flagged as high-severity or involving a refund were held in a human-approval node. The entire pipeline ran on the client’s own n8n instance, with API keys stored in the client’s HashiCorp Vault. No regulated data left the building.
Outcome: 43 Percent Faster First Response, 28 Percent Lower Cost per Ticket
The pilot ran for five business days after the build week. The before/after baseline was measured over the same five-day window. Median first-response time dropped from 4.2 hours to 2.4 hours, a 43 percent reduction. The 90th-percentile response time fell from 14.1 hours to 6.8 hours. Triage classification accuracy on the 62 percent of tickets in the three high-volume categories was 94.3 percent, with the remaining 5.7 percent caught by the human-approval gate. Cost per ticket, measured as fully loaded labor cost divided by ticket volume, declined by 28 percent over the pilot window.
The ISO 27001 auditor reviewed the data-flow diagram and the n8n audit log during the surveillance visit. The documented, repeatable triage procedure closed the gap the auditor had flagged. The company did not proceed to a full rollout immediately; the CTO used the pilot data to model the cost of scaling to all 400 weekly tickets and to negotiate a managed-operation retainer with Forfis. The decision to expand was made on the numbers, not on a sales pitch.
Lessons for Similar Teams
- Baseline before you build. The two-week timeline only works if the process audit is done in week one and the build in week two. Skipping the audit and going straight to model integration wastes the pilot. The 30-day ticket coding exercise is not optional; it is what tells you which categories to automate first.
- Scope the pilot to one workflow, not a platform. The pilot automated triage and routing. It did not build a RAG assistant over the company’s help-center articles or automate invoice processing. Keeping the scope to one workflow is what makes two weeks realistic and the decision point clean.
- The human-approval gate is not a compromise; it is the product. For a company under ISO 27001 surveillance, the ability to show an auditor that no automated action touches money or contract terms without human sign-off is what makes the pilot auditable. Do not remove the gate to save two minutes of cycle time.
- Model-agnostic architecture protects the client. The pilot used OpenAI for classification, but the n8n workflow was structured so that the model call is a single node. If the client later wants to run an open-weight model on its own GPU because a data-residency requirement changes, the swap is a configuration change, not a rebuild.
- Hand over the n8n project file. The pilot is not a black box. The client receives the workflow file, the runbook, and the data-flow diagram. If the client’s team can open n8n and read the nodes, the pilot has succeeded even if the client does not proceed to rollout.
Leave a Reply