My Cloud Crew / CRM Build / Audit
AuditBuild PlanSales SOPResults

CRM Audit  /  October 1, 2026

What is inside the My Cloud Crew CRM

A full read of the account: how leads come in, which automations are live, how the pipelines are used, and what needs fixing before we send lead quality back to Facebook.

01 / Summary

The short version
  • Leads are arriving and the main automations work. Facebook and website leads are captured, tagged, emailed and posted to Slack.
  • Nobody moves leads through the pipelines. Only 8 of 1,456 MCC Pipeline cards were ever moved by hand, the last one in August 2024. Lead quality is tracked with tags instead.
  • Facebook only hears about the form fill. The Meta Conversions API sends one event when a lead arrives and nothing after that, so Facebook cannot tell a real prospect from spam.
  • A booked call is not proof of quality. Recent bookings include vendor sales pitches, so a booking alone should not be reported to Facebook as a good lead.
  • A few automations overlap. One website form starts two workflows, and 14 email campaigns share the same trigger.

02 / Account at a Glance

What the account holds
Contacts10,074
Workflows6240 live, 22 draft
Pipelines6
Tags464
Forms / Surveys24 / 11
Funnels15
Calendars118 active
Custom fields103

03 / How Leads Come In

Entry points and what happens next
SourceHandled byWhat happensStatus
Facebook lead form "Mycloud Form 2026"Facebook Lead Form Submitted-Aug-2026Card in PPC pipeline, tag, Meta event, team email, customer thank-you email, Slack postWorking
Facebook lead form "2024-02 Business Lead Capture"Same workflowSame as aboveWorking
Facebook lead form "2025 Firerock Campaign"Same workflow, then the Hot Lead workflowCard in PPC pipeline, tag "new_lead-hot", thank-you email, Slack post, SMS to the on-shift repWorking
Website Enquiry Form V2Facebook workflow and 2024 Landing Page InquiryBoth workflows run, so each enquiry gets two PPC cardsOverlap
Discovery call booking (website, meeting link, claim offer)3 "Customer Booked Appointment" workflowsCard in MCC Pipeline at "Booking Requested", confirmation and remindersWorking
Google Ads leads (tag "google ads")TAG: Google Ad Campaign PipelineCard in PPC pipeline, welcome email, Slack postWorking
Landing pages (SEO, marketing, VA download)2024 landing page workflowsCard in PPC or email pipeline, email, Slack postWorking
LinkedIn lead formWebsite & LinkedIn Form SubmittedCard in MCC Pipeline at "New Lead"Live

Changed with this build

This table shows the account as audited. Since October 1, the three Facebook forms create their card in MCC Pipeline instead of the PPC pipeline. See the Build Plan.

Fixed on September 23

Leads from the "Mycloud Form 2026" and "2024-02 Business Lead Capture" Facebook forms were not getting the customer thank-you email or the Slack post. Both are now added and were tested live with Meta's lead testing tool: the email was delivered and the Slack step ran.

04 / Pipelines

How the pipelines are actually used
PipelineCardsFed byManual stage moves
MCC Pipeline1,456Call bookings, LinkedIn form, older Facebook forms8 ever, last in Aug 2024
PPC Ads Campaign412Facebook, Google Ads, website formsNone. All moves are automated
MCC Email Campaign6,000+Industry email campaignsAutomated
Cold Call Pipeline6,000+Cold call listAutomated
Soft Close Pipeline12Soft close formIts workflows are drafts
Test1NoneUnused

MCC Pipeline stages today

StageCardsHow cards get there
New Lead1,272LinkedIn form and older lead forms
Email Opened22Older email automation
Called / Booking Link Clicked0Not used
Booking Requested61Automatic when a discovery call is booked (26 in 2026)
Booking Completed2Manual, last used 2024
Booking No Show / Soft Close / Lost5Manual, last used 2024
Bad Lead94Manual, last used Feb 2024

What this means

The team rates leads with tags ("bad lead", "booking confirmed", "spam likely") and not with pipeline stages. Facebook leads also land in the PPC pipeline, while their booked calls land in MCC Pipeline, so one lead can have up to three cards across two pipelines.

05 / Facebook Conversions API

What Facebook is told today
Lead fills a Facebook form→GHL sends one "lead" event to Meta→Nothing else is sent
ItemFinding
ConnectionConnected The Meta pixel and access token are set up and events send successfully
Events sentOnly at lead intake (4 Facebook branches send a lead-stage event, the website branch sends a standard Lead event)
Quality signalMissing No event is sent when a lead turns out to be real, books, or signs
Lead matchingReady Facebook leads store their Facebook Lead ID, which Meta uses to match later events

How Meta learns lead quality

Meta does not accept a "bad lead" penalty. You choose one good stage (for example, a qualified call) and send it back. Meta compares the leads that reach that stage with the ones that do not and shifts ad delivery toward the good ones. Meta's guidance: the stage should happen within 28 days of the lead and convert at between 1% and 40%.

06 / Team Notifications

Who hears about a new lead
ChannelWhereStatus
Slack#mcc-sales-leads, from 6 live workflows (Facebook, Hot Lead, Google Ads, landing pages)Live
Team emailFacebook branches email the sales team for each new leadLive
SMS to rep on shiftHot Lead workflow texts Laurence, Murali, Sameer or Von by time of dayAt risk SMS registration (A2P) was rejected in June

07 / Findings

What needs attention

1. No quality signal goes back to Facebook

Facebook optimizes for anyone who fills the form, including spam. This is the main gap the build fixes.

2. Pipeline stages are not being worked

Cards sit where automation drops them. Without a simple stage routine, there is nothing reliable to report to Facebook.

3. Facebook leads are split across two pipelines

The Facebook form creates the card in the PPC pipeline, and a booking creates a second card in MCC Pipeline. Reporting from one place is not possible today.

4. Website Enquiry Form V2 starts two workflows

Each enquiry gets two PPC cards and two sets of messages. One of the two workflows should stop listening to that form.

5. SMS registration (A2P) rejected

The carrier rejected the campaign on opt-in wording, and the sample messages still contain a placeholder company name. Text alerts and customer SMS may be blocked until it is resubmitted.

6. 14 email campaigns share one trigger

Fourteen industry email campaigns (hospitality, real estate, travel and others) all start on the same condition: an "insurance" tagged contact added to the email pipeline. If that happens, the contact would enter all 14 at once. The pipeline is quiet now, but the triggers should be corrected before it is used again.

7. Housekeeping

22 draft workflows, 3 unnamed empty workflows, duplicate tags (e-commerce / ecommerce, fin tech / fintech), and a Zoho Social connection on the Facebook page that fails because its admin was removed. None of these block the build.

08 / Recommendation

What we will build
  • Make MCC Pipeline the one pipeline for Facebook leads, from first contact to signed client.
  • Give the sales team a short stage routine so every lead is marked real, no-show, bad or won.
  • Send Facebook a quality event only when a real call happens or a client signs, and never for bad leads.

See the build plan →