Synchronized multi-channel communication enabling accessibility for collecting data
A method performed by a first network node that is in communication with a support node. The support node is configured to communicate with a first user node using a first communication channel of a logical communication session. The method includes receiving user account data associated with a user of the first user node, receiving, from the support node, a session request to initiate a second communication channel of the logical communication session, and configuring the second communication channel between the first network node and at least one of the first user node and a second user node, based on the session request and the user account data.
1 . A method performed by a first network node that is in communication with a support node, the support node being configured to communicate with a first user node using a first communication channel for a first communication session, the method comprising:
receiving user account data associated with a user of the first user node;
receiving, from the support node, a session request to initiate a second communication channel for a second communication session that bypasses the support node but that is logically joined to the first communication session to create a single logical communication session, the first communication channel being voiced-based, and the second communication channel being data-based, the support node being unable to view any communications transported via the second communication channel; and
configuring the second communication channel between the first network node and at least one of the first user node and a second user node, based on the session request and the user account data, the first communication session and the second communication session being synchronized to a predefined business process associated with the logical communication session where the first network node simultaneously sends and receives data from at least one of the first user node and second user node via the first communication channel or the second communication channel.
2 . The method of claim 1 , wherein the initiation of the second communication channel is configured to occur:
at a first time instance for a first type of predefined business process; and
at a second time instance for a second type of predefined business process, the second time instance being different from the first time instance.
3 . The method of claim 1 , wherein the configuring of the second communication channel comprises:
sending a request to a complementary communication system;
receiving a session token for the second communication channel;
communicating the session token to the first network node by at least one of:
sending the session token to the support node along with an instruction to the support node to share the session token with at least one of the first user node and the second user node;
sending the session token to a user email address identified in the user account data; and
sending the session token as a push request to at least one user application identified in the user account data and associated with at least one of the first user node and the second user node; and
authenticating the second communication channel using the session token.
4 . The method of claim 1 , further comprising:
receiving a fetch request from the support node;
sending a data request to the complementary communication system for forwarding through the second communication channel to at least one of the first user node and the second user node;
receiving, from the complementary communication system, in response to the data request, user input data through the second communication channel from at least one of the first user node and the second user node;
validating the received user input data;
forwarding the validated user input data to the support node;
receiving, in response to the forwarding, a confirmation message from the support node; and
in response to the confirmation message, terminating the second communication channel.
5 . The method of claim 1 , further comprising:
receiving a fetch request from the support node, the fetch request being associated with a predefined business process;
in response to the fetch request, sending a data request to the complementary communication system for forwarding through the second communication channel to at least one of the first user node and the second user node based on the fetch request and the predefined business process;
receiving, from the complementary communication system, in response to the data request, user input data through the second communication channel from at least one of the first user node and the second user node, the user input data being inaccessible by the support node;
performing at least one transaction associated with the user input data; and
sending an instruction to the support node, the instruction being based on a status of the predefined business process.
6 . The method of claim 5 , wherein sending, through the second communication channel, the data request comprises:
generating a data packet based on the fetch request, the user account data, and the predefined business process, the data packet being configured to communicate with a user interface of at least one of the first user node and the second user node; and
allowing access to at least one of the first user node and the second user node to at least one of:
a webpage,
an application,
an image, and
a portable document format, PDF, document,
via the complementary communication system, based on a format of the generated data packet.
7 . A method performed by a support node in communication with a first network node, the method comprising:
configuring a first communication channel for a first communication session between the support node and a first user node; and
sending, to the first network node, a session request to initiate a second communication channel for a second communication session that bypasses the support node but that is logically joined to the first communication session to create a single logical communication session, the first communication channel being voiced-based, and the second communication channel being data-based, the support node being unable to view any communications transported via the second communication channel, the second communication channel being between the first network node and at least one of the first user node and a second user node, the first communication session and the second communication session being synchronized to a predefined business process associated with the logical communication session where the first network node simultaneously sends and receives data from at least one of the first user node and second user node via the first communication channel or the second communication channel.
8 . A first network node that is in communication with a support node, the support node being configured to communicate with a first user node using a first communication channel for a first communication session, the first network node comprising processing circuitry configured to:
receive user account data associated with a user of the first user node;
receive, from the support node, a session request to initiate a second communication channel for a second communication session that bypasses the support node but that is logically joined to the first communication session to create a single logical communication session, the first communication channel being voiced-based, and the second communication channel being data-based, the support node being unable to view any communications transported via the second communication channel; and
configure the second communication channel between the first network node and at least one of the first user node and a second user node, based on the session request and the user account data, the first communication session and the second communication session being synchronized to a predefined business process associated with the logical communication session where the first network node simultaneously sends and receives data from at least one of the first user node and second user node via the first communication channel or the second communication channel.
9 . The first network node of claim 8 , wherein the initiation of the second communication channel is configured to occur:
at a first time instance for a first type of predefined business process; and
at a second time instance for a second type of predefined business process, the second time instance being different from the first time instance.
10 . The first network node of claim 8 , wherein the configuring of the second communication channel comprises:
sending a request to a complementary communication system;
receiving a session token for the second communication channel;
communicating the session token to the first network node by at least one of:
sending the session token to the support node along with an instruction to the support node to share the session token with at least one of the first user node and the second user node;
sending the session token to a user email address identified in the user account data; and
sending the session token as a push request to at least one user application identified in the user account data and associated with at least one of the first user node and the second user node; and
authenticating the second communication channel using the session token.
11 . The first network node of claim 8 , wherein the processing circuitry is further configured to:
receive a fetch request from the support node;
send a data request to the complementary communication system for forwarding through the second communication channel to at least one of the first user node and the second user node;
receive, from the complementary communication system, in response to the data request, user input data through the second communication channel from at least one of the first user node and the second user node;
validate the received user input data;
forward the validated user input data to the support node;
receive, in response to the forwarding, a confirmation message from the support node; and
in response to the confirmation message, terminate the second communication channel.
12 . The first network node of claim 8 , wherein the processing circuitry is further configured to:
receive a fetch request from the support node, the fetch request being associated with a predefined business process;
in response to the fetch request, send a data request to the complementary communication system for forwarding through the second communication channel to at least one of the first user node and the second user node based on the fetch request and the predefined business process;
receive, from the complementary communication system, in response to the data request, user input data through the second communication channel from at least one of the first user node and the second user node, the user input data being inaccessible by the support node;
perform at least one transaction associated with the user input data; and
send an instruction to the support node, the instruction being based on a status of the predefined business process.
13 . The first network node of claim 12 , wherein sending, through the second communication channel, the data request comprises:
generating a data packet based on the fetch request, the user account data, and the predefined business process, the data packet being configured to communicate with a user interface of at least one of the first user node and the second user node; and
allowing access to at least one of the first user node and the second user node to at least one of:
a webpage,
an application,
an image, and
a portable document format, PDF, document,
via the complementary communication system, based on a format of the generated data packet.
14 . A support node in communication with a first network node, the support node comprising processing circuitry configured to:
configure a first communication channel for a first communication session between the support node and a first user node; and
send, to the first network node, a session request to initiate a second communication channel for a second communication session that bypasses the support node but that is logically joined to the first communication session to create a single logical communication session, the first communication channel being voiced-based, and the second communication channel being data-based, the support node being unable to view any communications transported via the second communication channel, the second communication channel being between the first network node and at least one of the first user node and a second user node, the first communication session and the second communication session being synchronized to a predefined business process associated with the logical communication session where the first network node simultaneously sends and receives data from at least one of the first user node and second user node via the first communication channel or the second communication channel.