Use this chat stream to ask questions and chat about the call. Join the call 👇 https://us06web.zoom.us/j/75070492711?pwd=MboeQeNTj3huuCIG6Fb53ISFsmeoHg.1

Just a reminder that our special ManyChat live is happening tomorrow at 12 PM EST inside SmartContent AI Studio™. I’ll be joined by Heston Roberts, ManyChat and Chat Marketing expert, for a 1-hour conversation focused on how to use ManyChat more strategically in your business. We’ll cover: ✅ ManyChat’s new pricing restructure ✅ ManyChat integrations and what connects directly ✅ What to do when your platform doesn’t connect natively ✅ A live look at real ManyChat flows and templates ✅ Why simply sending someone a link can leave opportunities on the table ✅ Using follow-ups and reminders to keep conversations moving ✅ When to automate and when to personally jump into your DMs ✅ Using voice messages to make automation feel more human ✅ Live Q&A with Heston 📅 Friday, October 2 ⏰12:00 PM EST 📍Inside SmartContent AI Studio™ Whether you’re brand new to ManyChat or already using automations, this will be a great chance to see how to make your flows smarter, more personal, and more useful for actually moving conversations forward. Bring your questions. Let’s turn those comments into clients. See you tomorrow! Morgan

I spent weeks writing technical posts that completely tanked on mobile. I was spending 2 hours drafting in obsidian, testing the snippets, and checking the architecture On my desktop monitor, the drafts looked clean Then I opened one of the live posts on my iphone, it was unreadable. A 4-sentence paragraph had stretched into 14 lines of unbroken text. Readers on linkedin saw zero whitespace and scrolled away in 2 seconds The code was solid, but nobody reads a solid wall of text on a 6-inch glass screen. I only fixed the retention when I stopped guessing line breaks and started using a layout grid. Today, I run a 3-tool workflow that separates the writing from the mobile formatting: - Raw capture in obsidian: I dump my terminal outputs, error logs, and architecture notes into local markdown without worrying about line breaks - Fluff removal in claude: I run the draft through claude with a strict prompt to cut passive voice, strip filler words, and keep sentences under 15 words - Layout extraction: I grab the structural skeleton from posts in blotato and that held high engagement on linkedin. It strips away the author's words and leaves the whitespace grid: a 1-line tension opener, a 2-line problem frame, 3 short mechanism bullets, and a diagnostic closer I drop my cleaned notes straight into that empty grid and schedule the post The structure makes the post scannable in 45 seconds on an iphone, while the substance stays 100% technical. My drafting time dropped from 2 hours of manual reformatting down to 15 minutes of review. When you post technical work online, do you write freestyle into a blank box, or do you draft inside a fixed layout grid?

I spent 3 months testing two different extremes of content creation, and both failed The first extreme was 100% automated AI generation. I set up workflows to scrape trending topics, generate full drafts with claude, and auto-schedule them. The speed was incredible, but the content was unreadable slop. It sounded like an enthusiastic press release written by a committee Nobody read it, and it damaged my technical credibility The second extreme was 100% manual writing. I opened a blank document every morning and wrote every single word from scratch. The quality was high, but it took 2 hours per post. Within 3 weeks, I was completely burned out and stopped publishing. I only built a sustainable publishing rhythm when I adopted the 70/30 rule The rule separates the structural mechanics of writing from human editorial judgment: - 70% Structural physics (delegated to software): I let tools handle the uncreative heavy lifting. Software parses the raw transcript, extracts 3 clear takeaways, and maps them into a tested mobile reading frame. It removes the friction of staring at a blank screen - 30% Human editorial taste (reserved strictly for me): This is where the actual trust is built. I spend 5 minutes stripping out synthetic buzzwords, injecting my real dollar numbers, adding the mistake I made last Tuesday, and cutting every generic adjective Software gives you the skeleton. You supply the marrow When you try to let AI do 100% of the thinking, you get ignored. When you try to do 100% of the formatting manually, you quit. 70% structural leverage plus 30% human conviction is the only formula that survived my testing. When you draft content today, what takes up more of your stamina: building the initial outline, or polishing the final draft?

I recently discovered where Skool's top group owners are spending most of their time on social media. And if you're looking to grow your own Skool group 📝 you're gonna want to take notes. The attached image highlights 6 social platforms referenced most by Skool's Top 100 groups: ▪️Facebook ▪️Instagram ▪️LinkedIn ▪️TikTok ▪️Twitter/X ▪️YouTube So which platforms are Top Skoolers driving traffic from most? And what tools are they using to do it? One major factor I'm happy to share was more than half of those that use Instagram to drive traffic are doing it at a very high level with my favorite DM automation tool, Manychat. I shared this post to Skool's main group, Skoolers, and received 100+ comments and 200+ likes. But a question I wanted to ask there (but couldn't due to silly rules 😏) was this ... Do you use Manychat to drive traffic from Instagram to Skool, a podcast, maybe a YouTube channel or anywhere else? 💬 Share your response in the comments and let's discuss ...