#Customer Service토론 중인 항목 14개

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.