Abstract: Contacts are managed within a contact centre by representing each contact as a software object which contains skillset and priority identifiers. Contact objects are queued relative to one another by means of references to and/or from the object(s) immediately ahead of and behind each contact. In this way a conventional queue can be dispensed with. Queries can be made to a plurality of contact centres across a network to identify objects matching certain criteria at the top of each local queue. In this way a set of local queues substitutes for a network queue providing increased resilience in the case of the failure of any individual component of the network or of the network itself.

Abstract: Contacts are managed within a contact centre by representing each contact as a software object which contains skillset and priority identifiers. Contact objects are queued relative to one another by means of references to and/or from the object(s) immediately ahead of and behind each contact. In this way a conventional queue can be dispensed with. Queries can be made to a plurality of contact centres across a network to identify objects matching certain criteria at the top of each local queue. In this way a set of local queues substitutes for a network queue providing increased resilience in the case of the failure of any individual component of the network or of the network itself.

Abstract: Contacts are managed within a contact centre by representing each contact as a software object which contains skillset and priority identifiers. Contact objects are queued relative to one another by means of references to and/or from the object(s) immediately ahead of and behind each contact. In this way a conventional queue can be dispensed with. Queries can be made to a plurality of contact centres across a network to identify objects matching certain criteria at the top of each local queue. In this way a set of local queues substitutes for a network queue providing increased resilience in the case of the failure of any individual component of the network or of the network itself.

Abstract: A method and system are provided for generating statistical information from input data relating to the operation of a monitored system over time. The monitored system is preferably a contact center or call centre. The method involves pegging input data relating to the operation of the system over a finite time interval and storing this pegged data in a record so that the contents of the record are identifiable according to the finite time interval to which the data relates. This pegging is repeated continually resulting in a large number of records being stored, each containing data relating to a short time interval. The pegged data from the revelant records can then be used multiple times in a variety of statistical threads or windows rather than having each statistical thread engine peg the information it requires separately.

Abstract: Contacts are managed within a contact centre by representing each contact as a software object which contains skillset and priority identifiers. Contact objects are queued relative to one another by means of references to and/or from the object(s) immediately ahead of and behind each contact. In this way a conventional queue can be dispensed with. Queries can be made to a plurality of contact centres across a network to identify objects matching certain criteria at the top of each local queue. In this way a set of local queues substitutes for a network queue providing increased resilience in the case of the failure of any individual component of the network or of the network itself.