FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR MANAGING AN ORDER SUBMISSION WORKFLOW FOR A PRODUCT ORDER”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR MANAGING AN ORDER SUBMISSION WORKFLOW FOR A PRODUCT ORDER
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to Customer Relationship Management (CRM) systems. More particularly, embodiments of the present disclosure relate to managing an order submission workflow for a product order.
BACKGROUND OF THE DISCLOSURE
[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] Customer relationship management (CRM) is the combination of technologies, practices, and strategies that companies use to manage and analyse customer/client and/or lead interactions and data throughout the customer life cycle. The objective of CRM is to improve customer service relationships and assist in customer retention and drive sales growth. CRM systems compile customer data across different channels, or points of contact, between the customer and the company, which could include the company's website, telephone, live chat, mail, marketing materials, social networks and like others. CRM systems can give customer-facing staff member’s detailed information on customers' personal information, order history, preferences, and concerns.
[0004] An order is an entity that is created in a database and helps in tracking the progress of an operation, such as new customer onboarding, modifications in customer profile etc., through milestones. Orders can be categorized differently depending on their characteristics. At present, many types of orders exist at granular level based on various order characteristics. Accordingly, it may be said that order refers to an activity or task performed on the CRM portal. Order includes, such as but not limited to, ‘New Customer Onboarding’ order, ‘Modification in Customer Details/Profile’ order, ‘Modification of

Customer Services’ order, ‘Porting of Customer Services’ order, ‘Mobility of Customer’ and/or the like. Each order is a scenario with a valid scenario identifier (scenario ID) mapped to it. Milestone stages may vary from one scenario to another scenario. Each order is defined by a number of milestones, which are required to be undertaken/processed in a specified format termed ‘Workflow.’ A milestone is an entity that is created in a database and helps in tracking the progress of an order. A milestone can be referred to as a step in the workflow of performing any order. The milestones may embody, such as but not limited to, Know Your Customer (KYC) milestone, ‘Customer Approval’ milestone, ‘Customer Verification’ milestone, ‘Tele-verification’ milestone, and/or ‘Installation’ milestone. Furthermore, one or more of the aforementioned milestones are followed in a specific manner (termed ‘workflow’) to complete execution of an order. In an exemplary embodiment, for execution of ‘New Customer Onboarding’ order, the workflow is defined to perform each of the ‘KYC’ milestone, ‘Customer Approval’ milestone, ‘Customer Verification’ milestone, ‘Tele-verification’ milestone, and the ‘Installation’ milestone, in the specified sequence. Notably, the execution of ‘New Customer Onboarding’ order may include other milestones as well, and the concepts of the present disclosure should not be limited to only the aforementioned milestones. In light of the aforementioned, it is understood that ‘KYC’ milestone is an important milestone, particularly, for execution of ‘New Customer Onboarding’ order.
[0005] When it comes to dedupe daily key validation, CRM reviews any constraints or limitations that may affect order fulfilment, such as regulatory requirements, or logistical challenges. Order feasibility check ensures that the order can be completed while adhering to these constraints. Few examples of such constraints are maximum number of allowed connections per day, maximum number of allowed connections per customer per circle.
[0006] A CRM system may define a number of rules for conforming to such constraints, for example, the CRM system may define rules for restricting the total number of connections that can be given to a customer, up to the maximum allowed number of connections. Here, ‘rules’ may be referred to as the process of allowing/restricting the execution of an order.
[0007] In order to perform such rules of deduplication of customer details during execution of an order, for example, a ‘New Customer Onboarding’ order, the CRM system

is enabled to allow a new customer onboarding order to proceed only if the count of the number of retrieved entries is below a threshold value; and reject the ‘New Customer Onboarding’ order to proceed further in case the count of the number of retrieved entries is above the threshold value. However, such order submission (i.e., the order submission for new customer onboarding), and the workflow for processing the order submission and milestone achieving workflow process is rigidly defined and no customization or configuration is possible as per operation need and any modification or addition is not easily feasible. Further, for adding features, there is requirement of system downtime and coding. This may be complex, time consuming and not efficient way to manage the CRM system.
[0008] Thus, there exists an imperative need in the art to provide a solution for managing an order submission workflow for a product order, which the present disclosure aims to address.
SUMMARY OF THE DISCLOSURE
[0009] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0010] An aspect of the present disclosure may relate to a method for managing an order submission workflow for a product order. The method comprises receiving, by a transceiver unit at a customer engagement system, an order submission request for the product order. Further, the method comprises validating, by a validation unit at the customer engagement system, the order submission request. Further, the method comprises performing, by a processing unit, at the customer engagement system, a duplicate detection check for the order submission request. Further, the method comprises performing, by the processing unit at the customer engagement system, a parameter check for the order submission request. Further, the method comprises creating, by the processing unit at the customer engagement system, the order associated with the order submission request, in a database. Further, the method comprises enriching, by the processing unit at the customer engagement system, the order with one or more attributes. Further, the method comprises

transmitting, by the transceiver unit, a notification, from the customer engagement system to a data server, for the order submission for the product.
[0011] In an exemplary aspect of the present disclosure, the duplicate detection check is performed if the order submission request is for a mobility product.
[0012] In an exemplary aspect of the present disclosure, prior to performing the duplicate detection check for the order, the validation unit determines one of an order acceptance state and an order rejection state, based on the validation of the order submission request.
[0013] In an exemplary aspect of the present disclosure, the duplicate detection check for the order submission request is performed in an event the order acceptance state is determined based on the validation of the order submission request.
[0014] In an exemplary aspect of the present disclosure, the order acceptance state is determined based on validating the order submission request for presence of one or more parameters in the order submission request.
[0015] In an exemplary aspect of the present disclosure, the order submission request comprises at least the one or more parameters, wherein the one or more parameters comprises at least a customer name, a customer proof of identity (PoI), a customer proof of address (PoA) and a product identification (ID).
[0016] In an exemplary aspect of the present disclosure, the duplicate detection check comprises identifying one of a presence and an absence of one or more orders in the database with a duplicate customer PoI and a duplicate customer PoA.
[0017] In an exemplary aspect of the present disclosure, the method further comprises accepting the order submission request based on the absence of the one or more orders in the database with a duplicate customer PoI and a duplicate customer PoA.
[0018] In an exemplary aspect of the present disclosure, the parameter check is performed if the order submission request is accepted.

[0019] In an exemplary aspect of the present disclosure, the parameter check is performed if the order submission request comprises Service Identification (ID) parameter in the one or more parameters of the order submission request.
[0020] In an exemplary aspect of the present disclosure, the parameter check comprises determining if the parameter is unique by comparing the Service ID parameter with the one or more orders in the database.
[0021] In an exemplary aspect of the present disclosure, the Service ID parameter is associated with the Product ID parameter from the one or more parameters in the order submission request.
[0022] In an exemplary aspect of the present disclosure, the one or more attributes for enriching the order, are based on at least a customer type, a communication circle and a product type.
[0023] In an exemplary aspect of the present disclosure, based on the order creation in the database, a notification is transmitted, by the transceiver unit, from the customer engagement system to the customer, for the order submission request.
[0024] Another aspect of the present disclosure may relate to a system for managing an order submission workflow for a product order. The customer engagement system comprises a transceiver unit configured to receive an order submission request for the product order. Further, the customer engagement system comprises a validation unit configured to validate the order submission request. Further, the customer engagement system comprises a processing unit, configured to perform a duplicate detection check for the order submission request. Further, the processing unit is configured to perform a parameter check for the order submission request. Further, the processing unit is configured to create the order associated with the order submission request in a database. Further, the processing unit is configured to enrich the order with one or more attributes. Further, the transceiver unit is configured to transmit a notification from the customer engagement system to a data server, for the order submission for the product.

[0025] Yet another aspect of the present disclosure may relate to a non-transitory computer
readable storage medium storing instructions for managing an order submission workflow
for a product order. The instructions include executable code which, when executed by one
or more units of a customer engagement system, causes a transceiver unit of the customer
5 engagement system to receive an order submission request for the product order. Further,
the executable code when executed, causes a validation unit of the customer engagement system to validate the order submission request. Further, the executable code when executed, causes a processing unit of the customer engagement system to: (1) perform a duplicate detection check for the order submission request; (2) perform a parameter check
10 for the order submission request; (3) create the order associated with the order submission
request in a database; and (4) enrich the order with one or more attributes. Further, the executable code when executed, causes the transceiver unit of the customer engagement system to transmit a notification from the customer engagement system to a data server, for the order submission for the product.
15
[0026] Yet another aspect of the present disclosure may relate to a user equipment (UE). The UE comprises a memory unit. Further, the UE comprises a processor unit. The processor unit is configured to transmit an order submission request for a product order, to a customer engagement system. Further, the processor unit is configured to receive, a
20 notification for the order submission request, from the customer engagement system. The
notification is generated by the customer engagement system, where the customer engagement system comprises a transceiver unit configured to receive the order submission request for the product order. Further, the customer engagement system comprises a validation unit configured to validate the order submission request. Further, the customer
25 engagement system comprises a processing unit, configured to perform a duplicate
detection check for the order submission request. Further, the processing unit is configured to perform a parameter check for the order submission request. Further, the processing unit is configured to create the order associated with the order submission request in a database. Further, the processing unit is configured to enrich the order with one or more attributes.
30 Further, the transceiver unit is configured to transmit a notification from the customer
engagement system to a data server, for the order submission for the product.
OBJECTS OF THE INVENTION
7

[0027] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0028] It is an object of the present disclosure to provide a system and a method for
5 processing order submission in Customer Relationship Management (CRM) system.
[0029] It is another object of the present invention to provide a system and method for customized and configurable workflow and/or sub workflow in plug and play manner as per operation needs. 10
DESCRIPTION OF THE DRAWINGS
[0030] The accompanying drawings, which are incorporated herein, and
constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed
15 methods and systems in which like reference numerals refer to the same parts throughout
the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated
20 herein to highlight the advantages of the disclosure. It will be appreciated by those skilled
in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[0031] Fig. 1 illustrates an exemplary block diagram of a computing device upon which
25 the features of the present disclosure may be implemented in accordance with exemplary
implementation of the present disclosure.
[0032] Fig. 2 illustrates an exemplary block diagram of a system for managing an order
submission workflow for a product order, in accordance with exemplary implementations
30 of the present disclosure.
[0033] Fig. 3 illustrates a method flow diagram for managing an order submission workflow for a product order in accordance with exemplary implementations of the present disclosure.
8

[0034] Fig. 4 shows an exemplary screenshot of an exemplary user interface [400] for viewing information for managing an order submission workflow for a product order, in accordance with exemplary implementations of the present disclosure. 5
[0035] Fig. 5 illustrates an exemplary implementation environment [500] for managing an order submission workflow for a product order, in accordance with exemplary implementations of the present disclosure.
10 [0036] The foregoing shall be more apparent from the following more detailed description
of the disclosure.
DETAILED DESCRIPTION
15 [0037] In the following description, for the purposes of explanation, various specific
details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An
20 individual feature may not address any of the problems discussed above or might address
only some of the problems discussed above.
[0038] The ensuing description provides exemplary embodiments only, and is not
intended to limit the scope, applicability, or configuration of the disclosure. Rather, the
25 ensuing description of the exemplary embodiments will provide those skilled in the art with
an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
30 [0039] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
9

[0040] Also, it is noted that individual embodiments may be described as a process which
is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a
block diagram. Although a flowchart may describe the operations as a sequential process,
5 many of the operations may be performed in parallel or concurrently. In addition, the order
of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
[0041] The word “exemplary” and/or “demonstrative” is used herein to mean serving as
10 an example, instance, or illustration. For the avoidance of doubt, the subject matter
disclosed herein is not limited by such examples. In addition, any aspect or design described
herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as
preferred or advantageous over other aspects or designs, nor is it meant to preclude
equivalent exemplary structures and techniques known to those of ordinary skill in the art.
15 Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar
words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word— without precluding any additional or other elements.
20 [0042] As used herein, a “processing unit” or “processor” or “operating processor”
includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal
25 Processing) DSP core, a controller, a microcontroller, Application Specific Integrated
Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
30
[0043] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of
10

implementing the features of the present disclosure. The user equipment/device may
include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose
computer, desktop, personal digital assistant, tablet computer, wearable device or any other
computing device which is capable of implementing one or more features of the present
5 disclosure. Also, the user device may contain at least one input means configured to receive
an input from unit(s) which are required to implement one or more features of the present disclosure.
[0044] As used herein, “storage unit” or “memory unit” refers to a machine or computer-
10 readable medium including any mechanism for storing information in a form readable by
a computer or similar machine. For example, a computer-readable medium includes read¬
only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media,
optical storage media, flash memory devices or other types of machine-accessible storage
media. The storage unit stores at least the data that may be required by one or more units
15 of the system to perform their respective functions.
[0045] All modules, units, components used herein, unless explicitly excluded herein, may
be software modules or hardware processors, the processors being a general-purpose
processor, a special purpose processor, a conventional processor, a digital signal processor
20 (DSP), a plurality of microprocessors, one or more microprocessors in association with a
DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0046] As used herein the transceiver unit include at least one receiver and at least one
25 transmitter configured respectively for receiving and transmitting data, signals, information
or a combination thereof between units/components within the system and/or connected with the system.
[0047] As used herein, an “order” refers to an entity that is created in a database and helps
30 in tracking the progress of an operation, such as new customer onboarding, modifications
in customer profile etc., through milestones. Order includes, such as but not limited to, ‘New Customer Onboarding’ order, ‘Modification in Customer Details/Profile’ order, ‘Modification of Customer Services’ order, ‘Porting of Customer Services’ order, ‘Mobility of Customer’ and/or the like.
11

[0048] As used herein, a “milestone” refers to an entity that is created in a database and
helps in tracking the progress of an order. A milestone can be referred to as a step in the
workflow of performing any order. The milestones may embody, such as but not limited
5 to, Know Your Customer (KYC) milestone, ‘Customer Approval’ milestone, ‘Customer
Verification’ milestone, ‘Tele-verification’ milestone, and/or ‘Installation’ milestone.
[0049] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented
10 interchangeably. While specific embodiments may disclose a particular functionality of
these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve
15 the intended functionality described herein, are considered to be encompassed within the
scope of the present disclosure.
[0050] As discussed in the background section, the current known solutions have several shortcomings. The order submission and the workflow for processing the order submission
20 and milestone achieving workflow process is rigidly defined and no customization or
configuration is possible as per operation need and any modification or addition is not easily feasible. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing method and system of managing an order submission workflow for a product order. According to the present disclosure, an
25 order is validated for some custom checks. Further, a dedupe daily key check is performed,
i.e., it is checked whether more than specified number of orders are placed with matching proof of address (POA) and proof of identity (POI). If the PoI and PoA match, then the order is rejected. Further, it is checked whether order exists with same service identity (service ID). If an order exists with same service ID, then the order is rejected. Further, if
30 the PoI and PoA do not match and no order exists with same service ID, then, the order is
created in a database, and a notification is triggered to customer that order has been submitted. Also, in an inward stage, the order is validated against mandatory parameters, the order approval and milestone flow are added to the order. Further, the database is notified regarding the customer creation.
12

[0051] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
5 [0052] Fig. 1 illustrates an exemplary block diagram of a computing device [100] upon
which the features of the present disclosure may be implemented in accordance with
exemplary implementation of the present disclosure. In an implementation, the computing
device [100] may implement a method for managing an order submission workflow for a
product order utilising the system as disclosed in the present disclosure. In another
10 implementation, the computing device [100] itself implements the method for managing an
order submission workflow for a product order using one or more units configured within the computing device [100], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
15 [0053] The computing device [100] may include a bus [102] or other communication
mechanism for communicating information, and a hardware processor [104] coupled with bus [102] for processing information. The hardware processor [104] may be, for example, a general-purpose microprocessor. The computing device [100] may also include a main memory [106], such as a random-access memory (RAM), or other dynamic storage device,
20 coupled to the bus [102] for storing information and instructions to be executed by the
processor [104]. The main memory [106] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [104]. Such instructions, when stored in non-transitory storage media accessible to the processor [104], render the computing device [100] into a special-purpose machine
25 that is customized to perform the operations specified in the instructions. The computing
device [100] further includes a read only memory (ROM) [108] or other static storage device coupled to the bus [102] for storing static information and instructions for the processor [104].
30 [0054] A storage device [110], such as a magnetic disk, optical disk, or solid-state drive
is provided and coupled to the bus [102] for storing information and instructions. The computing device [100] may be coupled via the bus [102] to a display [112], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user.
13

An input device [114], including alphanumeric and other keys, touch screen input means,
etc. may be coupled to the bus [102] for communicating information and command
selections to the processor [104]. Another type of user input device may be a cursor
controller [116], such as a mouse, a trackball, or cursor direction keys, for communicating
5 direction information and command selections to the processor [104], and for controlling
cursor movement on the display [112]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
10 [0055] The computing device [100] may implement the techniques described herein using
customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [100] causes or programs the computing device [100] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [100] in response to the processor
15 [104] executing one or more sequences of one or more instructions contained in the main
memory [106]. Such instructions may be read into the main memory [106] from another storage medium, such as the storage device [110]. Execution of the sequences of instructions contained in the main memory [106] causes the processor [104] to perform the process steps described herein. In alternative implementations of the present disclosure,
20 hard-wired circuitry may be used in place of or in combination with software instructions.
[0056] The computing device [100] also may include a communication interface [118] coupled to the bus [102]. The communication interface [118] provides a two-way data communication coupling to a network link [120] that is connected to a local network [122].
25 For example, the communication interface [118] may be an integrated services digital
network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface [118] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be
30 implemented. In any such implementation, the communication interface [118] sends and
receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
14

[0057] The computing device [100] can send messages and receive data, including
program code, through the network(s), the network link [120] and the communication
interface [118]. In the Internet example, a server [130] might transmit a requested code for
an application program through the Internet [128], the ISP [126], the local network [122],
5 the host [124], and the communication interface [118]. The received code may be executed
by the processor [104] as it is received, and/or stored in the storage device [110], or other non-volatile storage for later execution.
[0058] Referring to Fig. 2, an exemplary block diagram of a customer engagement system
10 [200] for managing an order submission workflow for a product order, is shown, in
accordance with the exemplary implementations of the present disclosure. The customer
engagement system [200] comprises at least one transceiver unit [202], at least one
validation unit [204], and at least one processing unit [206]. Also, all of the components/
units of the customer engagement system [200] are assumed to be connected to each other
15 unless otherwise indicated below. Also, in Fig. 2 only a few units are shown, however, the
customer engagement system [200] may comprise multiple such units or the customer
engagement system [200] may comprise any such numbers of said units, as required to
implement the features of the present disclosure. Further, in an implementation, the
customer engagement system [200] may be in communication with a user device (may also
20 be referred herein as a user equipment or a UE) to implement the features of the present
disclosure. In yet another implementation, the customer engagement system [200] may
reside in a server/ network entity.
[0059] The customer engagement system [200] is configured for managing an order
25 submission workflow for a product order, with the help of the interconnection between the
components/units of the customer engagement system [200].
[0060] The transceiver unit [202] is configured to receive an order submission request for
the product order. Here, a request related to order submission is received. For example, a
30 user (i.e., a customer) wants to buy a product, the user may submit a request for placing an
order of the product. Also, the product may be any product, such as, but not limited to, a mobility product (i.e., devices and equipment to aid individuals with limitations in moving around, for example, wheelchairs, walkers, mobility scooters, etc.), a fixed wireless access technology related product, etc. So, when a user places the request for placing an order for
15

the product, the request, i.e., the order submission request is received at the transceiver unit
[202] of the customer engagement system [200]. In an implementation, the order
submission request comprises at least one or more parameters, wherein the one or more
parameters comprises at least a customer name, a customer proof of identity (PoI), a
5 customer proof of address (PoA) and a product identification (ID). Since the user/customer
may place the order submission request using a digital platform, such as, but not limited to, a web portal, a website, a mobile application, etc., the customer may first login on the digital platform where the customer’s information may be saved. At the time of login, the customer may have provided a proof of identity (PoI) of the customer, and a proof of
10 address (PoA) of the customer, these details may be fetched from the customer details saved
during customer signing up at the digital platform. Alternatively, irrespective of the customer details saved with the digital platform or not, the customer while placing the order submission request may provide these customer details, i.e., the PoI and the PoA. Consequently, these customer details may be associated with the order submission request
15 as the one or more parameters.
[0061] The validation unit [204] is configured to validate the order submission request. In an implementation, the validation unit [204], to validate the order submission request, determines one of an order acceptance state and an order rejection state, based on the
20 validation of the order submission request. Also, in an implementation, the order
acceptance state is determined based on validating the order submission request for presence of one or more parameters in the order submission request. Here, the validation unit [204] checks whether the one or more parameters, i.e., the customer details comprising the PoI and PoA are associated with the order submission request or not. If the customer
25 details are present with the order submission request, the order may be accepted, i.e., the
validation unit [204] may determine the order acceptance state for the order submission request. Else, if the customer details are not present with the order submission request, the order may be rejected, i.e., the validation unit [204] may determine the order rejection state for the order submission request.
30
[0062] Further, the processing unit [206] is configured to perform a duplicate detection check for the order submission request. There may be some products for which the product seller does not allow a single user/customer to buy multiple copies of the product or does not allow a single user/customer to buy a number of copies of the product above a pre-
16

defined threshold. For example, the product seller does not allow a single user to buy more
than 1 copy of Product X, or the product seller does not allow a single user to buy more
than 4 copies of Product Y. For this, a duplicate detection check is performed. In an
implementation, the duplicate detection check is performed if the order submission request
5 is for a mobility product (i.e., devices and equipment to aid individuals with limitations in
moving around, for example, wheelchairs, walkers, mobility scooters, etc.), however the present disclosure is not limited thereto. In an implementation, prior to performing the duplicate detection check for the order by the processing unit [206], the validation unit [204] determines one of an order acceptance state and an order rejection state, based on the
10 validation of the order submission request. Also, for the duplicate detection check, the
product ID parameter in the order submission request may also be used. Each product may be tagged and identified with a product ID, and the product ID may be used to conclude whether multiple copies of this product are allowed to be bought by a single user or not. The product ID may be used to check the threshold number of copies of the product that a
15 single user can buy. Further, checking the product ID and the threshold number of copies
of the product that a single user can buy, the customer details may be used to determine whether the customer has already ordered the product a pre-defined threshold number of times or not.
20 [0063] In an implementation, the duplicate detection check comprises, identifying one
of a presence and an absence of one or more orders in the database with a duplicate customer PoI and a duplicate customer PoA. Say for example, when a user places an order submission request, the order submission request comprises the customer detail, i.e., PoI and PoA, and the product ID for the product for which the user has placed the order
25 submission request. Now, in the database comprising customer details, if the same product
ID is tagged as ordered with the same customer details, then the duplicate detection check may identify a presence of one or more orders (that is, the order made by the user for the product) in the database with a duplicate customer PoI and a duplicate customer PoA. However, if the product ID for which the user has placed the order submission request, is
30 not found as ordered by the same PoA and PoI of the customer, then the customer may be
allowed to order the product. Thus, in an implementation, the order submission request is accepted based on the absence of the one or more orders in the database with a duplicate customer PoI and a duplicate customer PoA.
17

[0064] In an implementation, the duplicate detection check for the order submission
request is performed by the processing unit [206], in an event the order acceptance state is
determined based on the validation of the order submission request. For example, it is
5 determined that a customer has not bought a pre-defined threshold number of copies of the
product, that is, the order acceptance state is determined, then the duplicate detection check may be performed as explained above.
[0065] Further, the processing unit [206] is configured to perform a parameter check for
10 the order submission request. In an implementation, the parameter check is performed by
the processing unit [206], if the order submission request is accepted. In an implementation, the parameter check is performed if the order submission request comprises a service identification (ID) parameter in the one or more parameters in the order submission request. In an implementation, the parameter check comprises determining if the Service ID
15 parameter is unique by comparing the Service ID parameter with the one or more orders in
the database. In an implementation, the Service ID parameter is associated with the Product ID parameter from the one or more parameters in the order submission request. For example, there is a service associated with the product that a user chooses to buy. For example, a user chooses to buy a router from an internet service provider. Thus, the service
20 of installation of the router may also be attached with the router. So, if in the order
submission request, for example, for buying the router, a service ID is present, and if the order submission request is accepted for the user, then the parameter check may be performed. In the given example performing the parameter check encompasses determining if the service ID present in the order submission request is unique by comparing the service
25 ID (i.e., the Service ID) parameter with the one or more orders in the database.
[0066] Further, the processing unit [206] is configured to create the order associated with
the order submission request in a database. Here, if the duplicate detection check and/or
the parameter check are passed and the order submission request is accepted by the system,
30 then the same may be reflected in the system as well and the order corresponding to the
accepted order submission request is created. Thus, for this purpose, the database may be updated with an order creation. For example, an order ID may be assigned to the order created after acceptance of the order submission request and saved in the database. In an implementation, based on the order creation in the database, a notification is transmitted,
18

by the transceiver unit [202], from the customer engagement system [200] to the customer, for the order submission request. Continuing with the above example, the order ID may be transmitted to the customer in the notification.
5 [0067] Further, the processing unit [206] is configured to enrich the order with one or
more attributes. In an implementation, the one or more attributes for enriching the order,
are based on at least a customer type, a communication circle and a product type. Here, in
the database, after the order is created, the same may be enriched with the one or more
attributes related to the order created. For example, the customer type attribute may be one
10 of an individual customer, a small company, a large company, etc., the product type may
be one of a dish antenna, a set top box, a router, etc. Therefore, such details are added to the order that is created for the enrichment of said order.
[0068] Further, the transceiver unit [202] is further configured to transmit a notification
15 from the customer engagement system [200] to a data server, for the order submission for
the product. Also, a data server may be separately maintained for all customers. Here, the
data server may be any computing device that may comprise a processor and a memory
associated with it. The data server may be connected to the customer engagement system
[200] for receiving the notification related to the order submission. Also, the memory
20 associated with this data server may comprise a database that contains information of
customers, that is, this data server may contain all details related to all customers, for
example, customer ID, customer details, products bought by each customer, etc. This may
be used to track further, if a particular customer has bought a product in the past or not.
Also, these details may also be used for other purposes, such as, to assess when a particular
25 customer last bought a particular product, etc.
[0069] Referring to Fig. 3, an exemplary flow diagram of a method [300] for managing
an order submission workflow for a product order, in accordance with exemplary
implementations of the present disclosure is shown. In an implementation the method [300]
30 is performed by the customer engagement system [200]. Also, as shown in Fig. 3, the
method [300] starts at step [302].
19

[0070] At step 304, the method comprises receiving, by a transceiver unit [202] at a
customer engagement system [200], an order submission request for the product order.
Here, a request related to order submission is received. For example, a user (i.e., a
customer) wants to buy a product, the user may submit a request for placing an order of the
5 product. Also, the product may be any product, such as, but not limited to, a mobility
product, a fixed wireless access technology related product, etc. So, when a user places the request for placing an order for the product, the request, i.e., the order submission request is received at the transceiver unit [202] of the customer engagement system [200]. In an implementation, the order submission request comprises at least one or more parameters,
10 wherein the one or more parameters comprises at least a customer name, a customer proof
of identity (PoI), a customer proof of address (PoA) and a product identification (ID). Since the user/customer may place the order submission request using a digital platform, such as, but not limited to, a web portal, a website, a mobile application, etc., the customer may first login on the digital platform where the customer’s information may be saved. At the time
15 of login, the customer may have provided a proof of identity (PoI) of the customer, and a
proof of address (PoA) of the customer, these details may be fetched from the customer details saved during customer signing up at the digital platform. Alternatively, irrespective of the customer details saved with the digital platform or not, the customer while placing the order submission request may provide these customer details, i.e., the PoI and the PoA.
20 Consequently, these customer details may be associated with the order submission request
as the one or more parameters.
[0071] At step 306, the method comprises validating, by a validation unit [204] at the customer engagement system [200], the order submission request. In an implementation,
25 the validation unit [204], to validate the order submission request, may determine one of
an order acceptance state and an order rejection state, based on the validation of the order submission request. Also, in an implementation, the order acceptance state is determined based on validating the order submission request for presence of one or more parameters in the order submission request. Here, the validation unit [204] checks whether the one or
30 more parameters, i.e., the customer details comprising the PoI and PoA are associated with
the order submission request or not. If the customer details are present with the order submission request, the order may be accepted, i.e., the validation unit [204] may determine the order acceptance state for the order submission request. Else, if the customer details are
20

not present with the order submission request, the order may be rejected, i.e., the validation unit [204] may determine the order rejection state for the order submission request.
[0072] At step 308, the method comprises performing, by a processing unit [206], at the
5 customer engagement system [200], a duplicate detection check for the order submission
request. There may be some products for which the product seller does not allow a single user/customer to buy multiple copies of the product or does not allow a single user/customer to buy a number of copies of the product above a pre-defined threshold. For example, the product seller does not allow a single user to buy more than 1 copy of Product
10 X, or the product seller does not allow a single user to buy more than 4 copies of Product
Y. For this, a duplicate detection check is performed. In an implementation, the duplicate detection check is performed if the order submission request is for a mobility product, however the present disclosure is not limited thereto. In an implementation, prior to performing the duplicate detection check for the order by the processing unit [206], the
15 validation unit [204] may determine one of an order acceptance state and an order rejection
state, based on the validation of the order submission request. Also, for the duplicate detection check, the product ID parameter in the order submission request may also be used. Each product may be tagged and identified with a product ID, and the product ID may be used to conclude whether multiple copies of this product are allowed to be bought
20 by a single user or not. The product ID may be used to check the threshold number of copies
of the product that a single user can buy. Further, checking the product ID and the threshold number of copies of the product that a single user can buy, the customer details may be used to determine whether the customer has already ordered the product a pre-defined threshold number of times or not.
25
[0073] In an implementation, the duplicate detection check comprises, identifying one of a presence and an absence of one or more orders in the database with a duplicate customer PoI and a duplicate customer PoA. Say for example, when a user places an order submission request, the order submission request comprises the customer detail, i.e., PoI
30 and PoA, and the product ID for the product for which the user has placed the order
submission request. Now, in the database comprising customer details, if the same product ID is tagged as ordered with the same customer details, then the duplicate detection check may identify a presence of one or more orders (that is, the order made by the user for the product) in the database with a duplicate customer PoI and a duplicate customer PoA.
21

However, if the product ID for which the user has placed the order submission request, is
not found as ordered by the same PoA and PoI of the customer, then the customer may be
allowed to order the product. Thus, in an implementation, the order submission request is
accepted based on the absence of the one or more orders in the database with a duplicate
5 customer PoI and a duplicate customer PoA.
[0074] In an implementation, the duplicate detection check for the order submission
request is performed by the processing unit [206], in an event the order acceptance state is
determined based on the validation of the order submission request. For example, it is
10 determined that a customer has not bought a pre-defined threshold number of copies of the
product, that is, the order acceptance state is determined, then the duplicate detection check may be performed as explained above.
[0075] At step 310, the method comprises performing, by the processing unit [206] at the
15 customer engagement system [200], a parameter check for the order submission request. In
an implementation, the parameter check is performed by the processing unit [206], if the order submission request is accepted. In an implementation, the parameter check is performed if the order submission request comprises a service identification (ID) parameter in the one or more parameters in the order submission request. In an implementation, the
20 parameter check comprises determining if the Service ID parameter is unique by comparing
the Service ID parameter with the one or more orders in the database. In an implementation, the Service ID parameter is associated with the Product ID parameter from the one or more parameters in the order submission request. For example, there is a service associated with the product that a user chooses to buy. For example, a user chooses to buy a router from an
25 internet service provider. Thus, the service of installation of the router may also be attached
with the router. So, if in the order submission request, for example, for buying the router, a service ID is present, and if the order submission request is accepted for the user, then the parameter check may be performed. In the given example performing the parameter check encompasses determining if the service ID present in the order submission request is unique
30 by comparing the service ID (i.e., the Service ID) parameter with the one or more orders in
the database.
[0076] At step 312, the method comprises creating, by the processing unit [206] at the customer engagement system [200], the order associated with the order submission request,
22

in a database. Here, if the duplicate detection check and/or the parameter check are passed
and the order submission request is accepted by the system, then the same may be reflected
in the system as well and the order corresponding to the accepted order submission request
is created. Thus, for this purpose, the database may be updated with an order creation. For
5 example, an order ID may be assigned to the order created after acceptance of the order
submission request and saved in the database. In an implementation, based on the order
creation in the database, a notification is transmitted, by the transceiver unit [202], from
the customer engagement system [200] to the customer, for the order submission request.
Continuing with the above example, the order ID may be transmitted to the customer in the
10 notification.
[0077] At step 314, the method comprises enriching, by the processing unit [206] at the customer engagement system [200], the order with one or more attributes. In an implementation, the one or more attributes for enriching the order, are based on at least a
15 customer type, a communication circle and a product type. Here, in the database, after the
order is created, the same may be enriched with the one or more attributes related to the order created. For example, the customer type attribute may be one of an individual customer, a small company, a large company, etc., the product type may be one of a dish antenna, a set top box, a router, etc. Therefore, such details are added to the order that is
20 created for the enrichment of said order.
[0078] At step 316, the method comprises transmitting, by the transceiver unit [202], a notification, from the customer engagement system [200] to a data server, for the order submission for the product. Also, a data server may be separately maintained for all
25 customers. This data server may contain all details related to all customers, for example,
customer ID, customer details, products bought by each customer, etc. This may be used to track further, if a particular customer has bought a product in the past or not. Also, these details may also be used for other purposes, such as, to assess when a particular customer last bought a particular product, etc.
30
[0079] The method thereafter terminates at step [318].
[0080] Referring to FIG. 4, which shows an exemplary screenshot of an exemplary user interface [400] for viewing information for managing an order submission workflow for a
23

product order, in accordance with exemplary implementations of the present disclosure. As shown in Fig. 4, the information of the order ID XXXXX is shown. The customer type may be, for example, ‘retail’, customer category may be, for example, ‘individual’, etc. Also, the sub-milestone workflows can be handled via parameters such as, but not limited to, Sequence Number, Enabled and Disabled flags.
[0081] Referring to FIG. 5 which illustrates an exemplary implementation environment [500] for managing an order submission workflow for a product order, in accordance with exemplary implementations of the present disclosure. In an implementation, the implementation environment [500] comprises a plurality of components. For example, and by no way limiting the scope of the present subject matter, the implementation environment [500] comprises an Enterprise Product Catalogue (EPC) [502], a Fulfilment management system (FMS) [504], a subscription engine [514], a plurality of channels [506], a load balancer [508], a Customer Relationship Manager (CRM) server [510] comprising a plurality of micro-services, and a set of database [512]. The set of databases may include a database 1, database 2, and a database 3. The EPC [502] is a centralised data repository which drives Business Support System (BSS) telecom operations and some network nodes for e.g., 5G charging system, called Policy Control Function (PCF) etc.
[0082] At the centre, the CRM server [510] containing different micro services is shown, which cater to different Application Programming Interfaces (APIs). Each microservice serves a particular context, e.g., Customer Order Processing Micro service (COP_MS) deals with order-related APIs which performs, for example, submit order, query order, and modify order actions. Customer Information Service (CIS) instances deal with customer-related APIs which performs create, modify or deactivate customer. Lead-to-Order (L2O) instances deal with APIs that manage the lifecycle of leads and prospects. Operations and Maintenance (OAM) instance deals with the maintenance and operation of all the microservice instances and communicates with outer products related to alarms, Key Performance Indicators (KPIs) or other management, and health check-up information.
[0083] The channels [506] are configured to provide input data to the CRM server [510] through a load balancer [508]. In an embodiment, some examples of the channels [506] include but are not limited to a channel 1 [506A], a channel 2 [506B], a channel 3 [506C] and a CRM user interface (UI) [506D]. The channels [506] which are tightly coupled to the

CRM e.g. CRM User Interface (UI) [506D] communicate directly via the load balancer [508] while other systems which belong to different products communicate to the CRM server [510] using the FMS [504]. FMS is a middleware which links two different products and performs language translations or workflow management. For example, if one product understands Simple Object Access Protocol (SOAP) protocol while the other one understands RESTful services, the FMS [504] translate the messages between these 2 nodes and ensure seamless communication. The CRM server [510] is also connected with the FMS [504], SMP (Service Management Platform) [515], and Data Information Framework (DIF) [518] via https. The DIF [518] is a copy of the CRM [510], EPC, and Geographical Information System (GIS) which caches the business data and provides API for fast access. The SMP [515] deals with the installation processes at customer premises, handling repair mechanism and technician visit to network sites.
[0084] In an implementation, an admin user operates the CRM UI [506D] to trigger the CRUD (Create/ Read/ Update/ Delete) operation on the CRM server [510] via the load balancer [508] or FMS. According to the present disclosure, the CRM server [510] stores all order journey configurations cached during the start-up of micro services. Whenever any change, such as ‘update’, ‘delete’, ‘create’ etc., in order journey configuration is received from the CRM UI [506D], the CRM server [510] processes the same and modifies the stored data in cache. The workflow engine picks the updated configuration item whenever subsequent order submission request comes at the CRM server [510]. Based on the configuration list, the next milestone is triggered.
[0085] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for managing an order submission workflow for a product order. The instructions include executable code which, when executed by one or more units of a customer engagement system [200], causes a transceiver unit [202] of the customer engagement system [200] to receive an order submission request for the product order. Further, the executable code when executed, causes a validation unit [204] of the customer engagement system [200] to validate the order submission request. Further, the executable code when executed, causes a processing unit [206] of the customer engagement system [200] to: (1) perform a duplicate detection check for the order submission request; (2) perform a parameter check for the order submission request; (3) create the order associated with the order submission request in a database; and (4) enrich the order with one or more

attributes. Further, the executable code when executed, causes the transceiver unit [202] of the customer engagement system [200] to transmit a notification from the customer engagement system [200] to a data server, for the order submission for the product.
[0086] The present disclosure further discloses a user equipment (UE). The UE comprises a memory unit. Further, the UE comprises a processor unit. The processor unit is configured to transmit an order submission request for a product order, to a customer engagement system [200]. Further, the processor unit is configured to receive, a notification for the order submission request, from the customer engagement system [200]. The notification is generated by the customer engagement system [200], where the customer engagement system [200] comprises a transceiver unit [202] configured to receive the order submission request for the product order. Further, the customer engagement system [200] comprises a validation unit [204] configured to validate the order submission request. Further, the customer engagement system [200] comprises a processing unit [206], configured to perform a duplicate detection check for the order submission request. Further, the processing unit [206] is configured to perform a parameter check for the order submission request. Further, the processing unit [206] is configured to create the order associated with the order submission request in a database. Further, the processing unit [206] is configured to enrich the order with one or more attributes. Further, the transceiver unit [202] is configured to transmit a notification from the customer engagement system [200] to a data server, for the order submission for the product. In an implementation, the notification also comprises details of the enrichment of the order with one or more attributes.
[0087] As is evident from the above, the present disclosure provides a technically advanced solution for managing an order submission workflow for a product order. The present solution facilitates management of order submission workflow of any kind of products including mobility products, fixed wireless access technology-based products etc. This management procedure on different kinds of products can be handled in production with zero developmental efforts. Similarly, if it is needed to interchange sequence of various flows inside the workflow without change in business logic, same can also be handled without any code overhead or redundant software lifecycles.

[0088] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

We Claim:
1. A method for managing an order submission workflow for a product order, the
method comprising:
receiving, by a transceiver unit [202] at a customer engagement system [200], an
order submission request for the product order;
validating, by a validation unit [204] at the customer engagement system [200], the
order submission request;
performing, by a processing unit [206], at the customer engagement system [200], a
duplicate detection check for the order submission request;
performing, by the processing unit [206] at the customer engagement system [200],
a parameter check for the order submission request;
creating, by the processing unit [206] at the customer engagement system [200], the
order associated with the order submission request, in a database;
enriching, by the processing unit [206] at the customer engagement system [200], the
order with one or more attributes; and
transmitting, by the transceiver unit [202], a notification, from the customer
engagement system [200] to a data server, for the order submission for the product.
2. The method as claimed in claim 1, wherein the duplicate detection check is performed if the order submission request is for a mobility product.
3. The method as claimed in claim 2, wherein prior to performing the duplicate detection check for the order, the validation unit [204] determines one of an order acceptance state and an order rejection state, based on the validation of the order submission request.
4. The method as claimed in claim 3, wherein the duplicate detection check for the order submission request is performed in an event the order acceptance state is determined based on the validation of the order submission request.
5. The method as claimed in claim 3, wherein the order acceptance state is determined based on validating the order submission request for presence of one or more parameters in the order submission request.

6. The method as claimed in claim 1, wherein the order submission request comprises at least the one or more parameters, wherein the one or more parameters comprises at least a customer name, a customer proof of identity (PoI), a customer proof of address (PoA) and a product identification (ID).
7. The method as claimed in claim 1, wherein the duplicate detection check comprises identifying one of a presence and an absence of one or more orders in the database with a duplicate customer PoI and a duplicate customer PoA.
8. The method as claimed in claim 7, further comprising accepting the order submission request based on the absence of the one or more orders in the database with a duplicate customer PoI and a duplicate customer PoA.
9. The method as claimed in claim 8, wherein a parameter check is performed if the order submission request is accepted.
10. The method as claimed in claim 9, wherein the parameter check is performed if the
order submission request comprises Service Identification (ID) parameter in the one
or more parameters of the order submission request.
11. The method as claimed in claim 10, wherein the parameter check comprises determining if the parameter is unique by comparing the Service ID parameter with the one or more orders in the database.
12. The method as claimed in claim 10, wherein the Service ID parameter is associated with a Product ID parameter from the one or more parameters in the order submission request.
13. The method as claimed in claim 1, wherein the one or more attributes for enriching the order, are based on at least a customer type, a communication circle and a product type.

14. The method as claimed in claim 1, wherein based on the order creation in the database, a notification is transmitted, by the transceiver unit [202], from the customer engagement system [200] to the customer, for the order submission request.
15. A customer engagement system [200] for managing an order submission workflow for a product order, the customer engagement system [200] comprising:
a transceiver unit [202] configured to receive an order submission request for the
product order;
a validation unit [204] configured to validate the order submission request; and
a processing unit [206], configured to:
- perform a duplicate detection check for the order submission request,
- perform a parameter check for the order submission request,
- create the order associated with the order submission request in a database,
- enrich the order with one or more attributes, and
wherein the transceiver unit [202] is further configured to transmit a notification from the customer engagement system [200] to a data server, for the order submission for the product.
16. The customer engagement system [200] as claimed in claim 15, wherein the duplicate detection check is performed if the order submission request is for a mobility product.
17. The customer engagement system [200] as claimed in claim 16, wherein, prior to performing the duplicate detection check for the order by the processing unit [206], the validation unit [204] determines one of an order acceptance state and an order rejection state, based on the validation of the order submission request.
18. The customer engagement system [200] as claimed in claim 17, wherein the duplicate detection check for the order submission request is performed by the processing unit [206], in an event the order acceptance state is determined based on the validation of the order submission request.

19. The customer engagement system [200] as claimed in claim 17, wherein the order acceptance state is determined based on validating the order submission request for presence of one or more parameters in the order submission request.
20. The customer engagement system [200] as claimed in claim 15, wherein the order submission request comprises at least the one or more parameters, wherein the one or more parameters comprises at least a customer name, a customer proof of identity (PoI), a customer proof of address (PoA) and a product identification (ID).
21. The customer engagement system [200] as claimed in claim 15, wherein the duplicate detection check comprises, identifying one of a presence and an absence of one or more orders in the database with a duplicate customer PoI and a duplicate customer PoA.
22. The customer engagement system [200] as claimed in claim 21, wherein the order submission request is accepted based on the absence of the one or more orders in the database with a duplicate customer PoI and a duplicate customer PoA.
23. The customer engagement system [200] as claimed in claim 22, wherein the parameter check is performed by the processing unit [206], if the order submission request is accepted.
24. The customer engagement system [200] as claimed in claim 23, wherein the
parameter check is performed if the order submission request comprises a Service
Identification (ID) parameter in the one or more parameters in the order submission
request.
25. The customer engagement system [200] as claimed in claim 24, wherein the parameter check comprises determining if the Service ID parameter is unique by comparing the Service ID parameter with the one or more orders in the database.
26. The customer engagement system [200] as claimed in claim 24, wherein the Service ID parameter is associated with a Product ID parameter from the one or more parameters in the order submission request.

27. The customer engagement system [200] as claimed in claim 15, wherein the one or more attributes for enriching the order, are based on at least a customer type, a communication circle and a product type.
28. The customer engagement system [200] as claimed in claim 15, wherein based on the order creation in the database, a notification is transmitted, by the transceiver unit [202], from the customer engagement system [200] to the customer, for the order submission request.
29. A User Equipment (UE) comprising:
a memory unit; and
a processor unit, wherein the processor unit is configured to:
transmit an order submission request for a product order, to a customer
engagement system [200];
receive, a notification for the order submission request, from the customer
engagement system [200], wherein the notification is generated by the customer
engagement system [200] comprising:
a transceiver unit [202], configured to receive the order submission request for
the product order;
a validation unit [204], configured to validate the order submission request; and
a processing unit [206], configured to:
- perform, a duplicate detection check for the order submission request;
- perform, a parameter check for the order submission request;
- create, the order associated with the order submission request in a database;
- enrich, the order with one or more attributes; and wherein:
the transceiver unit [202], is further configured to transmit a notification from the customer engagement system [200] to a data server, for the order submission for the product.