# The "Quick Question" That Never Ends

A client just sent a text message at 9: 45 PM on a Tuesday. It wasn't an emergency. There was no fire, no crashing server, and no one was in danger. It was just a "quick question" about a file they lost three weeks ago.

If you work with people, you know this feeling. It's that tiny, sharp prick of irritation in your chest. It happens when you spend hours-maybe even days-building a perfect, organized way of working, only to have someone treat it like a suggestion rather than a rule.

You have a project management tool. You have an email protocol. You have a specific way of tracking requests so nothing falls through the cracks. Then, suddenly, your phone buzzes. Or a random DM pops up on social media. Or a "quick" voice note arrives via an app you never use for work.

It feels disrespectful. But more importantly, it is incredibly inefficient.

The Chaos of the Shortcut

When a client bypasses your process, they think they are being helpful. They think they are saving time. "It's just faster to text, " they tell themselves.

But they aren't seeing the full picture.

Every time a request comes in through a random channel, it creates a tiny bit of chaos. You have to stop what you are doing. You have to dig through your texts to find the details. You have to manually move that information into your actual system so you don't forget it.

Eventually, that "quick" text becomes a lost piece of information. A deadline is missed. A mistake is made. And strangely enough, the client often blames the process for the very chaos they created.

It is a cycle of small interruptions that eventually lead to big frustrations. It is like trying to build a Lego castle while someone keeps tossing extra pieces at your head from across the room. You can't focus on the structure if you are constantly chasing loose bricks.

Why We Let It Happen

Why do we let them do it? Usually, it's because we want to be "easy to work with. "

We don't want to seem difficult or rigid. We worry that if we say, "Please send that via email, " we will sound like a grumpy librarian or a cold robot. We want to be the helpful partner, the person who is always there to save the day with a quick reply.

But here is the hard truth: Being "easy to work with" is not the same as being professional.

Professionalism is about reliability. And you cannot be truly reliable if your workflow is a mess. If you respond to every late-night text, you are teaching the client that your boundaries don't exist. You are training them to ignore your system.

You aren't

The Art of the Gentle Redirect

So, how do you fix this without making enemies? You don't need to send a stern, angry email. You don't need to ghost them. You just need to redirect.

Think of it like a polite detour on a road. You aren't telling them they can't go to their destination; you are just telling them the correct route to take.

If a client texts you a request, don't solve the problem in the text thread. If you solve it there, you have just validated that texting is an acceptable way to work. Instead, acknowledge the message and move it.

You might say something like: "Hey! I saw your note about the file. To make sure I don't lose this in my texts, could you pop it into our project board? I'll jump on it as soon as I see it there. "

Or, if it's via a random email: "Got it! I'm moving this over to our main task list now so the whole team can see it. It'll be updated there shortly. "

You are being kind. You are being helpful. But you are also being firm. You are reminding them-subtly-that the system exists for a reason: to serve them better.

Setting the Stage Early

The best time to fix this is actually before the chaos starts.

When you start a new relationship with a client, you have to set the "rules of engagement. " This doesn't have to be a boring legal document. It can be a simple, friendly conversation.

"To make sure I give your project the attention it deserves, I use [Software Name] for all requests. This keeps everything in one place so nothing gets missed. I usually check it at [Time] and [Time] every day. "

By saying this, you are framing the process as a benefit to them. You aren't saying "don't talk to me. " You are saying "this is how I ensure your project succeeds. "

It's a subtle shift in perspective. You aren't protecting your time; you are protecting their results.

The Long Game

Boundaries can feel lonely at first. There might be a moment where a client pushes back, or perhaps they seem slightly disappointed that you didn't reply to their 10 PM text instantly.

But stay the course.

Over time, the clients who value quality will respect your process. They will realize that when they use your system, things actually get done faster and better. And the clients who only want "quick and easy" will eventually find someone else-someone who is willing to work in the chaos they prefer.

In the end, a good workflow isn't a wall to keep people out. It's a bridge to help them get where they need to go, without everyone falling into the river along the way.

Sometimes, the most professional thing you can do is say, "Not here, but over there. "