Selling upgrades is new to Pulse users. And this article explains how to do that.
...
To choose the product(s), you check the name of the product the customer names and click on the + sign that is on the left of that product. You will also see that the number increases from zero (ascending order) as you click on the + sign.
To remove the product(s), you click on the - sign and the number will decrease towards zero.
As you add/remove the products the “Total Energy available” will also change
When it’s positive it’s in green color. Positive means that the products will be consuming less energy than the system can produce.
...
It’s red when it’s negative. Negative means that the products will be consuming more energy than the system can produce.
When this happens, you get a warning to tell you that you have exceeded the energy limit but Pulse doesn’t stop you from proceeding (if the customer insists).
If you want to proceed with click on “Close”. And click on “Next” button.
...
| Info |
|---|
When you close the success message, you land to the customer detail page. And account status changes to ‘Pay upgrade down payment’ |
...
Upgrade Customer Endpoints.
On the backend, the web app is calling the data warehouse API for customer upgrade model check (to verify whether the customer is eligible for the upgrade or not).
https://data-api-dev.bboxx.co.uk/user/upgarde/customer/unique_customer_id
1. The API is taking unique_customer_id as argument from the customer table.
2. The front-end web app 4 checks to verify customer eligibility for the upgrade, (certain conditions on client status, payment status, credit expires, contract performance).
3. Another check CU status depends on the API data (from data warehouse), in “ngu-configuration” we have CRM, in CRM we have “upgrades” as Boolean if it is “false” then it should be checked manually if it is “true” then it is managed by API call.