Call center network diagram

"A call centre or call center is a centralised office used for the purpose of receiving or transmitting a large volume of requests by telephone. An inbound call centre is operated by a company to administer incoming product support or information inquiries from consumers. Outbound call centers are operated for telemarketing, solicitation of charitable or political donations, debt collection and market research. In addition to a call centre, collective handling of letter, fax, live support software,social media and e-mail at one location is known as a contact centre.
A call centre is operated through an extensive open workspace for call centre agents, with work stations that include a computer for each agent, a telephone set or headset connected to a telecom switch, and one or more supervisor stations. It can be independently operated or networked with additional centres, often linked to a corporate computer network, including mainframes, microcomputers and LANs. Increasingly, the voice and data pathways into the centre are linked through a set of new technologies called computer telephony integration (CTI)." [Call centre. Wikipedia]
This call center network diagram example was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Telecommunication Network Diagrams solution from the Computer and Networks area of ConceptDraw Solution Park.

"An issue tracking system (also ITS, trouble ticket system, support ticket, request management or incident ticket system) is a computer software package that manages and maintains lists of issues, as needed by an organization. Issue tracking systems are commonly used in an organization's customer support call center to create, update, and resolve reported customer issues, or even issues reported by that organization's other employees. An issue tracking system often also contains a knowledge base containing information on each customer, resolutions to common problems, and other such data. An issue tracking system is similar to a "bugtracker", and often, a software company will sell both, and some bugtrackers are capable of being used as an issue tracking system, and vice versa. Consistent use of an issue or bug tracking system is considered one of the "hallmarks of a good software team".
A ticket element, within an issue tracking system, is a running report on a particular problem, its status, and other relevant data. They are commonly created in a help desk or call center environment and almost always have a unique reference number, also known as a case, issue or call log number which is used to allow the user or help staff to quickly locate, add to or communicate the status of the user's issue or request.
These tickets are so called because of their origin as small cards within a traditional wall mounted work planning system when this kind of support started. Operators or staff receiving a call or query from a user would fill out a small card with the user's details and a brief summary of the request and place it into a position (usually the last) in a column of pending slots for an appropriate engineer, so determining the staff member who would deal with the query and the priority of the request." [Issue tracking system. Wikipedia]
The UML activity diagram example "Ticket processing system" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Rapid UML solution from the Software Development area of ConceptDraw Solution Park.

This BPMN (Business Process Model and Notation) diagram sample represents the taxi service order procedure workflow.
"A business process or business method is a collection of related, structured activities or tasks that produce a specific service or product (serve a particular goal) for a particular customer or customers. It often can be visualized with a flowchart as a sequence of activities with interleaving decision points or with a Process Matrix as a sequence of activities with relevance rules based on data in the process. ...
There are three types of business processes:
(1) Management processes, the processes that govern the operation of a system. Typical management processes include "corporate governance" and "strategic management".
(2) Operational processes, processes that constitute the core business and create the primary value stream. Typical operational processes are purchasing, manufacturing, advertising and marketing, and sales.
(3) Supporting processes, which support the core processes. Examples include accounting, recruitment, call center, technical support. ...
The ... improvement areas are equally applicable to policies, processes and detailed procedures (sub-processes/ tasks). There is a cascading effect of improvements made at a higher level on those made at a lower level.
For instance, if a recommendation to replace a given policy with a better one is made with proper justification and accepted in principle by business process owners, then corresponding changes in the consequent processes and procedures will follow naturally in order to enable implementation of the policies" [Business process. Wikipedia]
The business process modeling diagram example "Taxi service order procedure - BPMN 1.2 diagram" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Business Process Diagram solution from the Business Processes area of ConceptDraw Solution Park.