#Customer Service14 discussing

Hi @Shruti Jain

The best approach is to use Salesforce Business Hours with Entitlement Management.

Create separate Business Hours for each customer region/time zone (e.g., US, UK, India), including working hours and holidays. Then use Flow or Apex to assign the appropriate Business Hours to the Case based on the customer's location.

For milestone calculation, Salesforce follows this hierarchy: 

Milestone → Entitlement Process → Case Business Hours.

Therefore, if the SLA needs to vary by customer location, configure the correct Business Hours on the Case and avoid overriding them at the Entitlement Process/Milestone level.

This ensures that Entitlement and Milestone timers count only the customer's applicable business hours, including holidays and time-zone differences.  

Hope This Helps!!

Hi Vadim,

Case Assignment Rules don't natively understand an employee's work schedule or whether a user is currently working.

A common approach is to maintain a simple Support Availability/Schedule object or fields that indicate whether a support analyst is available for assignment. Your assignment logic can then check that availability before assigning the Case.

If you're using a custom assignment process, Apex can query the available analysts and assign the Case accordingly. You could also maintain separate queues for different shifts and route Cases to the appropriate queue rather than directly to individual users.

For a small support team, queues plus a simple availability mechanism are usually easier to maintain than building a full scheduling system. 

Hi Justin,

Your use case can fit well with Cases + Service Contracts + Entitlements, without necessarily requiring a very complex implementation. 

I would consider using the Case as the customer/service issue and the Service Contract/Entitlement to determine what coverage and response expectations apply. Your custom Work Order can then handle the field-service-specific details such as dispatch, technician, diagnosis, parts, and trip/debrief information. 

For the warranty scenario, you could create separate entitlement rules for manufacturer warranty vs. customer service contracts, and have the Case determine which entitlement applies. You can then track metrics such as response time, number of trips, and resolution time to identify where repeat visits are occurring. 

I would start with the standard Case/Entitlement functionality and keep the Work Order integration as simple as possible, adding automation only where it removes manual steps. 

Hi Willow,

Rather than using the Case Last Modified Date, you can track the inbound emails associated with the Case. With Email-to-Case, each incoming email can be associated with the existing Case, so the email records can be used to count how many inbound messages were received. 

You could then create a report grouped by Case and count the inbound emails to measure the actual volume of customer responses/questions, even when they all belong to the same Case. 

If you need that count stored directly on the Case, you could use automation/custom Apex to maintain an "Inbound Email Count" field whenever a new inbound email is received. 

This would give you a much more accurate measure of the CS workload than simply counting Open Cases. 

Hi Sandra,

Not receiving the installation confirmation email is a common hiccup in Salesforce, but as long as the package installation screen showed complete without throwing critical errors, the package is almost certainly installed in your org. You don't actually need that email to proceed.

Here is how you can verify and fix both issues:

1.Check Installed Packages:Package Verification. 

Go to Setup > Installed Packages to confirm whether "Groundwire Volunteers for Salesforce" (or Volunteers for Salesforce) appears in your list with a valid version number. You can verify success when the package name and components are visible in the package list.

2.Check Session Settings or Domain:Help Link Redirect Fix. 

The help link redirect issue usually happens due to browser cookie conflicts or missing domain/session security settings that invalidate your session token when jumping to external domains. Try clearing your browser cache, logging out and back in, or checking your Session Settings in Setup (such as "Lock sessions to the IP address from which they originated"). You can verify success when clicking help links opens the documentation page without throwing access errors.

Hi Demps,

The message about the “inforce connector” suggests that the Request Update feature is using a third-party LinkedIn integration rather than a standard Salesforce feature. The “solution provider” would therefore be the vendor that supplied that connector/integration. 

Since this is from 2012, the LinkedIn integration/API may no longer be supported, which would explain why the login/authorization step is failing. The Salesforce Community post itself does not identify the provider or provide a current fix. 

I would check Setup → Installed Packages and Connected Apps for the Inforce/LinkedIn integration and identify the package/vendor. If the package is no longer supported, the Request Update feature would need to be replaced or updated with a supported LinkedIn integration. 

If you can provide the Inforce package name/version o

Hi,

For duplicate Ideas, there isn't a standard user action to merge two Idea records yourself. If you identify duplicates, you can flag/report them to the IdeaExchange/Product Manager team so they can review and determine whether they should be merged or otherwise handled. 

I'd recommend including the links/IDs of the suspected duplicate Ideas and explaining why they're duplicates. Avoid simply assuming that similar titles should be merged, since the Ideas may have different use cases or requirements. 

For the “Idea bundle/lot” review date, that isn't generally exposed as a standard field on the Idea. If you need to know when a Product Manager last reviewed a particular group of Ideas, that would depend on whatever internal process Salesforce uses for managing those Ideas.