Bangalore Tech builds compliance workflow software for mid-market companies in India and Southeast Asia. At 180 customers, their support volume had outgrown their three-person team — but they weren't ready to hire a fourth.
The backlog problem
Average response time had drifted to seven days. Not because messages were being ignored, but because every reply required the team to read the full thread, find the relevant documentation, and compose a contextually accurate response from scratch.
"We were spending 60% of our support time on message composition," their founder told us. "And we were still behind."
How drafting changed the math
After connecting their Gmail and uploading their product documentation to the knowledge base, the agent began generating draft replies for every inbound message. Each draft cited the relevant KB article and was calibrated to the customer's plan and conversation history.
The team's job shifted from composing to reviewing. A reply that used to take 20 minutes to write took two minutes to approve and send.
Within three weeks, average response time dropped to same-day. The team's output tripled. No new hire was needed.
The unexpected benefit
The KB gap detection surfaced something the team hadn't noticed: 23% of inbound support questions were about a single feature that had no documentation. The product team wrote three articles. Those questions dropped by 80% over the following month — further reducing volume.
"We thought we had a staffing problem," the founder said. "We had a documentation problem and a drafting problem. Both are solved."