Method, systems, and computer-readable storage media for real-time event management system for mobile devices
A computerized system and method of managing events surrounding the lifecycle of used and new mobile devices. The system provides a “360 view” that integrates a mobile device's service options, such as financing and device protection, as well as at the device level regarding potential hardware/software errors. This provides an end-to-end view of consumers, such as claims on device protection plans, repayment issues, utilization of upgrades and/or other information in a user's profile across multiple underlying systems during the device's lifecycle.
1. A computer-implemented method for operating one or more servers to manage lifecycles of mobile computing devices, the method comprising:
detecting, by the one or more servers, a triggering event regarding a mobile computing device of a customer;
responsive to detecting the triggering event, determining, by the one or more servers, a customer profile with (i) one or more service options available to the customer; and (ii) repayment issues of the customer and/or utilization of upgrades by the customer corresponding to the mobile computing device by integrating disparate data sources concerning the customer together using a plurality of APIs;
providing, by the one or more servers, data to a customer application executing on the mobile computing device that includes a user interface feature executing on the mobile computing device;
receiving, by the one or more servers, a service option request that requests one or more service options available to the customer based on one or more user-selections on the customer application; and
in response to receiving the service option request from the customer application, updating, by the one or more servers, the disparate data sources corresponding to the mobile computing device of the customer to reflect the one or more service options requested in the service option request.
2. The computer-implemented method of claim 1 , wherein the one or more servers detect the triggering event based on a communication from the customer application indicating detection of a hardware and/or software fault on the mobile computing device of the customer.
3. The computer-implemented method of claim 2 , wherein the one or more servers detect the triggering event based on a communication from the customer application indicating a battery malfunction on the mobile computing device of the customer.
4. The computer-implemented method of claim 1 , wherein the one or more servers detect the triggering event based on a communication from the customer application indicating selection from the customer application identifying a hardware and/or software fault of the mobile computing device of the customer.
5. The computer-implemented method of claim 1 , wherein the one or more servers detect the triggering event based on a communication from the customer application identifying a cracked screen on the mobile computing device of the customer.
6. The computer-implemented method of claim 1 , wherein the triggering event is initiated by the one or more servers, based on a designated time period left before a contract associated with the mobile computing device of the customer expires.
7. The computer-implemented method of claim 1 , wherein the customer profile includes financing options and device protection options available to the customer, wherein the financing options and device protection options are determined by integrating data from disparate data sources through a plurality of APIs.
8. The computer-implemented method of claim 1 , wherein the user interface feature includes a presentation of one or more of an upgrade option, a replacement option and/or a repair option based one or more service options available to the customer in the customer profile.
9. The computer-implemented method of claim 8 , wherein in response to receiving a service option request requesting a replacement option or an upgrade option from the user interface feature, further comprising tracking an outbound device sent to the customer based on an IMEI number of the outbound device.
10. The computer-implemented method of claim 9 , wherein in response to receiving a service option request requesting a replacement option or an upgrade option from the user interface feature, further comprising tracking an inbound device sent by the customer based on an IMEI number of the inbound device.
11. The computer-implemented method of claim 10 , wherein in response to the service option request requesting the replacement option or the upgrade option further comprising monitoring for the IMEI number of the outbound device to activate on a cellular network of a carrier associated with the customer.
12. The computer-implemented method of claim 11 , wherein in response to detecting the IMEI number of the outbound device being activated, further comprising transmitting a message to the carrier of the customer's cellular network to block the inbound device from the cellular network based on the IMEI number of the inbound device.
13. The computer-implemented method of claim 10 , further comprising grading the inbound device based, at least in part, on the triggering event.
14. The computer-implemented method of claim 13 , wherein the grading step includes determining a destination address for shipping the inbound device based on the triggering event.
15. The computer-implemented method of claim 10 , wherein the outbound device and the inbound device are tracked simultaneously.
16. The computer-implemented method of claim 15 , wherein the outbound device is sent to the customer responsive to receiving the service option request requesting a replacement option or an upgrade option from the user interface feature prior to receiving the inbound device.
17. A real-time event management system for mobile computing devices, the system comprising:
one or more servers configured to communicate via a plurality of APIs with a plurality of systems managing service options concerning mobile computing devices of a plurality of customers;
a mobile computing device of the mobile computing devices of the plurality of customers in data communication with the one or more servers, wherein the mobile device includes a computer program embedded in a computer readable medium comprising computer executable instructions for execution by a processor, the computer program comprising:
instructions to trigger gathering of potential service options available to the customer of the mobile device, including financing and device protection options available to the customer, wherein gathering of potential service options includes integrating, by the one or more servers, a plurality of disparate data sources using the plurality of APIs;
instructions to receive selection of one or more service options on the mobile computing device;
instructions to update a customer profile associated with the customer based on selection of the one or more service options on the mobile computing device; and
instructions to track an outbound device sent to the customer based on an IMEI number of the outbound device in response to receiving selection of the one or more service options.
18. The system of claim 17 , wherein in response to receiving selection of the one or more service options, further comprising instructions to track an inbound device sent by the customer based on an IMEI number of the inbound device, wherein the outbound device is sent to the customer prior to receipt of the inbound device.
19. A server to manage lifecycles of mobile computing devices, the server comprising:
a processor; and
non-transitory, computer-readable storage media comprising a plurality of instructions stored thereon that, in response to being executed, cause the processor to:
detect a triggering event regarding a mobile computing device of a customer;
determine, responsive to detecting the triggering event, a customer profile with one or more service options available to the customer corresponding to the mobile computing device by integrating disparate data sources concerning the customer together using a plurality of APIs;
provide data to a customer application executing on the mobile computing device that includes a user interface feature, wherein the user interface feature includes a presentation of one or more of an upgrade option, a replacement option and/or a repair option based one or more service options available to the customer in the customer profile;
receive a service option request that requests the replacement option or the upgrade option based on one or more user-selections on the mobile computing device;
in response to receiving the service option request from the customer application, update the disparate data sources corresponding to the mobile computing device of the customer to reflect the one or more service options requested in the service option request; and
track an outbound device sent to the customer based on an IMEI number of the outbound device responsive to receiving the service option request requesting the replacement option or the upgrade option.
20. The server of claim 19 , wherein in response to receiving the service option request requesting a replacement option or an upgrade option from the user interface feature, further comprising one or more instructions to track an inbound device sent by the customer based on an IMEI number of the inbound device.
21. The server of claim 20 , wherein in response to the service option request requesting the replacement option or the upgrade option further comprising one or more instructions to monitor for the IMEI number of the outbound device to activate on a cellular network of a carrier associated with the customer.
22. The server of claim 21 , wherein in response to detecting the IMEI number of the outbound device being activated, further comprising one or more instructions to generate a message to the carrier of the customer's cellular network to block the inbound device from the cellular network based on the IMEI number of the inbound device.
23. The server of claim 20 , further comprising one or more instructions to grade the inbound device based, at least in part, on the triggering event.
24. The server of claim 23 , wherein to grade the inbound device comprises determining a destination address for shipping the inbound device based on the triggering event.
25. The server of claim 20 , wherein the outbound device and the inbound device are tracked simultaneously.
26. The server of claim 25 , wherein the outbound device is sent to the customer responsive to receiving the service option request requesting the replacement option or the upgrade option prior to receiving the inbound device.
27. One or more non-transitory, computer-readable storage media comprising a plurality of instructions stored thereon that, in response to being executed, cause a computing device to:
detect a triggering event regarding a mobile computing device of a customer;
determine, responsive to detecting the triggering event, a customer profile with one or more service options available to the customer corresponding to the mobile computing device by integrating disparate data sources concerning the customer together using a plurality of APIs;
provide data to a customer application executing on the mobile computing device that includes a user interface feature, wherein the user interface feature includes a presentation of one or more of an upgrade option, a replacement option and/or a repair option based one or more service options available to the customer in the customer profile;
receive a service option request that requests the replacement option or the upgrade option based on one or more user-selections on the mobile computing device;
in response to receiving the service option request from the customer application, update the disparate data sources corresponding to the mobile computing device of the customer to reflect the one or more service options requested in the service option request; and
track an outbound device sent to the customer based on an IMEI number of the outbound device responsive to receiving the service option request requesting the replacement option or the upgrade option.
28. The one or more non-transitory, computer-readable storage media of claim 27 , wherein in response to receiving the service option request requesting a replacement option or an upgrade option from the user interface feature, further comprising one or more instructions to track an inbound device sent by the customer based on an IMEI number of the inbound device.
29. The one or more non-transitory, computer-readable storage media of claim 28 , wherein in response to the service option request requesting the replacement option or the upgrade option further comprising one or more instructions to monitor for the IMEI number of the outbound device to activate on a cellular network of a carrier associated with the customer.
30. The one or more non-transitory, computer-readable storage media of claim 29 , wherein in response to detecting the IMEI number of the outbound device being activated, further comprising one or more instructions to generate a message to the carrier of the customer's cellular network to block the inbound device from the cellular network based on the IMEI number of the inbound device.
31. The one or more non-transitory, computer-readable storage media of claim 30 , further comprising one or more instructions to grade the inbound device based, at least in part, on the triggering event.
32. The one or more non-transitory, computer-readable storage media of claim 31 , wherein to grade the inbound device comprises determining a destination address for shipping the inbound device based on the triggering event.
33. The one or more non-transitory, computer-readable storage media of claim 28 , wherein the outbound device and the inbound device are tracked simultaneously.
34. The one or more non-transitory, computer-readable storage media of claim 28 , wherein the outbound device is sent to the customer responsive to receiving the service option request requesting the replacement option or the upgrade option prior to receiving the inbound device.
35. The one or more non-transitory, computer-readable storage media of claim 27 , further comprising one or more instructions to determine repayment issues and utilization of upgrades by the customer by integrating data from disparate data sources through a plurality of APIs.