Quick answer

Keep Slack Active at a Coworking Space

Coworking spaces combine unreliable shared WiFi, network switching, and captive portals that repeatedly break Slack's connection. Idle Pilot runs on stable cloud servers with dedicated internet, keeping your Slack green no matter how bad the coworking WiFi gets.

Why this happens

Coworking spaces present a unique combination of networking challenges that all affect Slack presence. Shared WiFi is the biggest issue. When 50 or 100 people share a single WiFi network, bandwidth per user drops, latency increases, and packet loss rises. Slack's WebSocket connection is sensitive to all three. Captive portals are another problem. Many coworking spaces require re-authentication every few hours or after a certain amount of data usage. When the captive portal intercepts your traffic, it breaks Slack's WebSocket connection. You might not even notice the portal popped up until you try to browse, but Slack already went away in the background. Network switching compounds the issue. Moving between floors, rooms, or common areas in a coworking space often means connecting to different access points. If the coworking space uses multiple SSIDs or VLANs, your IP address changes with each switch, forcing Slack to reconnect. Some coworking spaces also implement bandwidth throttling or QoS policies that deprioritize WebSocket connections in favor of HTTP traffic. Slack's presence heartbeat might get queued behind someone else's large file upload. Public IP changes can also trigger Slack's security measures, briefly interrupting the session. The overall effect is that coworking WiFi creates an unreliable foundation for any real-time connection.

The reliable solution

Local workarounds try to keep your device active, but they can't solve the fundamental problem: Slack needs constant signals from your device. When your device sleeps, locks, or loses connection, those signals stop.

Cloud-based presence scheduling Cloud-based presence scheduling like Idle Pilot runs on always-connected servers. It maintains your Slack status during scheduled hours regardless of what your device is doing.

Works even when your laptop is closed or off
No local installs or device workarounds needed
No workspace bot or admin approval required
Set your schedule once, it handles the rest

Try Idle Pilot free for 7 days

Platform-specific options

Here are platform-specific settings you can adjust. Note that these are workarounds with limitations, not complete solutions.

Mac

1 Prefer 5GHz WiFi bands over 2.4GHz for less interference in crowded spaces
2 If the coworking space has Ethernet ports, use a USB-C to Ethernet adapter for stability
3 Disable 'Ask to join networks' in System Settings > WiFi to avoid accidental network switches
4 Forget any networks you don't actively use to prevent your Mac from auto-joining weak signals

Limitation: Even on the best coworking WiFi, shared bandwidth and captive portals cause drops. You can't control the network infrastructure.

Windows

1 Connect to the 5GHz network if available for better throughput and less interference
2 Bring a USB Ethernet adapter for a more reliable wired connection
3 In Settings > Network > WiFi > Manage known networks, remove old coworking networks to prevent auto-join issues
4 Disable 'Metered connection' for the coworking WiFi to prevent Windows from throttling background data

Limitation: You can optimize your end, but shared network quality depends on the coworking space's infrastructure and how many people are connected.

Set up scheduled presence in 3 steps

Get reliable Slack presence without device workarounds:

Step 1

Connect your Slack account

Authorize Idle Pilot to update your presence. This uses Slack's standard OAuth, no workspace bot installation needed.
Step 2

Set your schedule

Choose the days and hours you want to appear active. Set your timezone so it aligns with your actual work hours.
Step 3

Enable and forget

Turn on your schedule and you're done. Idle Pilot keeps your Slack status active during those hours, regardless of your device state.

Troubleshooting

Slack goes away every time the captive portal re-authenticates

Captive portals redirect all traffic, breaking WebSocket connections. Cloud scheduling is unaffected because it connects to Slack from servers outside the coworking network.

WiFi is fine for browsing but Slack keeps disconnecting

HTTP requests can tolerate more latency and packet loss than WebSocket connections. Slack's real-time presence needs consistent, low-latency connectivity. Cloud scheduling doesn't depend on your local WiFi quality.

Slack presence drops when moving between floors or rooms

Moving between access points causes IP changes and brief disconnections. Each one can trigger Slack's away timer. Cloud scheduling provides stable presence regardless of your physical location in the space.

FAQs

Why does coworking WiFi cause more Slack issues than my home WiFi?

Coworking WiFi is shared among dozens or hundreds of users, leading to bandwidth contention, higher latency, and more packet loss. Home WiFi typically serves a few devices with a dedicated connection. The shared nature of coworking networks makes real-time connections like Slack's WebSocket unreliable.

How do captive portals affect Slack presence?

Captive portals intercept all network traffic to display a login page. When the portal re-authenticates (often every few hours), it kills Slack's WebSocket connection. You might not notice the portal until you open a browser, but Slack has already gone away.

Should I use an Ethernet adapter at the coworking space?

If your coworking space has Ethernet ports, a wired connection is almost always more reliable than WiFi. You avoid wireless interference, get more consistent latency, and bypass some WiFi-specific issues. A USB-C to Ethernet adapter is small enough to carry daily.

Does switching coworking rooms or floors affect Slack?

Moving between areas often means connecting to different access points. If the coworking space uses different subnets per floor, your IP address changes, forcing Slack to reconnect. Even seamless roaming between access points can cause brief drops that affect presence.

Can I use my phone hotspot instead of coworking WiFi for Slack?

A personal hotspot gives you a dedicated connection, which can be more stable than shared WiFi. The tradeoff is battery drain on your phone and potential carrier throttling. For Slack's low bandwidth needs, hotspot is often more reliable than congested coworking WiFi.

My coworking space has 'high-speed WiFi' but Slack still drops. Why?

Advertised speed doesn't reflect real-world performance with many simultaneous users. High-speed WiFi can still have congestion, packet loss, and latency spikes during peak hours. Slack needs consistent connectivity more than raw speed. Cloud scheduling removes your dependency on the coworking network.