Leaky bucket diagram

"The leaky bucket theory The leaky bucket theory is the model that seeks to describe the process of customer gain and loss, otherwise known as customer churn . Customer retention is one of the key concepts in relationship marketing. Most companies concentrate on recruiting new customers to replace customers who move on, rather than seeking to retain customers." [Blythe J. Key Concepts in Marketing. 2009. knowledge.sagepub.com/ view/ key-concepts-in-marketing/ n5.xml]
"Customer attrition, also known as customer churn, customer turnover, or customer defection, is the loss of clients or customers.
Banks, telephone service companies, Internet service providers, pay TV companies, insurance firms, and alarm monitoring services, often use customer attrition analysis and customer attrition rates as one of their key business metrics (along with cash flow, EBITDA, etc.) because the "...cost of retaining an existing customer is far less than acquiring a new one." Companies from these sectors often have customer service branches which attempt to win back defecting clients, because recovered long-term customers can be worth much more to a company than newly recruited clients." [Customer attrition. Wikipedia]
The example "Leaky bucket diagram" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Marketing Diagrams solution from the Marketing area of ConceptDraw Solution Park.

"Decision-making can be regarded as the cognitive process resulting in the selection of a belief and/ or a course of action among several alternative possibilities. Every decision-making process produces a final choice that may or may not prompt action. ...
Decision-making can also be regarded as a problem-solving activity terminated by a solution deemed to be satisfactory. It is, therefore, a reasoning or emotional process which can be rational or irrational and can be based on explicit assumptions or tacit assumptions. Most decisions are followed by some form of cost-benefit analysis. Rational choice theory encompasses the notion that people try to maximize benefits while minimizing costs.
Some have argued that most decisions are made unconsciously, if not involuntarily. Jim Nightingale, author of Think Smart – Act Smart, states that "we simply decide without thinking much about the decision process. ...
A major part of decision-making involves the analysis of a finite set of alternatives described in terms of evaluative criteria. Information overload occurs when there is a substantial gap between the capacity of information and the ways in which people may or can adapt."" [Decision-making. Wikipedia]
The block diagram example "Customer decision making" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Block Diagrams solution from the area "What is a Diagram" of ConceptDraw Solution Park.

This customer types matrix diagram distribute customers into four categories depending of two criteria: 1) desired degree of proximity between customers and suppliers, and 2) types of relations that expect customers.
One time customers have short-term relations with suppliers and characterized by distance in relations with them.
Loyal customers have long-term relations with suppliers and characterized by distance in relations with them.
Customers who exploit relationships have short-term relations with suppliers and characterized by proximity in relations with them.
Relationship seekers have long-term relations with suppliers and characterized by proximity in relations with them.
This customer types matrix diagram example was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Matrices solution from the Marketing area of ConceptDraw Solution Park.

This example of UML class diagram models bank account system.
"A bank account is a financial account between a bank customer and a financial institution. A bank account can be a deposit account, a credit card, or any other type of account offered by a financial institution. The financial transactions which have occurred within a given period of time on a bank account are reported to the customer on a bank statement and the balance of the account at any point in time is the financial position of the customer with the institution. a fund that a customer has entrusted to a bank and from which the customer can make withdrawals." [Bank account. Wikipedia]
This bank account system UML class diagram example was created using the ConceptDraw PRO diagramming and vector drawing software extended with the ATM UML Diagrams solution from the Software Development area of ConceptDraw Solution Park.

This interactive voice response (IVR) diagram sample illustrates how ENUM call forwarding can be achieved. It was designed on the base of the Wikimedia Commons file: Call Forwarding with ENUM.jpg. [commons.wikimedia.org/ wiki/ File:Call_ Forwarding_ with_ ENUM.jpg]
"Telephone number mapping is a system of unifying the international telephone number system of the public switched telephone network with the Internet addressing and identification name spaces. Internationally, telephone numbers are systematically organized by the E.164 standard, while the Internet uses the Domain Name System (DNS) for linking domain names to IP addresses and other resource information. Telephone number mapping systems provide facilities to determine applicable Internet communications servers responsible for servicing a given telephone number using DNS queries.
The most prominent facility for telephone number mapping is the E.164 Number Mapping (ENUM) standard. It uses special DNS record types to translate a telephone number into a Uniform Resource Identifier (URI) or IP address that can be used in Internet communications." [Telephone number mapping. Wikipedia]
The IVR diagram example "Call Forwarding with ENUM" was designed using ConceptDraw PRO diagramming and vector drawing software extended with the Interactive Voice Response 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.

"An example scenario is presented to demonstrate how a common issue tracking system would work:
(1) A customer service technician receives a telephone call, email, or other communication from a customer about a problem. Some applications provide built-in messaging system and automatic error reporting from exception handling blocks.
(2) The technician verifies that the problem is real, and not just perceived. The technician will also ensure that enough information about the problem is obtained from the customer. This information generally includes the environment of the customer, when and how the issue occurs, and all other relevant circumstances.
(3) The technician creates the issue in the system, entering all relevant data, as provided by the customer.
(4) As work is done on that issue, the system is updated with new data by the technician. Any attempt at fixing the problem should be noted in the issue system. Ticket status most likely will be changed from open to pending.
(5) After the issue has been fully addressed, it is marked as resolved in the issue tracking system.
If the problem is not fully resolved, the ticket will be reopened once the technician receives new information from the customer. A Run Book Automation process that implements best practices for these workflows and increases IT personnel effectiveness is becoming very common." [Issue tracking system. Wikipedia]
The UML use case 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.

"Dimensions of service quality.
A customer's expectation of a particular service is determined by factors such as recommendations, personal needs and past experiences. The expected service and the perceived service sometimes may not be equal, thus leaving a gap. The service quality model or the ‘GAP model’ developed by a group of authors- Parasuraman, Zeithaml and Berry at Texas and North Carolina in 1985 , highlights the main requirements for delivering high service quality. It identifies five ‘gaps’ that cause unsuccessful delivery. Customers generally have a tendency to compare the service they 'experience' with the service they 'expect' . If the experience does not match the expectation , there arises a gap. Ten determinants that may influence the appearance of a gap were described by Parasuraman, Zeithaml and Berry. in the SERVQUAL model: reliability, responsiveness, competence, access, courtesy, communication, credibility, security, understanding the customer and tangibles.
Later, the determinants were reduced to five: tangibles; reliability; responsiveness; service assurance and empathy in the so called RATER model." [Service quality. Wikipedia]
The block diagram example "Gap model of service quality" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Block Diagrams solution from the area "What is a Diagram" of ConceptDraw Solution Park.