Why S4S?

If you are using or moving to Salesforce as a CRM, you can now team up with Sitecore CMS to integrate and publish your Salesforce objects and assets to public-facing websites and extranets with ease. The S4S connector makes this easy. With transparent and bi-directional access, the rich graphical environment of Sitecore is supported by the heavy duty CRM tools offered by Salesforce.

S4S is the ideal solution for clients requiring both a strong web content management and Salesforce, the market leading customer management and collaboration platform. This allows sharing features across platforms and the ability to maintain and publish content and information from one place.

Have a look at the following example use cases:

Use Case 1 – Salesforce Contacts are flagged as Sitecore website users

• Salesforce Contact A belongs to Account T and needs login access to the website.
• Account T has already been designated as a Sitecore Role.
• Using S4S, Contact A can now log in to the website and has a Sitecore role that equates to Salesforce Account T (and Sitecore renders content according to that role).

Use Case 2 – Salesforce Leads are created from the Sitecore website registration form

• Customer A comes to the website for the first time and registers on the registration form.
• Using S4S, Lead L is created in Salesforce using the registration details.

Use Case 3 – Web-to-Lead capture from the Sitecore website Apply Now form

• Customer A visits the website and submits an Apply Now form.
• Using S4S, Candidate A is created in Salesforce and populated with the form details (Candidate is an object from the AppExchange Recruiting application).

Use Case 4 – Salesforce Contact A details are updated on the Sitecore website

• Customer A visits the website, logs in and makes changes to his/her profile.
• Using S4S, the customer is matched to Contact A in Salesforce and the Contact details in Salesforce are updated.

Use Case 5 – Website users view files in the Salesforce Document Tab

• Customer A visits the website, logs in and navigates to a Show Files page.
• On the page, the customer clicks the “Show All” button.
• Using S4S, the files listed in the Salesforce Document tab are displayed on the website page.
• The customer clicks on the required file which opens in accordance with its document type.

Use Case 6 – Sitecore website users see a pre-populated Support form

• Customer A visits the website, logs in and navigates to a Support page.
• On the page, several customers detail fields are already populated with the current data from Salesforce.

Use Case 7 – Show a Salesforce Report on the Sitecore website

• Customer A visits the website and navigates to the Reports page.
• The customer selects and views the required report in the preferred format.

Use Case 8 – Salesforce User X monitors the movement of Contact A on the Sitecore website

• Customer A comes to the website for the first time and visits three pages.
• Using the OMS and S4S, the customer is matched to Contact A in Salesforce.
• The customer returns to the site at a later time and the OMS and S4S passes the experience to Salesforce.
• Salesforce User X can see what the customer (Contact A) is doing on the site.

Use Case 9 - Salesforce User X selects what Customer A is shown on the Sitecore website

• Salesforce User X wants Customer A to buy Product Y.
• Salesforce User X connects the customer to Salesforce Account T and clicks the Product Y checkbox to reflect the customers interest.
• Using S4S, the OMS knows this and assigns a very high interest value for Product Y whenever Customer A comes to the website.
• The websites content adapts using OMS rules and Customer A will see a lot of Product Y content.

Document Resource:      S4S Brochure