Powering Salesforce with a Complete Customer View Salesforce puts a wealth of information at your fingertips. With real-time snapshots of your sales and marketing performance to annual summaries, it’s no surprise that most Salesforce customers aim to take full advantage of this information to make strategic decisions that drive revenue. Cloud Customer 360 for Salesforce helps you accomplish that.
Cloud Customer 360 for Salesforce automatically detects and corrects erroneous and duplicated data while validating contact and address information. These steps are also repeated at point of entry using Cloud Customer 360’s automated search and enrichment capability, to help marketing maximize lead gen ROI and sales follow CRM best practices.
Are your problems with poor data quality leading to reduced conversions, poor forecasting and low marketing ROI?
Cloud Customer 360 for Salesforce uses fuzzy matching to automatically consolidate your data. Prioritize data sources and key fields from multiple cloud and on-premises systems, such as SAP, Oracle EBS, Marketo and so forth. Now you can maintain and enrich master data on a constant basis and provide sales, marketing and customer service with single unified source of real-time data.
Are you struggling to get a single view of your customer across multiple cloud and on-premises systems?
Whether inherited from M&A or deployed as a deliberate strategy, multiple Salesforce instances (Orgs) need to be coordinated in a way that matches your business model. With the flexibility of Customer 360 for Salesforce, you can now either roll up reporting for sales, marketing and services into a Global Reporting Hub, or deploy a Master Sub Org to manage and synchronize business processes across the enterprise. Either way, you’ll gain a big picture view of your business for better strategic decision making and selling.
Are you unable to get a global view of your customers across multiple Salesforce orgs?
With dynamic, multidimensional hierarchies, Cloud Customer 360 for Salesforce enables each user to see the relevant customer story for their role, regardless of the source. Now you can navigate and go beyond Salesforce functionality to manage the different hierarchy types and relate global accounts with their subsidiaries rolled up to an ultimate parent. With Contact, Lead and Opportunity objects visible across the entire account hierarchy (including subsidiaries), marketing can track campaign influence. And sales can perform white space analysis to identify cross and-up-sell opportunities across the entire company.
Are your reporting problems preventing you from gaining a bigger picture of your global accounts for strategic planning?
Requirement ID – Requirement Definition
FR1.0 – Installation and license activation.
FR1.1 – Configure preliminary CC360 configurations to activate the application:
FR2.0 – Validate and standardize address and email address data using Informatica’s DaaS service options within CC360
FR2.1 – Profile SFDC dataset to establish the quality of data CC360 will be working with. Informatica’s Cloud platform (“ICS”) contains a mapplet which can assist. The mapplet outputs 3 spreadsheets which represent Frequency Distribution, Pattern Analysis and Profile Summary. Using this data an initial configuration can be completed.
FR2.2 – Once there is an indication of the data quality, CC360 can be configured accordingly using the best populated fields for comparison purposes:
With the results of the data profiling activity, the following settings will be configured:
FR3.0 – Master bean and bean records will created:
FR3.1 – Identify duplicate records based on the Match configuration settings previously set:
FR4.0 – Review the list of duplicate records stored under the Duplicate Accounts objects. Note – after review we may be required to adjust the CC336 segment, match and/or performance settings ( goto FR2.2 ).
FR4.1 – Resolve duplicates through a phased approach based on the duplicate score:
FR5.0 – Configure CC360 for up to 2 additional external data sources
FR6.0 – Define enrichment behavior between bean and transactional object:
FR7.0 – Hierarchy