Skip to content
Olive Tree Growth Partners
Explore AI Solutions

CASE STUDY / INTERNAL WORKFLOWS

How an AI-built mini app reduced call center documentation time

Ambitious targets. Tired systems. A small tool built around the work.

By Shelly Phillips · September 24, 2026

The result at a glance

Before35 min/day

After5 min/day

I reduced my own after-call documentation time by about 86% within the first week of using the tool. Those 30 minutes each day became time available for other work.

Firsthand results reported by Shelly Phillips. Approximate daily totals across an eight-hour workday. No company-wide time study or labor-cost savings figure is presented.

The challenge beneath the numbers

While working with incoming customer calls at a Fortune 500 financial technology company, I saw a gap between performance targets and the tools available to reach them. Leadership tracked handling time, productivity, transfers, and issue resolution. Proper documentation still required repetitive manual work.

Information had to be entered into several places. Notes needed consistent formatting. Even with extensive customer service experience, I needed extra time after calls to create the record the business required.

A small application with a clear purpose

I built a lightweight internal application with the help of an approved large language model. I am not a software developer. Knowing the work firsthand helped me define exactly what the tool needed to do.

  • Use dictation where it was faster than typing.
  • Pre-fill fields with information entered once.
  • Copy a section in one click instead of retyping it.
  • Apply consistent formatting automatically.
  • Guide agents with prompts for the details they needed to collect.

The application supported the documentation workflow. People continued to serve customers and use their judgment.

Tested on my own calls first

Before the tool, I spent roughly 35 minutes a day completing after-call documentation. With it, that fell to 5 minutes. The improvement appeared within the first week.

At that daily rate, 200 working days would represent 100 hours of capacity returned to one person. This is an illustration based on the observed daily time difference, not a measured annual result or a claim of payroll savings.

From one workflow to wider adoption

The tool was adopted across the customer support division. As described in my September 2026 account, it remains in use company-wide. I own the application, and the company uses it with my permission.

The company is not named in this case study. The measured before-and-after figures above relate to my own work.

What this means for your business

Repeated data entry and scattered documentation can quietly consume paid hours. A focused tool can help your team reclaim capacity when it addresses a real bottleneck. Whether that becomes lower overtime, room for more clients, or faster service depends on how the business uses the time.

My work starts with your people and the problems they face. We examine the workflow, identify what is slowing it down, and decide what is worth building. Clear responsibilities and human review help the improvement take root.

AI clears the ground so people can do the work that needs their judgment, care, and experience.

Questions about AI-built internal tools

What changed after the mini app was introduced?

On my own calls, after-call documentation fell from roughly 35 minutes across an eight-hour day to 5 minutes within the first week. That is about 30 minutes returned each day, an approximately 86% reduction. These figures describe my experience, not a measured average across the company.

What did the application do?

It supported dictation, reused information already entered, pre-filled fields, copied sections with one click, standardized formatting, and provided prompts for the information agents needed to collect.

How was AI used?

I used an approved large language model to help build the application. Understanding the work and specifying what the tool needed to do came first. This case describes an AI-assisted build, not an autonomous agent replacing customer service staff.

Can this approach help a smaller business?

The same kinds of friction appear in service businesses: repeated data entry, inconsistent notes, and information moving between systems. We begin by reviewing the workflow, then assess whether a focused tool would be useful. Scope, timing, cost, and results depend on the business.

Who owns the application?

I designed and built the application and retain ownership. The company uses it with my permission.

PLANT TODAY. PROSPER TOMORROW.

Where is your team losing time?

Bring the repeated task, documentation backlog, or workflow that keeps slowing people down. Let’s discuss a practical solution.

Book a call with ShellyBring your questions. Start with a conversation.