CommEngine
  • About CommEngine
  • CommEngine sCRM & Customer Growth Solution | Support & Service Structure
  • SLA
  • Messages after 24 hour
  • HOW YOU CAN MEASURE YOUR CXM (CUSTOMER EXPERIENCE MANAGEMENT) EFFORT
  • Feature Guideline
    • CommEngine Introduced the New Follow-Up Feature
    • AUTO-ASSIGN: CommEngine IJM
      • Things To Know About Auto-Assign
      • CommEngine Intelligent Job Manager
      • DISTRIBUTION PROCEDURE: HOW TO GET RID of MESS :)
      • NEED MORE TECHNICAL EXPLANATION? HERE IT IS .ed
    • Account Opening
    • AI Profiling
    • Demo Account
    • Feed
    • Filter by Time and Customize Date
    • Tags
    • Assign Management & Notification Mail
    • Search a user in the inbox
    • How to set Follow-Up Reminder
    • Token Refresh
    • Campaign
    • User Administration
    • Social Media Guide
    • Token Refresh
    • Order Management with CommEngine
    • Lead management
    • Lead Management lifecycle
    • How to Set Company Logo
  • Feature Guideline Bangla
    • Sign Up
    • Ai profiling
    • Campaign
    • Campaign benefit
    • Query management ( Feeds)
    • Token Refresh
    • How to purchase Campaign Balance
    • Wallet recharge
  • Guideline to CRM
    • CommEngine Social CRM 101
Powered by GitBook
On this page

Was this helpful?

  1. Feature Guideline
  2. AUTO-ASSIGN: CommEngine IJM

DISTRIBUTION PROCEDURE: HOW TO GET RID of MESS :)

DISTRIBUTION PROCEDURE: HOW TO GET RID FROM MESS :)

Distribution of tickets to logged-in users

Tickets will be distributed with the following thumb rule:

  1. The ticket should be distributed equally

  2. The ticket should be distributed as per individual handling capacity

Distribution mechanism can be understood by the following case studies:

CASE STUDY 01:

For example: Logged-in users: 2

User 1: Handling capacity: 80

User 2: Handling capacity: 20

If total handling capacity is 100 and ticket count is 50, then average capacity will be 25 per each user.

  1. User 1 will get the 25 tickets and User 2 will get 20 tickets at the first iteration.

  2. Remaining 5 tickets will be distributed to the user 1 at the second iteration.

CASE STUDY 02:

For example: Logged-in users: 2

User 1: Handling capacity: 20

User 2: Handling capacity: 80

If total handling capacity is 100 and ticket count is 50, then average capacity will be 25 per each user.

  1. User 1 will get the 20 tickets and User 2 will get 25 tickets at the first iteration.

  2. Remaining 5 tickets will be distributed to the user 2 at the second iteration.

CASE STUDY 03:

For example: Logged-in users: 2

User 1: Handling capacity: 50

User 2: Handling capacity: 50

If total handling capacity is 100 and ticket count is 50, then average capacity is 25 per each user.

  1. User 1 will get the 25 tickets and User 2 will get 25 tickets at the first iteration.

CASE STUDY 04:

For example: Logged-in users: 3

User 1: Handling capacity: 20

User 2: Handling capacity: 30

User 3: Handling capacity: 50

If total handling capacity is 100 and ticket count is 100, then average capacity is 33 per user.

  1. User 1 will get the 20 tickets, User 2 will get 30 tickets and User 3 will get 33 tickets at the first iteration.

  2. Remaining 17 tickets will be distributed to the user 3 at the second iteration.

Interested to know more? Don't worry
buzz us: contact@commengine.xyz | www.facebook.com/supportCE

PreviousCommEngine Intelligent Job ManagerNextNEED MORE TECHNICAL EXPLANATION? HERE IT IS .ed

Last updated 4 years ago

Was this helpful?