Real client scenarioTotoong client scenario
The Messy Account HandoverAng Magulong Account Handover
This is the kind of message clients actually send. Nobody tells you what to build — working that out is the skill. Plan your answer first, then compare it with a suggested solution.
Ganitong klase ng message ang talagang pinapadala ng clients. Walang magsasabi sa'yo kung ano ang ibu-build — ang pag-alam niyan ang skill. Iplano muna ang sagot mo, tapos ikumpara sa suggested solution.
The client's message
"The last VA left. There are 200+ tags, nobody knows what half of them mean, and our smart lists are all broken. Can you clean it up?"
Ang message ng client
"Umalis na ang dating VA. Mahigit 200 ang tags, walang nakakaalam ng ibig sabihin ng kalahati, at sira lahat ng smart lists namin. Kaya mo bang linisin?"
Before you build, work out…Bago ka mag-build, alamin muna…
- Where do you start, before changing anything?
- How do you decide which tags to keep, merge or delete?
- How do you avoid breaking live workflows?
- What naming convention will you introduce?
- How will you document what you did?
- What must you check before deleting anything?
- Saan ka magsisimula, bago baguhin ang kahit ano?
- Paano mo pagdedesisyunan kung aling tags ang itatabi, pagsasamahin o ide-delete?
- Paano mo maiiwasang masira ang live workflows?
- Anong naming convention ang ipapakilala mo?
- Paano mo ido-document ang ginawa mo?
- Ano ang dapat mong i-check bago mag-delete ng kahit ano?
Your planAng plano mo
Write it here or on paper. Notes typed here stay in this browser only.Isulat dito o sa papel. Sa browser na 'to lang naka-save ang notes na tina-type mo dito.
Have you written your plan? The solution is much more useful after you've tried. There's no right answer you have to match.
Naisulat mo na ba ang plano mo? Mas kapaki-pakinabang ang solution pagkatapos mong sumubok. Walang iisang tamang sagot na kailangan mong gayahin.
Suggested solution
Awaiting hands-on verification. The concepts here are sound, but the click-by-click steps have not yet been re-walked in a live GoHighLevel sub-account. GoHighLevel changes often, so a menu name or screen may differ from what you see. Flagged rather than presented as verified.
What this scenario is really teachingAno talaga ang tinuturo ng scenario na 'to
This is the most common real first job a GHL VA is hired for. The skill is auditing safely: understand what depends on something before you change it, and leave a written record. Ito ang pinakakaraniwang totoong unang trabaho na pinag-ha-hire-an ng GHL VA. Ang skill ay ang ligtas na pag-audit: intindihin muna kung ano ang umaasa sa isang bagay bago ito baguhin, at mag-iwan ng nakasulat na record.
Clarifying questions worth askingMga clarifying question na sulit itanong
- Which workflows and automations are live and important to the business right now?
- Is anyone else working in the account while I clean up?
- Are there any tags your team uses by hand that I wouldn't see in a workflow?
- Aling workflows at automations ang live at mahalaga sa business ngayon?
- May iba pa bang nagtatrabaho sa account habang naglilinis ako?
- May tags ba na mano-manong ginagamit ng team n'yo na hindi ko makikita sa workflow?
Rule one: change nothing on day one
The danger in a clean-up isn’t leaving mess. It’s deleting a tag that a live workflow depends on, and silently breaking the client’s lead follow-up. Audit first, change later.
A suggested approach
1. Inventory. Export or list every tag. For each one, record: how many contacts have it, and whether any workflow triggers on it, filters on it, adds it or removes it. Check smart lists too.
2. Sort into four groups:
| Group | Meaning | Action |
|---|---|---|
| Keep | Used by a live workflow or the team, clearly named | Rename later to fit the convention |
| Merge | Duplicates (Website Lead, website-lead, lead-website) | Pick one, move contacts, update workflows, then retire the others |
| Convert | Really a field (budget-10k, budget-20k) | Create a proper field, migrate, update workflows |
| Retire | Unused, nothing depends on it | Delete — only after confirming |
3. Agree a naming convention with the client (Lesson 6) and write it down.
4. Change in small batches. After each batch, test the affected workflows.
5. Fix the smart lists last. Most “broken” lists are faithfully filtering inconsistent tags. Once the tags are merged, update each list’s filters and check the counts look right.
6. Document everything in a handover note: what changed, why, the new convention, and anything you weren’t sure about.
Before deleting any tag, check
- No workflow triggers on it, filters on it, or adds it
- No smart list filters on it
- The team doesn’t use it by hand (ask!)
- You’ve recorded which contacts had it, in case you need to restore it
What I’d tell the client
“I’ll start with an audit so nothing breaks — I won’t delete anything in the first pass. You’ll get a list of every tag sorted into keep, merge, convert and retire, plus a naming guide. Once you approve it, I’ll clean up in small batches and test your workflows after each one.”
That last sentence is why this kind of VA gets rehired.
Rule one: walang babaguhin sa unang araw
Ang panganib sa clean-up ay hindi ang pag-iwan ng gulo. Ito ay ang pag-delete ng tag na inaasahan ng live workflow, at tahimik na pagsira sa lead follow-up ng client. Mag-audit muna, saka magbago.
Suggested na approach
1. Inventory. I-export o ilista ang bawat tag. Para sa bawat isa, itala: ilang contacts ang may hawak nito, at kung may workflow na nagti-trigger, nagfi-filter, nagdadagdag o nagtatanggal nito. I-check din ang smart lists.
2. Hatiin sa apat na grupo:
| Grupo | Ibig sabihin | Gagawin |
|---|---|---|
| Keep | Ginagamit ng live workflow o ng team, malinaw ang pangalan | I-rename mamaya para tumugma sa convention |
| Merge | Duplicates (Website Lead, website-lead, lead-website) | Pumili ng isa, ilipat ang contacts, i-update ang workflows, tapos i-retire ang iba |
| Convert | Field talaga (budget-10k, budget-20k) | Gumawa ng tamang field, mag-migrate, i-update ang workflows |
| Retire | Hindi ginagamit, walang umaasa dito | I-delete — pagkatapos lang kumpirmahin |
3. Magkasundo sa naming convention kasama ang client (Lesson 6) at isulat ito.
4. Magbago nang paunti-unti. Pagkatapos ng bawat batch, i-test ang mga apektadong workflow.
5. Huling ayusin ang smart lists. Karamihan ng “sirang” lists ay tapat lang na nagfi-filter ng inconsistent na tags. Kapag napagsama na ang tags, i-update ang filters ng bawat list at i-check kung tama ang bilang.
6. I-document ang lahat sa handover note: ano ang nagbago, bakit, ang bagong convention, at anumang hindi ka sigurado.
Bago mag-delete ng kahit anong tag, i-check
- Walang workflow na nagti-trigger, nagfi-filter, o nagdadagdag nito
- Walang smart list na nagfi-filter dito
- Hindi ito mano-manong ginagamit ng team (magtanong!)
- Naitala mo kung aling contacts ang may hawak nito, kung sakaling kailangan mo itong ibalik
Ano ang sasabihin ko sa client
“Magsisimula ako sa audit para walang masira — wala akong ide-delete sa unang pasada. Makakatanggap ka ng listahan ng bawat tag na nakahati sa keep, merge, convert at retire, plus naming guide. Kapag inaprubahan mo, maglilinis ako nang paunti-unti at ite-test ko ang workflows mo pagkatapos ng bawat batch.”
‘Yang huling pangungusap ang dahilan kung bakit nire-rehire ang ganitong klase ng VA.