Case Study ยท Kitchen Fabrication / AI Automation

Automation, AI & CRM Systems for Service Businesses

Every Order Update. One Click.

Zero Manual Entry.

How we connected a Google Sheet to GoHighLevel's AI receptionist so Kitchen Made New could update their entire AI knowledge base โ€” voice and web chat โ€” with a single button click and no technical knowledge required.

Company

Kitchen Made New (KMN)

Industry

Kitchen Fabrication & Restoration

Platforms

GoHighLevel ยท Google Apps Script ยท Make.com

Type

AI Knowledge Base Automation

Live Since

August 2025

1 Click

Updates the entire AI knowledge base โ€” voice and web chat simultaneously

Real-Time

Order status delivered to customers on first call โ€” no lag

0

Manual data re-entry steps after setup

49

Calls Handled by AI

54

Actions Triggered

100%

Positive Customer Sentiment

01 โ€” Context

An AI Receptionist Only as Good as Its Last Manual Update

Kitchen Made New (KMN) is a kitchen fabrication and restoration company serving residential and commercial clients. As part of their customer experience strategy, KMN integrated an AI receptionist into GoHighLevel โ€” giving customers real-time order tracking, service updates, and FAQ answers through both voice and web chat.

The AI was central to how KMN handled inbound calls โ€” particularly from manufacturing clients whose end-customers called multiple times per day asking where their orders stood. The system worked. But only as long as someone kept manually feeding it accurate data.

02 โ€” The Problem

Manual Updates Were Becoming a Bottleneck

Every time an order changed status, a staff member had to stop what they were doing, open GoHighLevel's knowledge base, find the right entry, type the updated information, and save it. With a growing volume of active orders across both residential and manufacturing clients, this manual step was becoming unsustainable โ€” and the AI was starting to give customers outdated answers.

  • โœ•One manual update per order status change. Every time an order moved through production, a staff member had to interrupt their workflow to update the AI separately.
  • โœ•Outdated information reaching customers. Missed or delayed updates caused the AI to give callers incorrect order status โ€” eroding trust on high-volume inbound days.
  • โœ•Unsustainable at scale. As order volume grew, the number of manual knowledge base updates per day grew with it โ€” with no ceiling in sight.
  • โœ•Voice AI and web chat were not synced. Updating one channel did not update the other โ€” customers could get different answers depending on how they contacted KMN.
  • โœ•No confirmation of accuracy. Staff had no way to verify what the AI was currently saying without logging into GHL and manually checking โ€” adding even more overhead.

The AI was only as accurate as the last person who remembered to update it. With dozens of active orders at any time, that gap was widening โ€” and customers were starting to notice.

03 โ€” The Solution

Google Sheet โ†’ One Button โ†’ Both AI Channels Updated in Seconds

We designed a centralized Google Sheet connected to a custom Google Apps Script. Staff input order changes in one structured table โ€” the same place they were already working. With a single button click, the script reads the Sheet, formats the data, routes it through Make.com, and pushes it directly to GoHighLevel's AI knowledge base via the GHL API. Both the voice AI and the web chat widget update simultaneously from the same source.

  • 1Structured Google Sheet as single source of truth. All order status and FAQ data lives in one table โ€” the same one staff were already maintaining.
  • 2'Update AI' button inside the Sheet. A custom Apps Script menu button triggers the full sync โ€” no technical knowledge required, no GHL login needed.
  • 3Google Apps Script reads and formats the data. The script parses the Sheet, structures it for GHL's API format, and fires a webhook to Make.com.
  • 4Make.com routes to the correct knowledge base categories. Parallel PUT requests update both Order Status and FAQ sections simultaneously.
  • 5Both AI channels sync from the same push. Voice AI and web chat widget both read from the same GHL custom values โ€” one update, both current.
  • 6Status confirmation after every update. Staff see a clear success or error confirmation without needing to verify inside GHL.
System Architecture โ€” One-Click AI Knowledge Base Sync
๐Ÿ“‹
Staff update Google Sheet
Order status or FAQ data entered in the structured table
๐Ÿ–ฑ
Click "Update AI" button
Custom Apps Script menu โ€” no GHL login, no technical knowledge needed
{ }
Apps Script reads, formats, fires webhook
Parses Sheet rows โ†’ structures for GHL API โ†’ sends to Make.com
โš™
Make.com routes to GHL knowledge base
Parallel PUT requests โ†’ Order Status category + FAQ category
๐Ÿค–
Both AI channels updated simultaneously
Voice AI (inbound phone) + web chat widget โ€” same data, same moment
โœ…
Confirmation returned to staff
Clear success/error status โ€” no GHL verification required
04 โ€” How We Built It

Three Working Sessions to Production

๐Ÿ—ฃ

Discovery

Three working sessions with the KMN team to map the full order lifecycle: from production floor to staff desk to AI knowledge base to customer call. Identified every manual touchpoint and where information was being re-entered.

๐Ÿ”ฌ

Analysis

Confirmed the core inefficiency: staff were already maintaining an accurate Google Sheet. The problem was the second step โ€” manually transcribing that same data into GHL. The Sheet was the right source of truth; it just needed a direct connection.

๐Ÿ—บ

Process Mapping

Designed a flow where the Google Sheet becomes the single authoritative source โ€” one structured spreadsheet controlling both order status and FAQ data, feeding both AI channels simultaneously.

๐Ÿ”จ

Build

Wrote the Google Apps Script, configured the Make.com webhook routing workflow with parallel GHL API calls, and added the 'Update AI' button inside the Sheet. Error handling built throughout โ€” empty rows, formatting edge cases, and API response failures all handled gracefully.

โœ…

QA & Handoff

Pilot tested with live order data across both AI channels. Verified voice AI and web chat widget both reflected updated knowledge correctly after a single click. Confirmed staff could complete the full workflow without any training or documentation walkthrough.

05 โ€” Results

Before vs. After

Before
After
Staff manually updated the AI after every order status change โ€” one update per status, per order
One click from inside the Google Sheet pushes all current order data to both AI channels simultaneously
Information lag between order changes and what the AI told customers โ€” sometimes hours behind
AI updated in seconds after each sheet edit โ€” customers get accurate status on first call
Voice AI and web chat ran off different data โ€” updating one did not update the other
Both AI channels read from the same GHL custom values โ€” one push syncs both instantly
Growing order volume made manual updates unsustainable โ€” the bottleneck worsened over time
System scales with order volume at no additional staff cost โ€” the script handles any number of rows
No visibility into what the AI was actually saying โ€” staff couldn't confirm accuracy without logging in
Staff control the source of truth directly in the Sheet and receive a confirmation on every update

The Takeaway

KMN eliminated the manual step that was holding their AI back. Staff now update the knowledge base as part of their normal order workflow โ€” no extra system, no extra time, no stale data. The AI became reliable because it became automatic. 49 calls handled, 54 actions triggered, 100% positive customer sentiment โ€” the AI running without manual intervention.

01 โ€” Context

01 โ€” Context

An AI Receptionist Only as Good as Its Last Manual Update

Kitchen Made New (KMN) is a kitchen fabrication and restoration company serving residential and commercial clients. As part of their customer experience strategy, KMN integrated an AI receptionist into GoHighLevel โ€” giving customers real-time order tracking, service updates, and FAQ answers through both voice and web chat.

The AI was central to how KMN handled inbound calls โ€” particularly from manufacturing clients whose end-customers called multiple times per day asking where their orders stood. The system worked. But only as long as someone kept manually feeding it accurate data.

02 โ€” The Problem

02 โ€” The Problem

Manual Updates Were Becoming a Bottleneck

Every time an order changed status, a staff member had to stop what they were doing, open GoHighLevel's knowledge base, find the right entry, type the updated information, and save it. With a growing volume of active orders across both residential and manufacturing clients, this manual step was becoming unsustainable โ€” and the AI was starting to give customers outdated answers.

  • One manual update per order status change. Every time an order moved through production, a staff member had to interrupt their workflow to update the AI separately.

  • Outdated information reaching customers. Missed or delayed updates caused the AI to give callers incorrect order status โ€” eroding trust on high-volume inbound days.

  • Unsustainable at scale. As order volume grew, the number of manual knowledge base updates per day grew with it โ€” with no ceiling in sight.

  • Voice AI and web chat were not synced. Updating one channel did not update the other โ€” customers could get different answers depending on how they contacted KMN.

  • No confirmation of accuracy. Staff had no way to verify what the AI was currently saying without logging into GHL and manually checking โ€” adding even more overhead.

The AI was only as accurate as the last person who remembered to update it. With dozens of active orders at any time, that gap was widening โ€” and customers were starting to notice.

03 โ€” The Solution

03 โ€” The Solution

Google Sheet โ†’ One Button โ†’ Both AI Channels Updated in Seconds

We designed a centralized Google Sheet connected to a custom Google Apps Script. Staff input order changes in one structured table โ€” the same place they were already working. With a single button click, the script reads the Sheet, formats the data, routes it through Make.com, and pushes it directly to GoHighLevel's AI knowledge base via the GHL API. Both the voice AI and the web chat widget update simultaneously from the same source.

1

Structured Google Sheet as single source of truth. All order status and FAQ data lives in one table โ€” the same one staff were already maintaining.

2

'Update AI' button inside the Sheet. A custom Apps Script menu button triggers the full sync โ€” no technical knowledge required, no GHL login needed.

3

Google Apps Script reads and formats the data. The script parses the Sheet, structures it for GHL's API format, and fires a webhook to Make.com.

4

Make.com routes to the correct knowledge base categories. Parallel PUT requests update both Order Status and FAQ sections simultaneously.

5

Both AI channels sync from the same push. Voice AI and web chat widget both read from the same GHL custom values โ€” one update, both current.

6

Status confirmation after every update. Staff see a clear success or error confirmation without needing to verify inside GHL.

System Architecture โ€” One-Click AI Knowledge Base Sync

๐Ÿ“‹

๐Ÿ“‹

Staff update Google Sheet

Order status or FAQ data entered in the structured table

๐Ÿ–ฑ

๐Ÿ–ฑ

Click "Update AI" button

Custom Apps Script menu โ€” no GHL login, no technical knowledge needed

{ }

{ }

Apps Script reads, formats, fires webhook

Parses Sheet rows โ†’ structures for GHL API โ†’ sends to Make.com

โš™

โš™

Make.com routes to GHL knowledge base

Parallel PUT requests โ†’ Order Status category + FAQ category

๐Ÿค–

๐Ÿค–

Both AI channels updated simultaneously

Voice AI (inbound phone) + web chat widget โ€” same data, same moment

โœ…

โœ…

Confirmation returned to staff

Clear success/error status โ€” no GHL verification required

04 โ€” How We Built It

Three Working Sessions to Production

๐Ÿ—ฃ

๐Ÿ—ฃ

Discovery

Three working sessions with the KMN team to map the full order lifecycle: from production floor to staff desk to AI knowledge base to customer call. Identified every manual touchpoint and where information was being re-entered.

๐Ÿ”ฌ

๐Ÿ”ฌ

Analysis

Confirmed the core inefficiency: staff were already maintaining an accurate Google Sheet. The problem was the second step โ€” manually transcribing that same data into GHL. The Sheet was the right source of truth; it just needed a direct connection.

๐Ÿ—บ

๐Ÿ—บ

Process Mapping

Designed a flow where the Google Sheet becomes the single authoritative source โ€” one structured spreadsheet controlling both order status and FAQ data, feeding both AI channels simultaneously.

๐Ÿ”จ

๐Ÿ”จ

Build

Wrote the Google Apps Script, configured the Make.com webhook routing workflow with parallel GHL API calls, and added the 'Update AI' button inside the Sheet. Error handling built throughout โ€” empty rows, formatting edge cases, and API response failures all handled gracefully.

โœ…

โœ…

QA & Handoff

Pilot tested with live order data across both AI channels. Verified voice AI and web chat widget both reflected updated knowledge correctly after a single click. Confirmed staff could complete the full workflow without any training or documentation walkthrough.

05 โ€” Results

Before vs. After

Before

After

Before

  • Staff manually updated the AI after every order status change โ€” one update per status, per order

  • Information lag between order changes and what the AI told customers โ€” sometimes hours behind

  • Voice AI and web chat ran off different data โ€” updating one did not update the other

  • Growing order volume made manual updates unsustainable โ€” the bottleneck worsened over time

  • No visibility into what the AI was actually saying โ€” staff couldn't confirm accuracy without logging in

After

  • Staff manually updated the AI after every order status change โ€” one update per status, per order

  • One click from inside the Google Sheet pushes all current order data to both AI channels simultaneously

  • One click from inside the Google Sheet pushes all current order data to both AI channels simultaneously

  • AI updated in seconds after each sheet edit โ€” customers get accurate status on first call

  • Both AI channels read from the same GHL custom values โ€” one push syncs both instantly

  • System scales with order volume at no additional staff cost โ€” the script handles any number of rows

  • Staff control the source of truth directly in the Sheet and receive a confirmation on every update

  • Information lag between order changes and what the AI told customers โ€” sometimes hours behind

  • AI updated in seconds after each sheet edit โ€” customers get accurate status on first call

  • Voice AI and web chat ran off different data โ€” updating one did not update the other

  • Both AI channels read from the same GHL custom values โ€” one push syncs both instantly

  • Growing order volume made manual updates unsustainable โ€” the bottleneck worsened over time

  • System scales with order volume at no additional staff cost โ€” the script handles any number of rows

  • No visibility into what the AI was actually saying โ€” staff couldn't confirm accuracy without logging in

  • Staff control the source of truth directly in the Sheet and receive a confirmation on every update

The Takeaway

KMN eliminated the manual step that was holding their AI back. Staff now update the knowledge base as part of their normal order workflow โ€” no extra system, no extra time, no stale data. The AI became reliable because it became automatic. 49 calls handled, 54 actions triggered, 100% positive customer sentiment โ€” the AI running without manual intervention.

Project Snapshot

Company

Kitchen Made New

AI Calls Handled

49

Actions Triggered

54

Customer Sentiment

100% Positive

Manual Steps

Zero

Live Since

August 2025

Tools Used

GoHighLevel

Google Apps Script

Make.com

GHL API

Google Sheets

Is Your AI Running on Stale Data?

If your team is manually updating tools that should be talking to each other, you're paying someone to do a job a script can handle in seconds.

More Case Studies

Invoice Automation

One Person. No Backup. Surgery Scheduled.

26-step Zapier pipeline replacing 100% manual invoice entry for an automotive dealership network.

CRM Integration

20 Shops. Every Estimate. Still Dragged by Hand.

Bidirectional Zapier integration connecting MobileTech Rx and GoHighLevel for 20+ PDR shop locations.

Onboarding Automation

From 5โ€“7 Days to Minutes.

Fully automated client onboarding for a business coaching company โ€” payment to active membership in under a minute.

Your Tools Should Talk to Each Other

Close the Manual Gap

Book a Systems Audit and we'll map exactly where your team is manually re-entering data that a script could handle in seconds.

ยฉ 2026 Nexus Level Advisor. All rights reserved.

Automation ยท AI ยท CRM ยท Operation Systems