A blocked app cannot negotiate your availability for you. The strongest boundary combines a clear response expectation, iOS attention controls, and a reversible network rule that you—not your workplace—control.
Name the real goal.
“Stop my boss messaging me” mixes several problems together. Do you want no sound, no banner, no temptation to open the app, no fresh work content, or a documented expectation that replies wait until morning? Each goal needs a different control.
Start with the least destructive boundary. Silence an interruption before disabling connectivity. Disable connectivity before disconnecting the whole device.
Build three layers.
1. State the expectation
Agree on working hours, the expected response time, and the channel for a real emergency. Put it in writing where appropriate. A technical block without a shared expectation can create confusion rather than a boundary.
2. Control attention
Use iOS Focus and per-app notification settings to remove sounds, banners, badges, and lock-screen exposure during personal time. These controls are better than network blocking when your goal is simply not to be interrupted.
3. Control refreshing
If seeing new work content is itself the problem, selective DNS filtering can stop matching new lookups for the work app while personal apps stay online.
Add a reversible network boundary.
- Open LetMeBe and include the work-messaging app in Blocking.
- Turn Blocking on only when your off-hours boundary begins.
- Close and reopen the target app so it must perform new DNS lookups.
- Verify a personal app still loads fresh content.
- Turn Blocking off before the next agreed availability window.
LetMeBe does not currently provide a scheduling promise, so do not build a policy around an automatic switch that is not there. Use an ordinary reminder or a personal routine to change the state deliberately.
Filtering is not an emergency-communications system. Existing sessions, shared infrastructure, cached content, and Apple notifications can produce partial or delayed behavior.
Design exceptions before you need them.
Decide what qualifies as urgent, who can invoke it, and which channel remains available. A phone call from a defined contact is clearer than treating every chat notification as an emergency.
If you are on-call, responsible for safety, or contractually required to respond, make sure the boundary fits those duties. This article is a product workflow, not employment or legal advice.
Review the outcome after a week.
- Did the interruption decrease?
- Did colleagues understand when to expect a reply?
- Did any unrelated app lose connectivity?
- Did you remember to restore access at the intended time?
- Would Focus alone solve the problem with less friction?
Keep only the layer that earns its complexity. If notification controls solve the problem, remove the network rule. If a network boundary helps, keep it narrow and test it after app or iOS updates.