Configure Case Routing Policies in Fullcast


This article provides information and direction on configuring a case routing policy in Fullcast. 

Add a New Case Routing Policy in Fullcast

  1. Access your Fullcast instance and switch plans if applicable. 
  2. Click Manage Policies by Territory on the Policies tile.
  3. Click Add New Policy.
  4. Click Add Policy on the Case Routing tile. 
  5. Configure the routing stages as applicable. 
  6. Configure the Policy Operation Tags and Policy Operation Times.
  7. Click Save and Exit. 

The case routing process consists of several stages, each of which can be switched on or off based on specific requirements. The general stages for case routing are: 

  • Duplicate Processing
  • Role-based Routing
  • Round Robin Settings
  • Default Users and Record Tagging
  • Notifications via Chatter

Duplicate Processing

This stage allows you to define how duplicates are managed when found. 

  1. Toggle the Duplicate Processing switch to ON. 
  2. Define what to do if duplicates from the same domain are found: Do nothing or Route. 
  3. Proceed to the next stage if applicable. 

Role-based Routing

At this stage, you can route incoming cases to an account owner or based on specific criteria. 

  1. Toggle the Role-based Routing switch to ON. 
  2. Identify what to do if the lead is matched to an account: route to owner or route based on specified criteria.
  3. Proceed to the next stage if applicable. 

Round Robin Settings

If you want to assign incoming cases to a team of reps, you can enable round-robin distribution to ensure equal workloads for your salespeople. This option can be combined with the previous stages to optimize workload allocation across different teams and roles. 

  1. Toggle Round Robin Settings to ON. 
  2. Click the radio button to select either Participants or Territories. 

Option Action
Participants
  1. Add any applicable team members.
  2. Identify if there are exceptions to the members added. 
  3. Proceed to Step 3. 
Territories
  1. Identify which territories and their children to add to the list.
  2. Identify any exceptions.
  3. Determine the role to route to. 
  4. Proceed to Step 3. 
  1. Complete the additional configuration options as appropriate. 
  2. Proceed to the next stage if applicable. 

Additional configuration in the Round-Robin stage

  • Additional configuration options in the round-robin stage offer more filter criteria and simplify routing execution. 
  • Bypass the round-robin stage when no matching skills are found by checking the designated box. This allows for direct routing to Default Users and Record Tagging. 
  • If agent support for round-robin routing is required, check the box labeled “Support Agent login for Round-robin routing.” 
  • Limit the number of leads distributed to reps by setting a maximum limit and specifying the amount. 

Default Users and Record Tagging


In this stage, set a default user or queue to send incoming cases to. 

  1. Toggle Default Users and Record Tagging to ON. 
  2. Select whether to route to a queue or user. 
  3. Identify the queue or user as appropriate. 
  4. Click the grey plus button to identify what fields to update on the case. 
  5. Select the Don’t update the Owner Field option if applicable. 
  6. Proceed to the next stage if applicable. 

Notifications via Chatter

Notifications via chatter will send messages to users when incoming leads are routed. 

To configure notifications via Chatter

  1. Toggle the Notifications via Chatter switch to ON. 
  2. Add additional text to send in the notifications if applicable.
  3. Identify the additional people to send notifications to besides the owner. 
  4. Click Save and Exit. 

Policy Operation Tags and Policy Operation Times

The tag field in routing policies directs items to specific queues, such as those based on lead geographical region, or industry. Using tag operators, you can create formula-based routing that efficiently matches as many records as possible for better management. 

Policy Operations Times allows you to define times when the queue will be open or closed. By default, the queue is available at all times. 

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us