End of September 2013, we will release our Autumn update of the Resco Mobile CRM. It’s the 3rd major update this year, and although previous two brought fantastic improvements such as Enterprise Security, Mobile Audit and others, this one will be an extraordinary. It will allow usage of Mobile CRM app also for non-CRM users such as suppliers, partners, or customers.
The current version of the Resco Mobile CRM allows only one, CRM user based, type of authentication. So as of now, a typical user of the Resco Mobile CRM is an organization’s own employee; such as sales rep or technician. Each must be a CRM user with a specific user role assigned.
The new update will bring two new types of authentication: Registered User and Anonymous.
In the Registered User authentication scenario, you can define one common CRM user with a specific security role, which will be used for all registered users. Then you select a specific entity (standard or custom) and two fields from it that will serve as Username and Password for the user authentication. To finish, just customize a mobile app in Woodford the same way as you would for your internal staff and the work is done. These registered users can then use a customized mobile app, as this type of authentication allows them to access user related CRM data.
To illustrate Registered User authentication, here is example scenario for business partners: You create a custom entity “Partners” in your CRM. Make sure the entity contains, among other fields, username and password. Your partner installs Resco Mobile CRM app to his smartphone or tablet and logs in. The partner-specific customization, you have previously published, shows up on his app and lets him work with partner-related CRM content. He is now able to update his profile, view common documentation, track open cases, create orders, get latest product info, etc.
As you can easily imagine, this is not just a new feature to Resco Mobile CRM. This is a new usage scenario. You can start considering completely new opportunities for your business.
I will describe the Anonymous authentication later on, in a second part of this blog.