No Transfer Responses


V1


Subject: Re: Sub-Account Transfer Request
Hi [Name],
 
Thank you for your kind message and the warm words — we’re grateful for the time you’ve spent inside the OS ecosystem, and it’s been a privilege to support you and your clients.
 
That said, we want to clarify our Account Transfer Policy, as this is a core protection of the infrastructure you’ve been building on, as outlined in our Terms Of Service.
 
“Sub-accounts under the OS platform are non-transferable and cannot be moved, cloned, or exported to other platforms or agencies — including other GoHighLevel (GHL) environments.”
 
This policy exists to protect:
  • The stability of our proprietary automations and systems
  • The attribution and MRR rewards tied to your OS account
  • The licensed assets and intellectual property exclusive to OS
  • The support experience for your clients, which can only be maintained inside OS
 
We understand your move and wish you the absolute best in your new chapter — but we’re unable to assist with transferring accounts out of the OS ecosystem.
 
We appreciate your transparency and the thoughtful way you’ve approached this. If you’d like to explore how to continue supporting clients within OS, or if you have questions about this policy, we’re here to help — just reach out.
 
Warm regards,
The OS Team
 

V2

Hi [Name],
 
Thank you for your kind message and the warm words — we’re grateful for the time you’ve spent inside the OS ecosystem, and it’s been a privilege to support you and your clients.
 
That said, we want to be upfront and clear about something important: our Account Transfer Policy.
 
As outlined in our Terms of Service, sub-accounts within OS are non-transferable. They can’t be moved, cloned, or exported to other platforms or agencies — including GoHighLevel environments outside OS.
 
This isn’t just a policy. It’s a core part of how we protect:
  • The integrity of our automation and system infrastructure
  • The licensed tools and intellectual property exclusive to OS
  • Your MRR tracking and partner rewards
  • And most importantly, the support experience your clients depend on
 
We built OS for long-term scalability, not short-term hacks — and transfers simply introduce risk we can’t support.
 
That said, you’ve got options:
  1. You can continue managing your clients right inside OS — no disruption, project board plugins, tech support, free imports, new premium templates, mini courses, custom GPTs, Themes, AI Plugins.
  1. You can sign up new users through your partner link and continue earning MRR directly without fulfillment.
  1. You can refer clients for DFY buildouts for additional commissions.
 
We appreciate your transparency and the thoughtful way you’ve approached this. If you’d like to explore how to continue supporting clients within OS, or if you have questions about this policy, we’re here to help — just reach out.
 
Respectfully,
The OS Team
 

V3

Subject: Regarding Your Account Transfer Request
Hi [Name],
 
First off — thank you. Your message came through with clarity, professionalism, and genuine care. We deeply appreciate the way you’ve shown up inside the OS ecosystem, and the commitment you’ve brought to your clients. It’s been a privilege to support your journey.
 
That said, we want to be upfront about something important: our Account Transfer Policy.
 
As detailed in our Terms of Service, OS sub-accounts are non-transferable. This means they can’t be moved, exported, or cloned to external platforms — including any GoHighLevel environments outside of OS.
 
This policy isn’t just about permissions — it protects:
  • The licensed tools and automations exclusive to OS
  • The integrity of our infrastructure and client experience
  • Your ongoing MRR tracking and partner rewards
  • And most critically, the reliability your clients count on
 
OS was built for sustainable, long-term growth — not quick fixes that create risk.
 
That said, you’ve got powerful paths forward:
  1. Keep growing right inside OS — full access to tech support, project boards, premium templates, free migrations, and AI tools.
  1. Sign up new users via your partner link — continue earning MRR without fulfillment duties.
  1. Refer DFY buildouts — earn additional commission from our in-house team.
 
Thanks again for your transparency and care. If you’d like to walk through options to scale inside OS — or have questions on this policy — we’re here to help.
 
With respect,
The OS Team

V4

 

Hi [Name],
Thanks for reaching out!
We appreciate the time you’ve spent building inside OS. That said, we want to be clear about our Account Transfer Policy, as outlined in our Terms of Service:
“Sub-accounts under the OS platform are non-transferable and cannot be moved, cloned, or exported to other platforms — including other HighLevel (GHL) environments.”
This policy exists to protect:
  • The integrity of OS-exclusive systems and automations
  • Attribution and MRR tied to your OS account
  • Licensed templates and proprietary IP unique to OS
  • The quality of client support that can only be maintained inside OS
For full details, you can review the policy here: teamos.ai/terms-of-service.
If you have questions or want to discuss next steps, feel free to reach out — we’re here to help.
Best,
The OS Team

Let me know if you’d like a shorter version for replies or a saved tag inside your inbox system.
 
 
Got it — here’s a concise update email to your user (Edwin, in this case) that explains how to use the custom values to send recording links automatically:

Subject: 📩 Update: How to Send Call Recording Links Automatically
Hey Edwin, understood. We are here to help.
Quick update — here's how to send follow-up emails with the call recording included:
 
Here is an overview video:
 
It covers how to find the call data sent through the webhook, and how to use the Inbound Webhook custom values to send the recording link, and populate contact fields.
 
Let us know if you have any questions.
 
Thank you,
The OS Team

Want me to generate this as a pre-built email template inside OS?