Skip to main content
Skip table of contents

Conversations | Rules for handling conversations in the waiting list

Purpose

This article describes the rules for controlling the handling of conversations in the Waiting List by members.

  • Features described in this article are available in the current version of the Popsell platform.

  • A new scenario to make it mandatory to close conversations might be released later (expected version 4.7.x,Q2 2024).

  • Potential new features are also described in the collapsed section at the end of this article, but are not currently part of the roadmap and there is no confirmation to date that they will ever be released.

First scenario: restrict handling of two many conversations

It is recommended to restrict the members to handle conversations on the waiting list, in order to avoid :

  • one member taking on too many conversations at the same time, and not being able to manage them properly simultaneously,

  • always having the fastest members take on new conversation requests.

Second scenario: force to close conversations

[4.7.x update] Members may also be restricted to handle new conversations without having properly closed their previous dialogues.

Specifications of 1st scenario (handling limitations)

Time penalties

A time penalty can be applied to members regarding they recent conversational activity, according to the rules defined in the following sections.

The aim is to control who has priority among the members, but at the same time avoid blocking the fast handling of conversations. The time constraints applied should remain light.

[4.7.1] When a time penalty is applied, request are hidden in the waiting list.

[4.7.x update] When a time penalty is applied, requests still appear in the waiting list, but they are greyed out. A message is displayed "New requests cannot be handled as you already have ongoing conversations. Please continue your current conversations or ask for a rating if the dialogue if finished.”.

Rules applicable to members' activities

Parameters used

  • Ongoing conversations are determined by messages written by either the member or the visitor in the last 5 minutes.

  • Closed dialogues : if a dialogue has been closed, it is not considered as an on going conversation anymore. Dialogues are considered as closed if a rating has been requested in the period mentioned above, i.e. 5 minutes.

  • Active members : number of active members is calculated based on the time of the last activity. A member is considered active if his last activity is less than 5 minutes old.

Algorithm

Waiting List behaviour in the App:

  • For all the Members without any ongoing conversation, new requests appear in the waiting list as soon as they are created,

  • For members with 1 ongoing conversation, the request will be locked during 15 seconds.

  • For members with 2 ongoing conversations, the request will be locked during 30 seconds.

  • For members with 3+ ongoing conversations, the request will be locked indefinitely.

In all cases,

  • if the conversation request has not been handled within 30 seconds after its creation, a push notification is sent to all Members. This gives offline members a better chance of handling the new request.

  • if only one Member is currently active, no penalty is applied. [Update 4.7.x]

Specifications of 2nd scenario (force to close conversations)

[Update 4.7.x]

Parameters used

  • Unclosed dialogues : number of dialogues established in the last 48 hours, which have not been closed

Algorithm

  • If a Member has more than 2 unclosed dialogues, access to the waiting list is prevented. Requests still appear in the waiting list, but they are greyed out. A message is displayed "New requests cannot be handled as you have too many dialogues in the last 48 hours which need to be closed by asking the visitor for a rating. ”.

  • if only one Member is currently active, no restriction is applied.

Potential new features for a future roadmap

The features described in this section are not currently part of the roadmap and there is no confirmation to date that they will ever be developed.

Other purposes

Additional purposes can be addressed:

  • Avoid having members handling too many conversations vs other members.

  • Beyond that, it is useful to define level of priority and the conditions for members to handle conversations according to their role.

Rules applicable to members’ role

Rule

Description

Priority

Time penalty (in seconds) applicable to incoming requests on the waiting list.

Each role can be assigned a different penalty time.

Filter based on topic

Ability to assign conversation topics to specific member’s roles.

If an assignment has been made to a role, members will only view the requests they are entitled to handle.

Filter based on URL

Ability to filter incoming requests by page, or by a group of pages assigned to a particular role.
For example, requests initiated from one of the pages in the e-commerce site's order tunnel should be handled by the customer service department.

Group pages are defined by URL regexes.

Rules applicable to members individually

Rule

Description

Priority

Time penalty (in seconds) applicable to incoming requests on the waiting list.

Each member can be assigned a different penalty time.

This allows a member to be penalised if an administrator judges the quality of his or her work to be unsatisfactory.

Other rules applicable to Members’ activities

  • Conversations over an extended period : if required by the brand, it is possible to penalize the members based on the number of conversations made over an extended period (e.g. 1 week or 1 month). This is to avoid the same members always answering all the conversations, and to distribute them more evenly between the different members. This should only apply to large communities, such as those encountered in direct sales

Algorithm

A time penalty of 20 seconds can be also assigned to members with a number of conversations handled over an extended period above a threshold (e.g. more than 20 conversations in the last 7 days).

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.