Every program runs in its own lane. They never cross.
REKA, AIBE and MDP all live inside one GoHighLevel account. The same person can be in two of them at once and stay completely separate, because each program uses its own labels, its own form, its own pipeline and its own pixel. Tap any step to see what happens. Pick a person below to watch one human flow through two programs without the wires touching.
Focus
Watch a person
📏
The 7 rules
The law for every EP funnel. Follow these and the lanes can never cross.
🔌
The one place they could collide
Two tools are shared by all programs. They must know who they are working for.
Shared plumbing ⚠ route by program
Every workflow above is locked to its own program. But two back-end tools serve all programs at once. If they ever assume "everyone is REKA," that is the single way a sale or a group-join lands in the wrong program. The rule: each must decide which program a person belongs to, then write that program's label.
💳 Payment robot
A sale comes in, it tags the buyer. Must route each payment link to the right label: reka-purchase vs aibe_purchase vs mdp_purchase. Route by which link was paid, not by price.
reka-purchaseaibe_purchasemdp_purchase
🔁 Group / Zoom checker
Matches the WhatsApp group export + Zoom attendees back to contacts. Must run per program so it sets aibe_wa_joined, not REKA's joined_whatsapp_group.
joined_whatsapp_groupaibe_wa_joinedmdp_wa_joined
REKAAIBEMDP (template)
Verified live 11 Jun 2026. One GHL account: Fastcom PLT. Tap a step for detail.