Phone calls were the entry point
Social media could influence demand, but the actual lead arrived by phone and Carmil personally handled the call or text response.
Implementation Case Study
Connecting Shopmonkey and GoHighLevel for Carmil Car Audio
Carmil Car Audio already had Shopmonkey handling appointments, jobs, estimates, invoices, payments, customer history, and reporting. The missing layer was structured lead capture and follow-up after an estimate or completed job. Enciu Consulting connected Shopmonkey with HighLevel and built the CRM automation around the system that was already working.
Relationship disclosure: Carmil Car Audio is owned by Carmil Enciu, Clay Enciu’s father. This was the implementation that led Clay to start Enciu Consulting. Carmil gave written permission for the business name, implementation details, screenshots, and approved metrics to be used in this case study.
The Problem
The operational system worked. The follow-up layer did not exist.
Before HighLevel, new leads arrived by phone. Shopmonkey held the customer record and handled the active job, but there was no dedicated system for continuing estimate follow-up, requesting reviews consistently, or retaining customers after the invoice was paid.
No structured reminder sequence
If a lead did not respond or did not move forward, there was no dedicated CRM sequence continuing the conversation over time.
Requests were manual or QR-code based
The shop had a Google review QR code, but there was no repeatable review-request workflow tied to the customer process.
Past customers mostly relied on word of mouth
Customer history existed in Shopmonkey, but there was no structured post-sale or long-term follow-up using that relationship.
Shopmonkey already handled them
Appointments, technician assignment, estimates, invoices, payments, and customer history were already part of the Shopmonkey workflow.
The process ended after the invoice
Phone call → technician appointment → install → invoice → customer leaves the active workflow.
The System
HighLevel was integrated around Shopmonkey instead of replacing it
The implementation kept the POS and operational workflow intact. Shopmonkey webhooks and API data feed customer events into HighLevel, where the lead and follow-up automations take over.
1
Website or shop eventA website form or Shopmonkey event creates the starting signal.2
Inbound webhookHighLevel receives the event through the configured workflow.3
Contact dataShopmonkey customer data is retrieved or website fields are captured.4
CRM recordHighLevel creates or updates the contact, opportunity, and tags.5
AutomationThe relevant estimate, review, post-sale, or nurture workflow runs.6
Operations stay putScheduling, jobs, invoices, payments, and reporting remain in Shopmonkey.Operational source of truth
Appointments, technician calendars, job status, estimates, invoices, payments, customer history, and business reporting remain inside Shopmonkey.
CRM and automation layer
Website leads, opportunity stages, follow-up, review requests, retention, long-term nurture, communication workflows, and CRM tags are handled in HighLevel.
Webhooks + Shopmonkey API
Inbound workflows pull Shopmonkey customer information into HighLevel so existing POS activity can drive CRM records and follow-up without duplicate manual entry.
Implementation
Five workflow areas extended the customer journey beyond the active job
The implementation was built around real stages and events visible in the live account. The screenshots below are from the documented Carmil Car Audio build.
New web inquiries enter HighLevel directly
The website workflow creates the contact, adds the New Lead tag, enables communication channels, creates or updates the opportunity, notifies the business, and sends the initial email.
A 42-day email and SMS sequence
Estimate Sent can trigger follow-up at 2, 7, 14, 21, 28, and 42 days. Unresolved opportunities are then moved into long-term nurture.
SMS followed by email
The review-request workflow waits, sends an SMS, waits another 60 minutes, then sends an email so the process no longer depends only on a physical QR code.
Follow-up extends to one year
Post Sale Follow Up calls the review workflow and continues communication at 12 hours, 7 days, 30 days, 90 days, 6 months, 9 months, and one year.
Monthly email path through Month 12
Leads moved into LTN receive a lower-frequency monthly nurture sequence before the opportunity is closed out at the end of the configured path.
No HighLevel calendar or replacement reporting
Shopmonkey calendars and reporting were retained. The implementation focused HighLevel on the areas where the existing stack had the clearest follow-up gap.
Implementation Evidence
Screenshots from the documented build
These images show the website form and workflow structure used for this implementation. Customer-identifying pipeline screenshots are intentionally excluded from the public case study.
Documented Activity
The strongest results are adoption and process coverage, not unsupported financial claims
Outcome reporting was limited, so this page is intentionally labeled an implementation case study. The figures below are workflow activity that could be tied to a named source and date or to cumulative enrollment counts visible in HighLevel.
~40
website-lead workflow enrollments from July 20 through August 18, 2026
HighLevel: 102. New Lead - Website
395
total website-lead workflow enrollments visible at documentation time
Cumulative activity, not unique incremental revenue
178
total Estimate Follow-Up & Conversion enrollments
Shows use of the automated estimate follow-up path
528
total Send Review Request workflow enrollments
Measures workflow activity, not reviews generated
548
total Post Sale Follow Up workflow enrollments
Shows customers entering the retention workflow
12
total long-term nurture workflow enrollments
Cumulative LTN activity visible in HighLevel
Owner observation
The practical change was having a structured follow-up system around Shopmonkey
Carmil reported that customer tracking became easier and that the business gained a defined way to send follow-up messages and email campaigns. He also reported more phone calls after the system was introduced, but call-history data was not available to quantify or attribute that increase, so it is not presented here as a measured result.
Google review context: Carmil Car Audio had 393 Google reviews when this case study was documented on August 18, 2026. Exact recent review timestamps were not available, so this case study does not claim that the HighLevel automation generated those 393 reviews or a specific percentage increase.
Limitations
What this case study does not claim
The implementation is well documented, but the available outcome data is not detailed enough to support every kind of business-performance claim.
No revenue attribution
Shopmonkey revenue data was not collected for this case study, so no revenue lift or ROI percentage is attributed to HighLevel.
No conversion-rate claim
The available workflow records do not provide a reliable before-and-after conversion-rate comparison.
No quantified phone-call lift
The owner observed more phone calls, but comparable call records were not available for a measured causal claim.
No review-growth attribution
The current total review count is known, but exact 30-, 60-, and 90-day review history was not available.
No 60/90-day workflow breakdown
HighLevel did not provide reliable historical breakdowns for every workflow, so only the available 30-day website-lead figure is presented with a specific rolling window.
Family relationship disclosed
The business owner is Clay Enciu’s father. The relationship is stated openly so readers can judge the implementation evidence with full context.
The Takeaway
Use HighLevel where it improves the process. Keep the systems that already work.
This build was not about replacing every tool. Shopmonkey stayed responsible for the shop’s core operations. HighLevel was connected where it could add a structured CRM layer for website leads, estimate follow-up, review requests, retention, and long-term nurture.