Case Study
A UK B2B SaaS company with 9,400 active accounts deployed a custom AI chatbot built by Softomate on GPT-4o + RAG, reducing Tier-1 support tickets by 60%, cutting first-response time from 41 minutes to 28 seconds, and recovering the build cost within 5 months.
1 min read By Deen Dayal Yadav, Founder & AI Automation Director
UK-based B2B SaaS, 9,400 paying customers, 11-person support team
A UK B2B SaaS company with 9,400 active accounts deployed a custom AI chatbot built by Softomate on GPT-4o + RAG, reducing Tier-1 support tickets by 60%, cutting first-response time from 41 minutes to 28 seconds, and recovering the build cost within 5 months.
UK-based B2B SaaS, 9,400 paying customers, 11-person support team
A UK B2B SaaS company with 9,400 active accounts deployed a custom AI chatbot built by Softomate on GPT-4o + RAG, reducing Tier-1 support tickets by 60%, cutting first-response time from 41 minutes to 28 seconds, and recovering the build cost within 5 months.
A UK-headquartered B2B SaaS company providing project-management software to professional services firms had reached a scaling inflection point that its support function could not absorb. With 9,400 paying customers across the UK and Ireland, monthly support volume had grown to 5,200 tickets, of which the support team itself had quantified that around 64% were repeat questions answerable from existing product documentation, in-app data, or account-state information already held in the platform's own database. The team of 11 support engineers was, in practice, spending the majority of its hours repeatedly answering the same dozen or so questions with slightly varied phrasings.
The product was good, the customer base was loyal, the renewal rate was over 91%, and yet the support function had become the single biggest operational drag on the business. The head of support had run an audit during the previous quarter and found that the average customer who contacted support waited 41 minutes for a first response during weekday hours, and over 6 hours outside of them. Customer satisfaction scores on post-interaction surveys had drifted from 4.4 out of 5 down to 3.9 over the previous twelve months, and the company's own NPS tracker showed a clear inverse correlation between average response time per customer cohort and likelihood to recommend.
The cost structure compounded the problem. The team was already operating at full capacity, with no slack for product-launch traffic spikes or unusual incident windows. Adding two further support engineers to absorb the growing volume would cost roughly ?124,000 fully loaded per year. That hire was already approved in principle but would not solve the underlying issue, which was structural: most of the support work was data-lookup and documentation-reference, not genuine problem-solving. Throwing more people at a documentation-shaped problem was, the head of support privately acknowledged, the wrong response.
The CTO had explored two off-the-shelf chatbot products before approaching Softomate. The first was a popular helpdesk-builder add-on that promised AI auto-replies. In practice, it could only respond to exact keyword matches from a pre-built FAQ library, which meant any rephrasing of a common question fell through to a human anyway. It was abandoned after a two-month pilot during which it deflected less than 3% of total volume. The second was a more sophisticated platform offering RAG-style retrieval over documentation, but it could not connect to the SaaS product's own database to look up actual account-state, meaning it could not answer questions like ?why was I charged twice in November? or ?when does my current plan renew? with any specificity. Customers found those generic responses more irritating than helpful, and the trial was cancelled within six weeks.
The CTO's brief to Softomate was specific. Build something that could answer documentation-style questions with the accuracy of a senior support engineer, look up actual account data live from the platform's own database to give personalised responses, hand off cleanly to a human when escalation was genuinely needed, and write a complete conversation summary back into the support ticketing system so that escalated tickets arrived in human queues with full context. Do all of this within an eight-week build window and integrate with the company's existing Zendesk and PostgreSQL data warehouse without requiring any production database changes.
Softomate's discovery phase mapped the existing support workflow in detail and analysed three months of historical Zendesk tickets to categorise every question type by frequency, complexity, and the specific data source needed to answer it. The output was a clear priority matrix. The top 14 question types accounted for 71% of all volume and could every one of them be answered by a chatbot with read access to the product's customer-state data, the billing system, and the documentation library. Categories like ?why was I charged X?, ?how do I export Y?, ?is feature Z available on my plan?, and ?what does this error message mean? were the bulk of inbound volume.
The chatbot architecture used GPT-4o for the language model layer with a retrieval-augmented generation system over three integrated data sources: the product's user-facing documentation (110 articles across six product modules), the customer's own account-state pulled live from the production database via a read-only API gateway, and the billing system pulled live via Stripe's API. The vector store was built on the documentation corpus and queried via semantic search, so that customer queries reached the correct policy or how-to snippet even when phrased unusually. The account-state lookups were structured queries against pre-defined intent classes, not free-form database queries, which kept the security model tight and predictable.
A critical part of the build was the escalation logic. The chatbot was trained to recognise four classes of query that required human handover: any billing dispute over ?100, any data-loss or potential-bug report, any explicit request for a human, and any query that could not be confidently answered within three retrieval attempts. On escalation, a structured handover summary was generated automatically, including the customer's identity, the specific question, the relevant account-state already retrieved, and the chatbot's best-effort interpretation of the underlying intent. This summary was attached to the Zendesk ticket as a private internal note so the assigned support engineer saw the full context the moment they opened the ticket.
Brand voice calibration matched the proven pattern from previous Softomate engagements. Softomate's team analysed 180 of the support team's highest-rated historical responses, categorised by tone (warm-formal vs technical-precise vs apology-and-resolution) and used them as the training corpus for the model's response style. The head of support reviewed 200 generated responses across the full intent spectrum before launch and signed off on the tone, with 14 specific tonal corrections applied to the prompt scaffolding before the pilot opened.
The build was deployed in a phased rollout over three weeks. Week one was a closed pilot with five internal users acting as customers. Week two opened to 5% of real customer traffic, with every chatbot conversation reviewed daily by Softomate and the head of support together. Week three opened to 100% of inbound chat traffic with continued daily monitoring. Twenty-one targeted refinements were made across those three weeks, most of them to the documentation knowledge base where the chatbot had given technically correct but tonally awkward answers about pricing tiers.
The technical stack deserves explicit mention because it was a deliberate choice. GPT-4o was selected over GPT-4o-mini for tonal reliability after side-by-side testing on 80 representative tickets. The retrieval layer was built on a self-hosted vector database (Qdrant) rather than a hosted alternative, because the SaaS company's compliance team required all customer-data-adjacent infrastructure to run inside their existing UK AWS region. The Zendesk integration used Zendesk's native API rather than a third-party connector, which added two days to the build but eliminated a per-ticket integration cost that would have compounded over time.
Within the first 90 days of full deployment, Tier-1 ticket volume handled by human engineers fell by 60%. The chatbot successfully resolved 3,120 of the average monthly 5,200 tickets without human escalation. Average first-response time across all ticket types dropped from 41 minutes to 28 seconds. The remaining 40% of tickets routed to humans were genuine complex cases, and engineer average response time on those improved to 14 minutes (from 41), because the queue had collapsed and engineers were no longer triaging high volumes of repeat questions before reaching the cases that actually needed them.
Customer satisfaction scores on post-interaction surveys rose from 3.9 to 4.5 out of 5 for chatbot-handled interactions, and from 4.0 to 4.6 for human-handled interactions (the latter rising because human time was now focused on harder problems where deeper engagement made a measurable difference to outcome). The company's NPS tracker moved from 38 to 52 across the same period, an improvement the CTO directly attributed to the response-time change in a board-level review.
The two-engineer hire originally approved was cancelled. The existing 11-person team had visible capacity for the volume reaching them, and the head of support reallocated 1.8 FTE worth of recovered time into a proactive customer success function that the company had wanted to build for over a year but had never had the headcount for. That function generated 14 expansion-revenue opportunities in the first quarter of operation, worth approximately ?47,000 in additional ARR.
Total Softomate engagement cost was recovered within 5 months of go-live, driven primarily by the avoided hire cost. The chatbot has since been extended to handle two additional ticket categories that were originally scoped out as too complex: feature-request triage and integration-troubleshooting for the platform's top 6 third-party integrations. Both extensions were delivered as configuration changes rather than new builds.
The unexpected outcome was operational intelligence. Because every interaction was logged with structured intent tagging, the product team gained a real-time view of which features generated the most customer confusion. A consistent pattern of questions about the platform's permissions model led directly to a UX redesign in the following quarter that removed an entire category of tickets at source. Softomate provides quarterly review sessions and adds new intent categories as the product evolves.
Related service:AI Chatbot Development Service London. Further reading:Custom AI Chatbot vs ChatGPT, How to Build a Custom AI Chatbot and No-Code AI Tools vs Custom AI Development. Related case study:AI Chatbot for London Letting Agency.
Anonymised client engagement. Identifying details modified for confidentiality. Outcome ranges reflect typical results from similar projects.
Names withheld to preserve confidentiality.
Names withheld to preserve confidentiality.
Work with us
Every project we take on has a measurable outcome. Talk to our London team and we will show you exactly how we would approach your challenge.
Softomate Solutions Limited
Deen Dayal Yadav
Online