We run a residential/commercial cleaning business and use Slack as our central communication hub. Each client has a private Slack channel. We want to connect these channels with Twilio SMS so clients (and sometimes multiple family members or co-managers) can text us, and our team can reply from Slack.
Here’s what we’ve already built:
A working Slack ↔ Twilio connection where client messages appear in their Slack channel and our replies go back to their phone.
A Google Sheet mapping phone numbers to Slack channel IDs (we’ve also experimented with running without Sheets and cloning scenarios per client).
Some filters and loop guards to prevent duplicate or “echo” messages.
Handling for multiple numbers (e.g. Mom + Dad) so both receive updates.
What we’re running into:
Media (photos and videos) handling: Twilio sends image links that require authentication, Slack posts private links — we want to handle photo and video sharing cleanly both ways.
Making sure filters are solid (so admin replies go out, but client replies don’t bounce back to themselves).
Potential need for instant webhooks instead of polling to avoid backlogs.
What we’d like help with:
Reviewing our current setup and cleaning up the logic so it’s reliable and scalable.
Ensuring best practices (loop guards, rate limiting, file handling).
Possibly restructuring (one scenario vs per-client scenarios) to make it easier to maintain as we grow.
Advice on the best way to handle multiple phone numbers per client in a clean workflow.
We are open to hiring an expert who can spend time inside our scenarios with us to get this polished and stable.
If this is your area of expertise, please reach out!
Hello @Woldenga_Cleaning , welcome to make.com community, I have worked and have experience with Make.com and l will love to collaborate with you on this you can schedule a call Here and you can checkout my upwork profile Here, for my pastworks and certifications
Okay great @Woldenga_Cleaning, I will be expecting the message, and in the meantime if you have any questions or clarifications on my services don’t hesitate to reach out anytime
We’re Make Gold Partners with deep experience building secure, scalable automations on Make.
One thing that sets us apart from many other Gold or Platinum partners is that we’re not simply task-masters who just “do what we’re told.” Our role is to be your strategic consultants — guiding you with solid business advice on what you could, should, and shouldn’t look to automate. That way, you’re not just getting a build, you’re getting a partner who helps you avoid wasted time, unnecessary costs, and mis-steps in your automation journey. We’ll share advice and suggestions at every step — not just execution.
We use our OpsMesh™ framework to guide this work. It’s a three-part system (Audit → Build → Maintain):
• OpsMap™ (Audit) — a structured review that uncovers inefficiencies and gives you a clear, prioritized plan.
• OpsBuild™ (Build) — putting the automation and workflows into place.
• OpsCare™ (Maintain) — ongoing support so everything continues running smoothly as your business grows.
Your request is very clear, and it looks like you’ve already done some of the heavy lifting with Slack, Twilio, and Google Sheets. We’ve helped other teams tackle the same issues you’re facing: handling media links between Slack and Twilio, building airtight loop guards, and restructuring for scale without creating a maintenance headache. Make can absolutely handle native modules where available and secure API connections where needed, so the media and webhook concerns are solvable.
Hi Jessa,
This looks like a well thought out setup with some room for refinement.
Happy to help review the workflows, clean up the logic, and advise on structure moving forward.
Let me know if you want to schedule a time to dig into the details.
As a Make Platinum Partner, we’ve helped several service-based businesses set up Slack ↔ Twilio SMS workflows just like what you’re aiming for. The challenges you mentioned around file handling, loop guards, and scaling across multiple clients are common, and they can definitely be solved with the right setup inside Make.
We’d be happy to review your current scenarios with you and suggest improvements, including media handling and a cleaner approach for multiple phone numbers per client. You can book a call with us here on Calendly .
Looking forward to connecting,
Sreeram k Msquare Automation | Make Platinum Partner
I’ve worked extensively with Make.com, Twilio, and Slack integrations, and your use case is very familiar. I can help you clean up your existing setup, add proper loop guards, handle media sharing seamlessly, and restructure the workflows for better scalability.