Has anyone built a reliable workflow for recording mobile phone calls and pushing summaries into GHL / Wayhub or a similar CRM? Use case: Business owner takes discovery calls on their existing mobile number. They do not want to change numbers. This is the reason we're not using GHL native features currently. Ideal flow: Mobile call recorded→ recording saved to cloud→ transcription and AI summary→ structured internal note added to GHL contact/opportunity→ optional follow-up task created I am looking for practical recommendations on: - iPhone or Android call recording apps that actually work - apps that can save recordings automatically to Google Drive, Dropbox or similar - whether native iPhone / Android call recording can be automated into a cloud folder - best transcription layer, for example OpenAI, AssemblyAI, Deepgram or similar - Make / Zapier / n8n workflows into GHL - any consent, privacy or reliability traps to watch for The big constraint is keeping the client’s existing mobile number. Has anyone solved this cleanly? Many thanks!

How do you have the client host the code but still work on it yourself. I heard you can use GitHub in some way. I have an idea of how it works with n8n but I would like to know how it works if you use Claude code through an IDE like VS code

I am trying to understand how people are actually deploying Claude Code-built automations for clients. My background is mostly Make.com, so I am used to automations being visual, easy to explain, and fairly easy for a client to understand at a high level. With Claude Code, Modal, and Trigger.dev, I can see the appeal. You can build something more flexible, probably faster in some cases, and less constrained by the limits of visual workflow tools. The bit I am still working through is the client side of it. I am especially interested in how this lands with small businesses and non-technical founders. My guess is that most clients mostly care about whether the automation works, is reliable, is documented, and has someone supporting it. But I can also see cases where Make.com or n8n might still be the better choice, even if the build is slower or less elegant. A client may want something visual. They may want internal ownership. T For people doing this in the real world, where are you drawing the line? - When would you use Claude Code, Modal, and Trigger.dev? - And when would you still choose Make.com or n8n because of the client, not because of the technology?

how was your experience doing so? Everyone is talking about claude code and not much on Codex and n8n/ automations... anyone tried out with codex? the usage is much better there... but havent had the time to explore and make the change

Hey guys, I have a genuine question for someone, whos been building and selling AI operating systems build on Claude code. Its been a thing for me and Iam going all into it, but one thing that I just cant figure out is what you actually sells, because I have of course watched all these videos from Liam, Jordan, etc. and everyone is explaining how it works and stuff like that. But tell me, do you just setup claude code in the terminal/vs code extension for the client or do you build a frontend, where non technical clients can manage all of their work, agents, etc. I understand the concept as a whole but I cant get these details off mind, because I think you cant build a frontend/dashboard for claude code, its just not possible and you would have to use claude API which of course doesnt have all the functions as claude code and isnt as powerful. So my question is how do you deal with this and what do you actually sell? Thanks