Can a simple presence change prevent lunch from becoming a support bottleneck?
Implement a clear procedure. Configure the zendesk away status to reflect real-time availability. Ensure the chat widget shows accurate presence to customers.
Assign permissions at the account level. Grant agents permission to modify their own agent status. Verify roles and permissions before rollout.
Route incoming tickets from the chat channel with definitive rules. Use triggers and capacity controls to preserve coverage during peak hours.
This section defines the operational question and the precise controls required. Follow the steps that follow to align availability, tickets, and messaging for predictable support outcomes.
Key Takeaways
- Configure presence: Set the zendesk away status so customers see true availability.
- Grant permissions: Allow agents to change their agent status independently.
- Optimize the chat widget: Display availability during peak hours and lunch.
- Route tickets: Apply triggers to ensure chat-generated tickets reach the right queue.
- Manage conditions: Use capacity and rules to prevent coverage gaps.
Understanding Zendesk Away Status and Availability Options
Establish explicit definitions for each agent presence to ensure predictable routing.
Define states before applying routing rules.
Defining Online, Away, and Invisible States
The Online state indicates that agents are available to accept incoming chat requests through the chat widget.
The Away state signals to the team that an agent is occupied and not accepting new conversations.
The Invisible mode lets an agent sign in while remaining hidden from customers—this renders the widget effectively offline if all agents use it.
Impact on Customer Experience and Widget Visibility
Each presence choice influences routing for chat and email channels.
If all agents are invisible, customers see the widget as offline; routing moves to email or queued messaging flows.
Managers must monitor availability during peak hours to prevent coverage gaps and to maintain consistent conversation handoffs.
- Online: active handling via chat widget.
- Away: internal busy signal to the team.
- Invisible: sign-in without appearing to customers—widget offline.
Understanding these options is a vital detailssign see for optimizing messaging and maintaining service levels.
How to Manually Configure Your Zendesk Away Status
Open the Chat dashboard and choose the availability menu in the upper-left corner.
Select the correct option to reflect real-time agent availability. This step updates the chat widget visibility and affects routing for chat and email.
Confirm that each agent has permissions in the account settings to modify their own availability. Administrators must verify role assignments before shift changes.
Perform this step at shift start and before breaks. Proper agent status configuration reduces misrouted tickets and prevents conversation handoffs to unavailable agents.
- Click the upper-left dropdown on the Chat dashboard to change availability.
- Ensure permissions allow each agent to update their agent status.
- Document the hours when manual switches are required.
| Action | Location | Permission Required | Impact on Tickets |
|---|---|---|---|
| Set available | Chat dashboard menu | Agent modify allowed | Receives new conversations |
| Set unavailable | Chat dashboard menu | Agent modify allowed | Routes to email or queue |
| Verify permissions | Account settings | Admin required | Prevents misrouting |
Automating Status Changes with Idle Timeout Settings
Set idle timeout thresholds to ensure the chat widget reflects real activity.
Automate presence to reduce manual updates during long hours.
Configuring Inactivity Periods
Enable the idle timeout feature in Classic Chat to move agents to idle after defined minutes of inactivity.
Default inactivity is 15 minutes. Change the minutes to match shift patterns and peak hours.
- Ignore if chatting: Prevents automatic changes during an active conversation.
- Accurate availability: Keeps the chat widget aligned with real agent activity.
- Time savings: Reduces manual steps for agents across the work day.
| Setting | Default | Recommended use |
|---|---|---|
| Idle timeout | 15 minutes | Adjust to match typical inactivity times per day |
| Ignore if chatting | Disabled by default | Enable to avoid interrupting active conversations |
| Browser check | N/A | Require browser activity for accurate agent status |
Managing Chat Routing and Department Availability
Choose routing logic that matches departmental workflows and peak hours.
Broadcast versus Assigned Routing
Broadcast routing sends incoming chat to all available agents. The first agent to accept the conversation handles the request. Use broadcast for general queues and high-volume hours.
Assigned routing directs chats to specific agents or groups. Use assigned for specialized departments or VIP customers. The chat widget then displays availability only for eligible staff.
Capacity Rules and Concurrent Limits
Set capacity limits to prevent overload. Configure concurrent chat caps per agent to protect response quality during busy hours.
- Limit concurrent conversations per agent—match limits to average handling time.
- Use departments to segregate traffic—this keeps tickets and email workflows organized.
- Combine routing with triggers to move overflow to email or queue when capacity is full.
| Routing | Best use | Impact on agents |
|---|---|---|
| Broadcast | General support queues | Faster first response; higher chance of collisions |
| Assigned | Specialized teams | Precise ownership; lower routing noise |
| Capacity rules | Peak hours control | Prevents burnout; maintains SLAs |
For configuration guidance, review the chat availability settings.
Implementing Unified Agent Status for Omnichannel Support
Centralize availability controls to ensure one agent setting governs email, voice, and chat channels.
Enable the unified agent feature in the account to control availability from a single menu. This feature maps an agent’s online/offline state across channels—email, voice, and messaging.
Configure custom entries to match shift patterns and peak hours. Professional plans permit up to five custom unified statuses. Enterprise plans permit up to one hundred for complex team structures.
- Consistency: One agent status prevents the widget from showing incorrect availability to customers.
- Routing: Define custom states to direct tickets and conversations to the correct queue or channel.
- Permissions: Grant account-level rights so agents can change their agent status when required.
Validate configuration before rollout. Test across chat and email channels to confirm the widget and ticket routing reflect the intended availability and do not mark agents offline erroneously.
Best Practices for Maintaining Consistent Team Coverage
Align shifts with traffic spikes to ensure continuous chat coverage and predictable response times.
Plan agents’ hours to match peak times. Stagger breaks and lunch so conversations always have a receiving agent.
Monitor the widget and capacity rules hourly. Adjust concurrent limits when overflow or long wait times appear.
Troubleshoot browser extensions that affect idle timeouts. Confirm browser settings to keep availability accurate across the day.
Use proactive triggers during business hours — but train each agent to handle the extra conversation volume when messages increase.
For management templates and team planning, review guidance on managing virtual teams and how to schedule office hours in shared calendars.
