Skip to content
FacebookYouTubeX (Twitter)

Move to Unassigned Action

Move to Unassigned Action

This action sets the chat status to Unassigned. It’s useful if you have Smart Assignment active and want to manage all chat requests through the Unassigned queue.

When you have the Smart Assignment option active, all chat requests in the Unassigned status (aka put in the Unassigned queue) will be delivered to Agents in a FIFO (First In, First Out) way based on the chat request’s creation time.

If a user is in a flow with a chatbot, you have many ways to assign it to the respective agent when this moment comes:

One way is through the Agent Handoff Action. This Action will find an available agent based on the Agent’s availability status. This means that the Agent Handoff will do its best to assign the request to an agent that is both:

  1. In the available status
  2. With a number of assigned chats (aka chat requests) under the Maximum chats option of the Smart Assignment section

Smart Assignment Configuration

When Smart Assignment is active, it’s generally preferable to not try the approach of directly assigning a chat to an agent. It’s better to directly put the incoming chat in the Unassigned queue and let the Smart Assignment module (if active) dequeue the chats and assign them to available agents based on the arrival (creation) time.

Ensures that chat requests are distributed fairly among available agents based on arrival time.

Provides better visibility and control over pending chat requests.

Automatically balances workload across available agents without manual intervention.

Maintains consistent service levels by following FIFO principles.

When you want to leverage the Smart Assignment system for optimal agent distribution.

When implementing a support system that requires proper queuing and fair distribution.

In busy environments where multiple agents need to handle incoming requests efficiently.

When you want to maintain separate queues for different departments or specialties.

Ensure Smart Assignment is properly configured before using this action.

Configure maximum chat limits per agent to prevent overload.

Regularly check queue metrics and agent response times.

Keep customers informed about their position in the queue.

Communicate expected wait times to users.

Use conditions to determine when to move chats to unassigned:

If peak_hours = true → Move to Unassigned
If agent_availability = low → Move to Unassigned

Check agent availability before deciding on assignment method:

If agents_online → Direct assignment
Else → Move to Unassigned for queue processing

Inform users about queue status and expected wait times.

Maximum Chats per Agent: Controls how many simultaneous chats each agent can handle.

Assignment Algorithm: FIFO ensures fair distribution based on arrival time.

Agent Availability: Only assigns to agents marked as available.

Department Filtering: Can be configured to respect department boundaries.

  • Average wait time: How long users wait in the unassigned queue
  • Queue length: Number of pending requests at any time
  • Agent utilization: How effectively agents are being utilized
  • Response time: Time from assignment to first agent response
  • Abandonment rate: Users who leave the queue before being served
  • Shorter wait times indicate good agent availability
  • High queue lengths may indicate need for more agents
  • Low agent utilization suggests over-staffing or inefficient routing
  • Increase agent staffing during peak hours
  • Review maximum chat limits per agent
  • Optimize bot flows to resolve more issues automatically
  • Monitor real-time queue status
  • Implement priority routing for urgent issues
  • Add more agents or extend working hours
  • Verify Smart Assignment settings
  • Check agent availability status
  • Review department configurations

Combine with condition actions to implement priority queues:

If customer_tier = "VIP" → Priority assignment
Else → Move to Unassigned (standard queue)

Use as fallback when direct assignment fails:

Agent Handoff → If successful: Direct assignment
If failed: Move to Unassigned

Route to different unassigned queues based on inquiry type:

Sales inquiry → Sales unassigned queue
Technical issue → Technical unassigned queue

The Move to Unassigned action is essential for implementing fair, efficient queue management in Pingstreams, especially when combined with Smart Assignment to ensure optimal distribution of chat requests among available agents.

For more information about Smart Assignment configuration and queue management best practices, contact our support team or explore our comprehensive Pingstreams documentation.