Web Server Token Synchronization for Mobile Sales Coordination
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems for network service providers are not well adapted to fully engage customers during sales interactions, as they typically only allow customers to view product information after a purchase and do not provide a clear breakdown of projected bills, including taxes and promotions, before the purchase is made.
Innovation Solution
A system that allows a web server to interact with multiple browsers, synchronizing processes between sales representatives and customers through inter-process signaling using tokens, ensuring that each user receives tailored information and facilitating coordinated interactions during sales transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the system is designed for sales representatives only, then sales representatives can access corporate database information, but customers cannot view product information or projected bill breakdown before purchase
Solution Approach 1:
The system segments user interfaces and information access by user type. Sales representatives receive access to corporate database information and internal tools, while customers receive a customized interface showing product information, projected bills with tax and promotion breakdowns, and purchase confirmation details. This segmentation allows each user group to access only the information and functions relevant to their role.
Solution Approach 2:
The patent implements local quality by providing different information displays and interaction capabilities to different users in the same system. Customers can view projected bill breakdowns, tax calculations, and promotion applications on their mobile devices, while sales representatives simultaneously access different data sets. Each user experiences a locally optimized interface tailored to their specific needs.
2Device complexity
If the system shows product information only after purchase, then system complexity is reduced, but customer engagement and verification capability are limited
Solution Approach 1:
The system performs preliminary actions by displaying projected bill information, tax calculations, and promotion applications to customers before the purchase is finalized. This allows customers to verify charges and understand what they are purchasing in advance, reducing information asymmetry and enabling informed decision-making before commitment.
Solution Approach 2:
The patent implements feedback mechanisms where customers can view real-time updates of projected bills as items are added or modified during the sales interaction. The system continuously provides feedback about tax implications, promotion applications, and total costs, allowing customers to verify information and ask questions before completing the purchase.
3Reliability
If the system uses inter-process signaling with tokens for synchronization, then coordination between sales representative and customer processes is improved, but device complexity increases
Solution Approach 1:
The patent introduces a server as an intermediary that manages the complex synchronization logic between the sales representative's device and the customer's device. The server handles token generation, validation, and process coordination, shielding the mobile devices from the complexity of inter-process signaling while ensuring reliable synchronization of the purchase process between users.
Data Source
AI summary
A web server sends a first coordinator to a first browser of a first mobile device. The first coordinator is a set of instructions executable by the first browser. The web server also sends a second coordinator to a second browser of a second mobile device. The second coordinator is a set of instructions executable by the second browser. The first coordinator, when executed by the first browser, cause the first browser to: send a first request for information to the second browser, over the web server; wait until the requested information is received from the second coordinator over the web server; and when the requested information is received from the second coordinator, perform a first action based on the requested information received from the second coordinator. The first request includes a first token, and the requested information includes a next token.