Overview
Introduction
This guide has been prepared with the aim of providing a generalized view of the life of the client in the company and the different processes that are involved. We are going to go through the complete cycle from when a client gets registered in the company.
The beggining
In order to talk about the life cycle of a client, the first thing we are going to see is how a client is generated. The moment a person accesses or becomes interested in any of the telecommunications products, products that can be consulted in MasCatalogue , within MasStack , and decides to make a contract, there are two possible channels to do this selling:
- Physical or face-to-face (stores)
- Not in person (Online)
Once the client uses either of the two options, a sale is generated, from which the life or life cycle of the client begins in the company. The sale process is described in Signup. All the information can be checked in Signups site
Post-sale
Once the sale or Signups is made, a unique identifier is generated to the customer. This unique identifier is called userId. We are going to see the different fields that a client has within our Api.
User
This object includes all the information related to the customer’s data, for example: address, bank account, mail … etc., as well as the different packages contracted in the sale.
-
Own information: can be accessed from Get user detail . In this object we will find everything related to customer data, from their address, identification document, email … It is accessed thanks to the userId
-
Information of the contracted packages: can be consulted in Get customer full tree This information can be accessible by email, identity document or subscription phone. This tree will return all accounts and subscriptions the client has contracted already along with their current status . We will see their structure below.
A first approach to how the hierarchy of our API is, with the different fields and how they relate to each other, can be seen in the following diagram. You can click on the squares to expand the differents sections.
Accounts
This object encompasses the different “contracts” made by the client. This contract or contracts is going to be a sum of different lines or services. Each contract will have a different account associated with its own accountId. All the different methods that we have in our MasStack
APIs can be consulted here Accounts
For example: a customer goes to the store and hires a package which is made up of: a fixed line, a mobile line and the internet. In this case we will have a contract with 3 different subscriptions.
- Fixed line
- mobile line
- Internet
Subscriptions
Each of the services contracted within a contract is what we call Subscription. Each of them may have different peculiarities. Everything related to this field can be consulted in Subscriptions
There are 4 types of services that you can have a subscription:
- Fixed Line
- Mobile
- Internet
- Television
In the following diagram we can see the different types of subscriptions that we can have:
The hierarchy
As we have seen in previous sections, all the fields are related to each other as can be seen in the diagram at the beginning of this page.
Bellow you can find a first approach on how these fields connect and which are the parameters needed when searching:
Now, we are going to see an overview of how the photo would look with all the fields integrated with each other and their method possibilities.
Next steps to this section can be seen in Signup’s site .