Skip to main content

Standalone CRM is Not Enough

Nearly every organization wants to serve its customers and constituents better, and Customer Relationship Management (CRM) software is seen as the answer to be better connected and more responsive to the needs of those your company, association or government agency serves.

CRM gives you a channel through which you can interact, and excellent means of tracking these customer interactions.  Microsoft Dynamics CRM, for instance, tracks customer service calls, orders, quotes, and marketing outreach.  With Parature for Dynamics, you get additional channels of online chat and social media. 

While CRM is a great start, and arguably essential to improving customer service, it is not enough without being integrated with other systems in your organization.  Being able to reach a customer service representative quickly is good only if that person can resolve your problem, and the information needed to solve the problem is likely in other system, such as accounting, manufacturing, orders, or appointment scheduling.

When InfoStrat worked on a Dynamics CRM implementation at a large U.S. federal agency, it required integration with over a dozen systems in order to provide all the visibility needed by a customer service representative. 

Fortunately, Microsoft Dynamics CRM is a modern software platform based on open standards such as web services, and lends itself to integration.  Along with other integration tools on the Microsoft development platform, you can provide an excellent user experience for customer service reps and customers alike.

So the moral of the story is to give the customer service reps access to all the data that they need so they can improve the satisfaction of all your customers.  Don't stop with just a CRM system that let's you keep score -- go the full distance so they can make it to the customer satisfaction finish line.  

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan