InterACT2Go, Mobile App and Designer for Sales and Service from CRMantra.Fully integrated with Salesforce and Siebel.
http://www.interact2go.com/
InterACT2Go
Mobilize your Sales and Service
Fully integrated with Salesforce and Siebel
Showing posts with label Salesforce. Show all posts
Showing posts with label Salesforce. Show all posts
Tuesday, 23 August 2016
Monday, 4 April 2016
NEW! InterACT2Go - Mobile CRM App and App Designer from CRMantra
NEW! InterACT2Go - Mobile CRM App and App Designer from CRMantra
It’s About Sales and Service, Not Just CRM.
1. CRM Isn’t the Only App.
Field reps use many apps and services (including CRM) to complete their tasks. For best UX and adoption, mobile apps should provide intuitive and seamless process flows resulting from mash ups of multiple back-end systems and services.Integrations with multiple back-end systems and services are critical.
2. 360° View at All Times.
Users need a 360° view at all times. Definition of the 360° varies by users’ role and stage in the process. This view has to be readily customizable.
3. Access to Data.
Users need access to relevant data all times. On the go. Online or Offline. That’s what mobile is about, isn’t it?
Want to know more and understand the full capabilities?
Fill in the form below and the InterACT2Go info sheet will be emailed to you.
Thanks
Wednesday, 27 January 2016
Mobile Apps - What’s the cost of free ?
Mobile Apps - What’s the cost of free ?
At some point everyone has to compete with ‘free’. I’ve recently come up against this and it is surprising how many customers hear the word ‘free’ and forget to check out the small print and all the repercussions.
So what makes the customer believe they have an option
that is ‘free’? I’ve listed a few
possible scenarios.
1 – “The licences are free”
This turns out to be a total misunderstanding, in fact the licences are far from free, but what they do have are existing licences that would cover this application, but there is still annual support and maintenance to be paid, and at a typical 18-22% this is no small amount.
There is also the dreaded small print – what exactly
are you signing up to? How long is it
‘free’ for? What happens after Year1 –
are you locked in regardless of any increase in costs? This could be an expensive mistake.
This is a sure fire way to have the
project fail, and potentially bring the company to its knee’s as key sales and
support users are unable to use the new application.
Additional
costs come from all directions
(a) Technical and functional consultants to correctly
implement and extend the OOTB solution
(b) Infrastructure and security architects to design a
deployable mobile solution
(c) Re-writing and developing new training material
(d) Rolling out user training
(e) New hardware and MDM system for the mobile
solutions
(f) Training for Operations and Support to allow them
to deploy and support the new application.
(g) Deploying and supporting the new application,
hardware and MDM systems
3 – “The free solution isn’t perfect, but its ‘good enough’”.
We have been recently deploying a number of Mobile Sales solutions and its pretty obvious that in this area ‘good enough’ rarely cuts it with the end user. The User Adoption rates for mobile solution needs to be almost vertical, otherwise the device is put on a shelf and forgotten about, and it’s then almost impossible to re-invigorate the user base, leaving IT to support costly legacy solutions, as well as the new applications.
A few key things on user adoption come to mind for a
mobile solution
(a) Usability – It has to be current, visually
appealing and easy to use. In sales for
example we are seeing sales reps, sitting with their customer using the mobile
solution to take them through the product catalog, the quote, the configuration
– this is no longer an internal facing application.
(b) Process centric – It needs to be easy and intuitive
to do the tasks that the user has to do day in, day out.
(c) One for all – It needs to be one app that covers
all the aspects of the users job, and that typically involves access to
information from a multitude of
back-end systems.
(d) It has to be a ‘useful’ tool – not just a way for
management to track the number of calls made or meetings organised. Intelligent
analytics are a key way to feedback to the user as to where to spend their time
to be most productive.
So let me quickly recap on those potential costs
·
Licence
fees
·
Maintenance
fees
·
Implementation
costs
·
Training
costs
·
Deployment
costs
·
Support
costs
·
Cost
of potential future tie-ins
·
Cost
of failure – due to poor user adoption
So, as you can see a free licence fee is far from it when
the total project is scoped out, and it’s typically only a small part of the whole project.
Read more about InterACT2Go - Enterprise Mobility Platform
Get in touch:
Monday, 21 December 2015
Friday, 26 June 2015
Cloud Control – When More than One could be a Crowd!
Cloud Control – When More than One could be a Crowd!
Too many cloud applications can quickly lead us to the same level of complexity as managing multiple On-Premise applications. Adding more cloud apps to your enterprise IT ecosystem may be too much of a good thing.
The CRM cloud application (It could be
Salesforce, Oracle Sales Cloud, or MS Dynamics, etc) is normally at the centre
of your solution. Typical challenges we see in maintaining these alongside multiple
‘edge’ cloud apps:
1.
Integrations and Data
Migrations: Many ‘edge’ cloud apps use a
custom object for the same CRM entity (for example, a custom object to hold
Account or Customer Information, Product Data, etc.. which are also present in
the base CRM application.)
There is a common need to “integrate” between the CRM object
definition and the cloud app’s customer object definitions. This approach increases integration and data
migration costs and results in unnecessary replication of data.
2.
Upgrades: Many cloud app vendors tout their frequent
release cycles as a testament to their pace of innovation. As a result, there is the rising cost of incessant cycles
of testing, releases, and user training.
3.
Environment cloning and
migrations: Each cloud app comes with
its unique installation and migration procedures. A strong system admin team is required to
clone environments for Development, QA, UAT and Production. Each application could have a different set
of code and processes to be installed.
4.
Technology Stack to build the
Cloud App: Is it native force.com, java,
.Net, or another custom language? Does
the Cloud app include components (such as configurator or pricing engines) that
are built using different languages or residing in a separate cloud?
5.
Process-related Data Migration:
‘Lead-to-Contract’ is one of the processes where data mapping needs to occur
between many objects such as Lead to Opportunity, Opportunity to Quote, Quote to
Order, Order to Contract, Asset to Quote, etc.
Custom workflows to enable the mappings and flows result in high
implementation and maintenance costs.
Many of the cloud vendors have ignored these
challenges, whilst a few are addressing these issues (and rightly so!). So when you’re looking for a cloud solution ask
the vendor if they have done the following:
1. Pre-built end-to-end,
industry-specific CRM apps reducing the need to manage and maintain multiple
cloud apps.
2. Focused at the
outset on the integrations and data migrations, building adapters for most
common on-premise applications.
3. Offer a ‘CRM’ object-first
guarantee. As a result, they would not
replicate any objects released by the CRM vendor, either pre-existing or in the
future. In addition, their apps
guarantee compatibility with the CRM native objects.
4. Provide tools to
facilitate Process-centric data migration through declarative mapping between
any objects in the CRM instance.
Takeaways:
1. The marginal
benefit of installing a new cloud app vis-Ã -vis the existing on-premise app requires
careful consideration. Keeping the
on-premise application may not be a bad decision after all!.
2. Just because the
edge app is built natively on the same platform as the CRM application doesn't
mean there is no integration and data migration effort.
3. Detailed
understanding of the integrations involved.
The existence of some APIs is just table stakes; use of those APIs to
integrate and load data is where heavy lifting is necessary. Check for existence of tools and solutions to
address these.
4. Check on the excessive
use of custom objects to store data that is already stored in the CRM native
object.
If you’d like to know more about which
cloud vendors we think are taking the right approach then please get in touch
Subscribe to:
Posts (Atom)