Skip to main content

Service Cloud Basics

Salesforce Service Cloud is a customer relationship management (CRM) platform that helps Salesforce clients offer service and support to customers.

Service Cloud offers a unified workspace with tools to support customers on any channel. It can help with:

  • Service Process Management: Deliver personalized service and support to customers across any channel
  • Field Service Management: Resolve issues remotely and boost first-time fix rates
  • Swarming with Slack: Collaborate to solve cases and complete field service requests faster
  • Automate service processes: Streamline workflows and find key articles, topics, and experts to support customer service agents
  • Case tracking and social networking plug-ins: For conversion and analytics
  • Web-to-Case: Create a new case automatically in Salesforce whenever a support request comes directly from your company's website 

Salesforce Service Cloud has different features that businesses can involve in their service and support practices to ensure smooth deliverability:



Case study:

For example if you are planning to buy intel products you can reach out intel service center via Salesforce service cloud:

They provided dedicated portal to provide service to their customers with below features:
  • Create support ticket
  • Verify your warranty coverage for the products you purchased
  • Pre sales enquiry to buy new product
  • Support history to view your service ticket status
  • Give feedback
  • Support community

 

Comments

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .