Industry Knowledge and Service Cloud Landscape
Reading the landscape like a consultant
Service Cloud questions test whether you can map business intent to platform capability. Know the positioning: a case-centric service application that extends into digital engagement (Messaging for In-App and Web, Service Cloud Voice, Experience Cloud self-service), field service, and AI (Einstein, Agentforce). Know that editions (Essentials, Pro Suite, Enterprise, Unlimited) gate features - Omni-Channel, Entitlement Management, and most Einstein/Agentforce capability are Enterprise-and-above conversations, and add-on licenses (Service Cloud Voice, Knowledge, messaging) are separate line items.
Speak contact-center metrics precisely, because questions hide slack definitions inside them:
- AHT = talk time + hold time + after-call work; not just talk time.
- FCR = resolved on first contact without reopen or transfer.
- CSAT vs NPS - satisfaction with a transaction vs loyalty propensity.
- Containment (bot resolves without a human) vs deflection (the customer never creates a case at all).
Trap: options that assume a feature ships in every edition, or that equate "chat" with "messaging." Messaging is asynchronous and persists across sessions; legacy chat is synchronous.
Rule of thumb: when a stakeholder gives you a metric, ask what sits in the numerator and denominator before you design a report around it.
Worked example: A client reports 4:00 AHT. Logs show 2:30 talk, 0:45 hold, 1:15 wrap-up, so true AHT is 4:30 - 25% of handle time is invisible in their current reporting. That gap becomes your first analytics requirement.