Three days later, you’re still waiting.
When you follow up, you get a reply that reads like it was generated by an excuse algorithm:
“We’re currently experiencing high ticket volume. Your request has been escalated to our Level 2 team and is in the queue for review. We appreciate your patience.”
Meanwhile, your new landing page isn’t resolving, your email deliverability is tanking, and you’re explaining to your boss why a “simple” request is now a week long odyssey.
Sound familiar?
You’re not alone. And no, you’re not being unreasonable. Let’s talk about why so many IT companies, especially those managing Cloudflare, DNS, email, and hosting, are maddeningly slow, and what they’re actually doing while you wait.
The Secret: You’re Not the Only Client (And You’re Probably Not the Biggest)
Most managed IT providers and MSPs (Managed Service Providers) operate on a model that prioritises volume over velocity.
Here’s the maths:
- They charge you $200–$500/month for “managed IT support.”
- To make that profitable, they need 50–200+ clients per technician.
- Your 30 second DNS change is ticket #47 in a queue behind password resets, printer issues, and someone’s Outlook that “just stopped working.”
You’re paying for access to a queue, not a dedicated resource.
The business model works for them. It doesn’t work for you when you need something done now.
What They’re Actually Busy Doing (Instead of Your Request)
1. Fighting Fires for Clients Who Pay More
Enterprise clients with higher retainers get priority. If a $5,000/month client has an Exchange server down, your Cloudflare ticket goes to the back of the line, regardless of when you submitted it.
2. Quoting and Onboarding New Clients
Sales and onboarding generate revenue. Your support ticket doesn’t. In many MSPs, the same technicians who handle support also help onboard new accounts. Guess which one gets attention when the sales team is pushing?
3. Navigating Their Own Bureaucracy
Larger IT providers have tiered support systems: Level 1 triages, Level 2 investigates, Level 3 actually does things. A simple request can bounce between tiers for days because no one wants to “own” a task outside their narrow scope.
4. Waiting on their Vendors
Sometimes they’re slow because they’re waiting on someone else, a hosting provider, a domain registrar, or their own internal approvals. They won’t always tell you this. It’s easier to blame “the queue.”
5. Absolutely Nothing
Let’s be honest: some providers are simply disorganised, understaffed, or complacent. When clients are locked into contracts and switching costs are high, there’s less pressure to perform.
The Excuse Playbook: Translations Included
You’ve heard these. Here’s what they actually mean:
| What They Say | What They Mean |
|---|---|
| “This has been escalated to our senior team.” | It’s been reassigned to someone who’s also overloaded. |
| “We’re waiting on a change window.” | We batch changes to reduce our workload, not for technical reasons. |
| “DNS propagation can take 24–48 hours.” | The change itself takes seconds. We just haven’t done it yet. |
| “We need to follow our change management process.” | We’ve built bureaucracy to protect ourselves from blame, not to help you. |
| “Your ticket is in the queue.” | We have no ETA and won’t until someone looks at it. |
| “We’re experiencing higher than normal volume.” | This is our normal volume. We’re just slow. |
The classic: “DNS propagation takes 24–48 hours.”
Let’s kill this myth. Modern DNS changes propagate globally in minutes, often seconds, especially with Cloudflare’s infrastructure. When an IT provider uses this line, they’re either uninformed or stalling.
Why Email and Cloudflare Requests Are Especially Painful
DNS and email sit in an uncomfortable middle ground:
- They’re critical. A broken MX record means no email. A wrong A record means your site is down.
- They’re “invisible.” Non technical stakeholders don’t understand them, so IT providers face less pressure to prioritise.
- They’re quick to fix but slow to ticket. The actual work takes 30 seconds to 5 minutes. The overhead of reading the ticket, logging into Cloudflare, verifying the domain, and documenting the change takes longer, so it gets deferred.
Email hosting is worse. DKIM, SPF, and DMARC records require precision. If your IT provider doesn’t specialise in email deliverability, they’ll treat your request like a research project instead of a routine task.
The Real Cost of Slow IT Support
This isn’t just an annoyance. It’s a business problem:
- Lost revenue: Landing pages that don’t resolve, forms that don’t submit, campaigns that can’t launch.
- Damaged deliverability: Email authentication issues compound daily. Every day without correct SPF/DKIM is another day your emails hit spam.
- Wasted time: You’re spending hours following up instead of doing your actual job.
- Opportunity cost: That product launch, that PR moment, that partnership announcement, delayed because someone couldn’t add a CNAME.
What You Can Do About It
1. Get Direct Access to Your Own Accounts
This is the single most impactful change.
- Cloudflare: You should own the account. Your IT provider can be added as a member with limited permissions if needed.
- Domain Registrar: Own your domain directly with any domain Registrar.
- Email Hosting: Use Google Workspace or Microsoft 365 admin access yourself, or ensure you have owner level credentials.
If your IT provider insists on owning these accounts “for security,” push back. You’re paying for the service. You should have access to the assets.
2. DIY.
Tools like GPT and Claude can walk you through almost any Cloudflare or email configuration task in plain English. Need to add a CNAME record? Ask AI. Need to set up DKIM for Google Workspace? Ask AI. It will give you step by step instructions with screenshots descriptions, explain what each setting does, and tell you exactly what to paste where.
The process:
Describe what you’re trying to do (“I need to point my subdomain shop.mysite.com to Shopify”)
Get clear, specific instructions for your exact platform
Follow the steps in Cloudflare’s dashboard, which, despite what your IT provider implies, is genuinely straightforward.
3. Fire Slow Providers
If you’ve raised the issue, documented delays, and nothing changes, leave.
Yes, migration is painful. Yes, there’s switching cost. But the cost of staying with a provider who treats your business as an afterthought is higher.
The Bottom Line
Your IT provider isn’t slow because Cloudflare is complicated or DNS is mysterious. They’re slow because:
- Their business model deprioritises small requests.
- Their internal processes are built for their convenience, not yours.
- They face no consequences for delays.
The fix isn’t better tickets or more polite follow ups. It’s taking control of your critical infrastructure and holding providers to real standards.
You shouldn’t need to wait three days for a 30 second task. And if your current provider can’t deliver, there are plenty who can.