Multi-Tenant AI "Digital Chief of Staff" (Make.com + Claude + WhatsApp)

@dvcontact

Hello Sir, Would you like to see a demo of our Multi-Tenant AI 'Digital Chief of Staff' solution before making any commitments? Our innovative AI agent seamlessly manages client emails, triages urgent messages, and delivers personalized daily briefings via WhatsApp, ensuring your clients experience enhanced productivity and satisfaction. Let's discuss this further and I can walk you through a detailed plan and demo tailored to your unique needs. Regards, Smith

@jonhw5

Hello, thanks for posting this project. I am confident in my ability to design and develop robust Gaming APIs with complex business logic using PHP Laravel. I have over 5 years of experience in Laravel development and a deep understanding of MySQL for optimized performance. I am excited about the opportunity to tackle the challenges of this gaming API project. How soon are you looking to get started on this project? What is your preferred data retention policy and security compliance level for multi-tenant data in Airtable and Gmail integrations? Looking forward to hearing from you. Best regards,

@krisk63

Hi there, I'm Kristopher Kramer from McKinney, Texas. I’ve worked on similar projects before, and as a senior full-stack and AI engineer, I have the proven experience needed to deliver this successfully, so I have strong experience in Automation, Prompt Engineering, PHP, Software Architecture, C# Programming, AI Chatbot, Java, AI Development, Airtable and Make.com. I’m available to start right away and happy to discuss the project details anytime. Looking forward to speaking with you soon. Best regards, Kristopher Kramer

@amadorjay

Hello, The primary engineering challenges include ensuring seamless data synchronization across multiple client Gmail accounts while maintaining scalability for a growing user base. Managing the complexity of multi-tenant architecture will be crucial, particularly in securing each client’s data and ensuring isolation. Additionally, the integration with various APIs must handle real-time events without compromising performance. What specific security measures are you considering for the OAuth2 integration to manage multiple client accounts? Is there an existing structure for handling error notifications, especially for API connection expirations? Furthermore, how will the data flow be managed between Airtable and the automation engine to ensure consistency in client profiles and message logs? Looking forward to discussing the intricacies of this architecture.

@tarast7

Hello, How are you? I have checked your job description and I’m confident I can complete exactly what you need. I have extensive experience with building scalable AI assistants using AI content, relevant technologies, and programming skills. So, I believe this job is an ideal match with my skill set and experience. Let's work together to bring this innovative project to life. Please send me a message so that we can discuss more. Thanks Taras

@tanithk

Hey — saw your post about building a multi-tenant “Digital Chief of Staff” using Make + Claude + WhatsApp. The tricky part with this kind of setup is keeping each client’s workflows, data, and context fully separated while still being easy to manage from your side. Quick question before I suggest an approach: Do you already have a tenant model in mind (per WhatsApp number, per workspace, per Make scenario), or is that still open? I’ve built automation stacks with Make + Claude + WhatsApp before, including multi-client setups where routing, context, and permissions were the main challenges. If you can share your current diagrams, Make scenarios, or any spec you have, I’ll review it and come back with a concrete way to structure the multi-tenant side.

@jeremiasg17

Hello! I’ve built a similar AI assistant that successfully managed multiple client inboxes, improving email response times by over 40% through automation. I can share the implementation details in our chat if you're interested. For your project, I'd approach it by setting up a robust multi-tenant architecture in Airtable, ensuring seamless integration with the Gmail API and the WhatsApp Business API. I’m curious—how do you envision managing the different writing styles for each client in practice? I can provide a small milestone task to demonstrate my capabilities or we could jump on a quick call to discuss your needs further. If you’re open, I can share the similar build and we can see if it fits.

@skolarai

I see you're handling multiple client voice profiles in Airtable—most people skip that and end up with generic responses. I've built similar multi-tenant agents using Claude API with Make workflows, storing writing styles and context in structured databases to maintain brand voice at scale. The tricky part is usually email triage logic and rate-limiting across clients without losing context. How are you planning to handle conflicting priorities when multiple clients have urgent emails in the same morning window.