To streamline communication and clarify case conversation history for an insurance company handling a high volume of cases, I recommend a combined approach utilizing Case Comments and Case Hierarchy, with careful consideration of Chatter's limitations:
A project sponsor has stated that their primary goal is to reduce the cost per case in the contact center.
Which standard metric should a consultant focus on improving to reduce cost per case in the contact center?
While all the options mentioned can be helpful for improving efficiency in resolving customer cases, the most suitable recommendation for Ursa Major Solar based on the given scenario is:
Use Salesforce Knowledge to store questions and answers so agents can easily reproduce the same answer for similar questions.
Universal Containers has implemented service-level agreements (SLAs) to resolve cases There is an additional requirement when the contact center is closed for a holiday to not apply escalation rules or milestones during this time
How should a consultant recommend implementing this requirement?
The reason why the work that was already in the queue is not being pushed to agents is:
The "Apply to existing records in queue" option was not selected.
At Ursa Major Solar, customer service agents follow a case close process to ensure a summary is provided of the customer's question and the provided answer
What should a consultant propose to improve this process so that these summaries make solving future customer cases more efficient?
Answer : A
To improve the case close process at Ursa Major Solar and make solving future customer cases more efficient, a consultant should propose using Salesforce Knowledge. By storing summarized questions and answers in Salesforce Knowledge, agents can quickly access and reuse this information for similar future inquiries. This approach not only saves time but also promotes consistency in customer responses and enhances the overall quality of support.
The consultant should recommend UC configure the solution by setting up the organization's default business hours and creating an escalation rule where the case matches the criteria associated with different business hours.
An administrator has activated Omni-Channel routing on a queue for the first time. However, agents are not seeing the work that was already in the queue
What is the reason for the work that was already in the queue not being pushed to agents?
Answer : A
When Omni-Channel routing is activated on a queue for the first time, existing records in that queue will not automatically be pushed to agents. This is because Omni-Channel only starts routing work items that arrive in the queue after its activation. Any work that was already in the queue prior to enabling Omni-Channel will need to be manually reassigned or triggered to enter the Omni-Channel routing process.
The most suitable Service Cloud Voice feature for Ursa Major Solar to
protect customer information during phone interactions is:
Pause/Resume Call Recording
A client requires that their Messaging for Web customers are able to see
wait times when starting an interaction. They also want to allow a banner to
inform customers that chats are unavailable outside of business hours.
What are some of the required configurations in this solution?
Answer : B
To enhance the customer experience for Messaging for Web, several configurations are needed:
Business Hours: Must be active to inform customers about service availability during specific hours.
Omni-Channel Queue or Flow: Required for managing and routing customer interactions.
Estimated Wait Time: Should be activated to display expected wait times to customers, helping manage their expectations.
Business Hours added to the Embedded Deployment: Ensures that the chat functionality reflects the correct availability times and conditions outside business hours.
Ursa Major Solar will use Data Loader for data migration of closed cases
because of large amount of data
What does a consultant need to keep in mind while using data loader?
The environments that should have a two-way deployment connection in
this scenario are Test Sandbox and Production Org.
Which requirement needs to be met to perform a quick deployment for
change sets or Metadata API components without testing the full
deployment?