Skip to main content

Understanding Queues in Parature from Microsoft

Parature is Microsoft's leading customer service tool in the Dynamics family. It supports multiple channels for customer service, including online self-service, social, phone, chat and more. 

Queues are one of the fundamental concepts of Parature and other customer service products.  They define a structure for presenting tickets to customer service representatives so they can be handled by the right person at the right time. This blog post expands on the material in the Parature knowledge base.  Here is an article with instructions on the steps to create and modify queues.

The most fundamental queue is the customer service representative (CSR) queue.  The queue is a holding place for tickets before they are grabbed by a CSR to work on the issue.   Once they are grabbed, the queue has served its purpose and the ticket will disappear from the queue.  Multiple CSRs could use the same queue, or queues could be personalized for a single CSR, depending on how your CSRs map to the issues and tickets. 

To determine how many queues are needed, you must map out the skills required to resolve a ticket and availability of CSR resources.  For instance, if all CSRs can solve all tickets (a desirable but uncommon state), then one queue would be sufficient for all CSRs. In this case, tickets will be pulled from the queue by each CSR as they are available. 

More commonly, tickets are divided into multiple queues based on the type of issue.  The result is that a CSR specializing in a particular issue would only see tickets for that issue. You want to avoid presenting CSRs with tickets in a queue on which they cannot act.  

Availability of CSRs at different times and service level agreements (SLA) present additional layers of complexity. You may need queues that allow you to map to which CSRs are on duty. For this reason, Parature offers special types of queues:
  • Escalation Queue: for only escalated tickets so critical issues that require special attention can be handled in a timely fashion.
  • Business Hours Queue: You can set up business hours, after hours, or always queues, and assign the appropriate CSRs each queue based on their work schedules.
  • Un-routed Tickets Queue: In the event of a routing rule error make sure you never miss a Ticket with an un-routed Tickets queue.
  • Urgent Queue: For emergency cases or issues to create high visibility for CSRs and managers.  
Parature queues may be used in additional ways that combine features of these queue types to meet your needs.  You set up intelligent workflows to ensure that tickets are assigned to the correct queues.

As you roll out Parature, you may end up refining queues to optimize the performance of your support staff.  Self-service capabilities can change the pattern of trouble tickets over time and affect the workload of CSRs, so you may want to consider revisiting your service desk design from time to time.



Popular posts from this blog

PowerApps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as PowerApps Portal and shifted to the PowerApps side of the Microsoft product family.


Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users.

The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription."

Pricing starts at $200/mo. for 100 dail…

ScreenMeet Remote Support Tool for Dynamics 365 Customer Service

I met Lou Guercia when he was president and CEO of Scribe Software, the leading CRM integration tool.  Scribe was acquired by TIBCO Software in 2018.  I recently reconnected with Lou and learned about ScreenMeet, the company he joined as chief operating officer.   The following is a description of the product provided by ScreenMeet:

ScreenMeet is a cloud-based remote support tool designed to integrate with Dynamics 365 Customer Service. By enabling customer service and IT support organizations to address critical technical issues directly from their CRM or ticketing platform, it streamlines the process and provides a fully browser-based support experience.

You can also use ScreenMeet with other CRM products or even on its own without a CRM.

Here is a short video demo of ScreenMeet with Dynamics integration:


ScreenMeet - Cloud-based Remote Support Integrated with Dynamics 365 Customer Support Once integrated with a Dynamics 365 CS organization, the ScreenMeet widget appears on Case pa…

Microsoft PowerApps and Microsoft Flow Licensing for Beginners

NOTE: Since this post was written, Microsoft has updated pricing.  For current pricing, see https://powerapps.microsoft.com/en-us/pricing

Next month marks two years since Microsoft announced the preview of its Flow workflow automation product.  Since then, PowerApps and Microsoft Flow have been gaining in popularity.

We at InfoStrat are receiving more questions from customers on how PowerApps and Flow are licensed by Microsoft.  This is a brief overview with links to authoritative Microsoft resources with all the details.

What are PowerApps and Flow? Microsoft PowerApps is a framework derived from Dynamics 365 (formerly Dynamics CRM) that allow you to build apps either with or without a form interface.  PowerApps works with Microsoft Flow.

Microsoft Flow is is a cloud software tool to build automated workflows that connect to many Microsoft and non-Microsoft systems and services.  For instance, you could write a workflow which would create a record in Dynamics 365 whenever a new file …