Gilbarco Veeder Root
A Sales Support App
The client (a B2B fuel dispenser company) reached out to us with a requirement to automate their sales and support process and modernize the traditional product catalog.
Currently, the on field sales teams carry multiple documents detailing multiple products when they meet Clients & Prospective customers. There was no automated mechanism to cater to support needs of existing customers in an efficient and effective manner. Customers would place calls to support center and would wait for service representatives to show up. This was a time consuming and cumbersome process that led to a negative customer experience.
An App which integrates the Seller & Buyer through a mobile interface
E-Catalogue for the sales force
24/7 Support via App
Excellent UI & UX with a user friendly interface
Registration and Login (Technician, Seller, Buyer )
Product Information, Spare Information, Technical Support
User Management and Authentication
New Product Content Upload
Provides the following regarding GVRs Dispensers:
A Sales-tour of the existing Dispensers.
Aids on-site troubleshooting of GVR dispensers done by technicians/engineers. They can upload the following to the app:
Pictures/Audio files/Video files limited to a certain size
Intimates GVR customers regarding availability of spares & discontinuation of spares for Dispensers nearing end-of-life.
Centralized backend which would be generalized for other GVR products as required
Currently, the app is being field tested across various geographies. Codewalla has supported the client through the user trials and evaluates the feedback received to enhance the app.
250 South End Avenue,
+1 646 719 0064.
B3, Cerebrum IT Park
+91 20 65291823
And they have to be really good to exploit advanced features. For example, iOS 12 allows you to voice-enable your apps thru Siri extensions (even when your app is not running) Good luck doing that with hybrid (7/7) #sirikit #iOS12TH #iosdev #hybriddev
One of the products we're working on is well past market-validation. At this stage, the total cost (TCO) of hybrid development is higher than that of native development. But the catch is that these are radically different skill sets, for which you need different developers (6/7)
And because with hybrid you can't introduce advanced, OS-specific features as quickly as possible, you risk losing to competition (5/7)