I don't have an answer to your question but want to say and ask; Hubspot is cool, I'm just wondering what features you like about it that might be incorporated in Skool? I know you're wanting to transfer the phone number to the CRM but once there what will you do with it?

@Jacob Murphy So if the phone number was a URI you could click from here and then you could use your favorite VoIP app. Or just copy and paste the number. voice.google.com is nice if you don't have one already.

This is great. Now could you send a ICS file for the event to my email address if I desire that to happen?

@Sam Ovens I don't know, I think the event view would be good on my desktop view. Maybe add a option variable for which view to see?

One way to go about this would be to have a controlled posting category where only invited members could use/see that category. I fee that this has been discussed before ... doing a search I see that it has.

@Hanneke Verhoef That's not an easy answer. But just so you understand here is an answer generated from ChatGPT. As a director of software engineering, the duration of the beta testing phase for a project depends on various factors, such as the complexity of the project, the size of the user base, the amount of feedback needed, and the resources available for addressing the issues discovered during testing. Typically, beta testing can last anywhere from a few weeks to a few months. Here's a suggested plan to determine the appropriate duration: 1. Assess the project complexity: Analyze the features, functionality, and dependencies of your software to estimate the potential number of issues that could arise during testing. 2. Define goals and objectives: Set clear goals and objectives for the beta testing phase, including the types of issues you want to uncover and the level of user engagement needed to gather sufficient feedback. 3. Estimate user base size: Determine the size of the user base you'll need for beta testing to get a representative sample of feedback. Larger user bases may require longer testing periods to manage and analyze feedback effectively. 4. Allocate resources: Evaluate the resources available for addressing issues discovered during beta testing. If your team is smaller or has limited bandwidth, you may need a longer testing period to ensure all issues are resolved. 5. Monitor progress and adjust: Regularly review the progress of the beta testing phase, and be prepared to adjust the duration as needed based on feedback and issue resolution. In general, it's crucial to strike a balance between thorough testing and timely release. While there's no one-size-fits-all answer, planning for a beta testing phase of 4 to 12 weeks is a reasonable starting point, with adjustments made based on the factors mentioned above.

@Jay Israel A subscription billing model with payments accepted via Skool.

@Pam Yang, she-her Maybe more of an action for the member to confirm joining the call similar to Calendly? The Skool calendar entry would allow for members of a classroom to be notified via email when a Skool calendar entry is made and their email program could add it to their calendar? @Sam Ovens What do you think?

@Pam Yang, she-her Don't you have (I don't know, I don't own a community) an option to group those members in paid versus free, etc? When you create the calendar event can you specify which group that can see it?