Omni-Channel Service Desk on Salesforce FSC

A configurable Salesforce Financial Services Cloud (FSC) solution using Sales + Service Cloud to unify Email, Voice (CTI), WhatsApp, Website Chatbot, and Web/App API tickets into a single governed Case system-of-work, powered by Agentforce automation and straight-through processing (STP) integrations to backoffice platforms (e.g., Miles, Wealth Spectrum).

Who this is for

This solution is designed for broking, wealth, and BFS service operations (or any regulated contact center) that need a single omni-channel service desk with strong SLA governance, auditable workflows, and STP execution of common service requests via backoffice systems—while maintaining clear system-of-record boundaries.

Typical Users

• Contact Center Agents (L1/L2) handling Email, Chat, WhatsApp, and Voice interactions
• Supervisors/Team Leads for queue monitoring, escalations, coaching, and approvals.
• Operations / Resolver Teams (DP, Funds, Trading, RMS, KYC, Compliance) working from department pending queues
• Relationship Managers / Branch teams (Sales Cloud users) for service-to-sales follow-ups, retention, and VIP servicing
• Knowledge Managers / Content Owners for Knowledge Base governance and publishing
• Compliance / Grievance Desk for regulatory complaints and escalations
• CRM / IT Admins for security, integration monitoring, and configuration management

A single Salesforce FSC-based system-of-work for servicing with the following capabilities:

• Customer 360 and Relationship Context: Unified client profile (Person Account), household/group context, contact points, preferences, and a cross-channel interaction timeline.
• Omni-Channel Intake: Email-to-Case, CTI voice, WhatsApp, Website Chatbot, and API-based ticket creation from customer web/mobile apps.
• Governed Case Lifecycle: Configurable taxonomy (Nature → Function → Sub-function → Sub-sub-function), controlled status transitions, mandatory disposition + reason capture.
• SLA/TAT Governance: Business hours + holiday calendars, milestone tracking, breach alerts, escalation matrix, and controlled reassignment rules.
• Agentforce Automation: Sentiment analysis, auto-classification, summarization, response drafting using Knowledge, SLA breach risk prediction, and supervisor assist.
• Knowledge-first Servicing: Knowledge Base-driven responses for bot + agents to improve first-time resolution and reduce repeat queries.
• Straight-Through Processing (STP): Integrations to backoffice systems (Miles, Wealth Spectrum, and similar) to execute standard service requests and auto-update Case status.
• End-to-End Audit Trail and MIS: Dashboards for channel-wise inflow/outflow, SLA compliance, escalations, reopen trends, productivity, and quality indicators.

Service operations are often fragmented across inboxes, telephony tools, WhatsApp, portals, and multiple back-office screens. This leads to:

• Swivel-chair servicing due to a lack of a single client interaction history and inconsistent tagging
• Unreliable SLA tracking and escalations due to manual handoffs and unclear ownership
• Long resolution times for standard requests (statements, profile changes, order/fund status) that could be automated
• Limited deflection of FAQs because digital channels are not Knowledge-driven
• High agent effort on repetitive tasks: classification, summarization, drafting, and follow-ups
• Low visibility for supervisors into queue load, breach risk, and quality of responses

Salesforce FSC + Service Cloud is the core system-of-work for servicing, supported by:

• FSC Data Model: Person Accounts, Household/Relationship Groups, financial account context (as applicable), interaction history
• Service Cloud Case Management: omni-channel routing, queues, SLAs/milestones, escalations, and Knowledge
• Sales Cloud Enablement: RM/branch visibility for service follow-ups, VIP servicing, and retention workflows (where applicable)
• Agentforce Layer: automation and AI-driven assistance (sentiment, categorization, summaries, drafts, risk alerts, supervisor assist)
• Channel Integrations: Email, CTI, WhatsApp, Website Chatbot, Web/App APIs
• Backoffice STP Integrations: Miles, Wealth Spectrum, and similar systems for statements, profile updates, order inquiries, and payment-related inquiries
• Reporting & MIS: dashboards for operations, leadership, compliance, and QA

Module 1 — FSC Customer 360 and Identity

• Person Account as the primary client record; supports multiple contact points (phone/email), preferences, and consent flags.
• Household / Relationship Group support for family relationships and mapped service context
• Identity matching for digital and assisted channels using registered email/phone + client/trading ID (configurable)
• Customer interaction timeline consolidating emails, calls, chats, WhatsApp conversations, and cases

Module 2 — Case Management, Taxonomy and Workflow Governance

• Single Case record as the work item for all channels with taxonomy: Nature → Function → Sub-function → Sub-sub-function
• Controlled status transitions: New → In Progress → Pending with Department → Customer Awaiting → Resolved → Closed (configurable)
• Stage gates: mandatory reason capture, disposition codes, closure summary, and attachments where required
• Controlled handoffs/reassignments with audit logs; optional concurrency lock/freeze to prevent parallel actioning
• Repeat/duplicate detection for inbound requests using customer + topic + time window (configurable), with merge/link capability.

Module 3 — Omni-Channel Intake

Email-to-Case

• Convert inbound emails to Cases with full thread history and mailbox-driven routing.g
• Auto-acknowledgement templates and controlled outbound replies from approved mailboxes
• Queue/skill routing using mailbox + keywords + customer type + priority rules

Voice / CTI

• Screen pop client profile and open cases using caller ID and/or assisted verification
• Call-linked Case creation with disposition, notes, and an optional recording link
• Supervisor monitoring and call outcome reporting (as enabled by CTI provider)

WhatsApp/Website/Mobile App Chatbot

• WhatsApp bot for FAQs + structured request capture; creates/updates Cases and attaches transcript
• Live agent handoff with context + transcript when the bot cannot resolve
• Notifications for case milestones and document requests (optional)

Web/App APIs

• API-based Case creation and status tracking from customer web/mobile apps and support pages
• Attachment upload APIs for screenshots/documents with validation controls
• Customer Status View: case status, SLA due time, last update, and next required action

Module 4 — Website Chatbot with Knowledge-First Responses

• Chatbot Embedded: on the customer website to support inquiries and service requests.
• Knowledge-First Responses: bot answers using Salesforce Knowledge articles mapped to intents/taxonomy
• Authenticated Journeys: for account-specific queries via SSO (preferred) or OTP verification (configurable)
• Case Creation From Chat: when execution is required; bot captures structured fields (category, statement type, date range, etc.)
• Live Agent Handoff: during service hours or case creation + callback scheduling after hours, with transcript attached

Module 5 — Knowledge Base (KB) Governance and Reuse

• Knowledge Article: authoring, approval, and publishing workflows with review/expiry cycles
• Taxonomy-Based Article: mapping to improve bot resolution and agent recommendations
• Agent Assist Panel: KB suggestions surfaced based on Case category + conversation context
• Analytics: deflection rate, top intents, article effectiveness, and content gaps prompting new KB creation

Module 6 — Agentforce Automation (Service Productivity + Governance)

Agentforce Use Cases

• Sentiment analysis on inbound Email/Chat/WhatsApp transcripts to auto-adjust priority and trigger supervisor alerts for high-risk cases
• Auto-classification of Cases (Nature/Function/Sub-function) and routing suggestions with confidence scoring
• Conversation summarization for long email threads and chat transcripts; auto-generated “Customer Ask” + “Next Steps.”
• Response drafting using approved KB content and templates (agent final review and send)
• SLA breach risk prediction and proactive reassignment recommendations to supervisors
• Auto-generated closure narrative and compliance-ready resolution summary

Module 7 — Backoffice STP Integrations (Miles, Wealth Spectrum, and similar)

Integration Pattern

• Salesforce FSC/Service Cloud is a system of work for request capture, validation, approval, and customer communications.
• The integration layer orchestrates API/file calls to back-office systems, handles retries, reconciliation, and async callbacks.
• Backoffice remains the system of record for execution, ledger, statement generation, and trading/payment processing.
• Salesforce auto-updates Case status with backoffice reference IDs + outcomes (success/failure/reason codes)

Straight-through processing (STP) request catalog (sample set)

Statements and Reports

• Contract note/trade confirmation
• Ledger statement (date range)
• Holdings statement
• P&L / capital gains report
• Transaction statement
• Charges/brokerage breakup

Customer Profile Updates (Governed)

• Email/mobile update with verification
• Address update with document proof (where applicable)
• Bank account add/change with maker-checker approval
• Nominee update / KYC / FATCA updates (as per operating model)

Order and Trade Inquiries

• Order status/rejection reason
• Trade execution details
• Pending order/modification/cancellation inquiry (status-based; action per policy)
• RMS/margin block explanations (informational) and remediation workflow (if applicable)

Payment and Funds Inquiries

• Pay-in / pay-out status
• Funds not reflected
• Payout failure reason
• Margin shortfall / collateral status inquiry

Module 8 — SLA/TAT Governance, Escalations, and Department Pending Controls

• SLA policies by category and customer segment using business hours + holiday calendars
• Milestones for first response, interim updates, and final resolution (configurable)
• Escalation matrix (L1 → TL → Manager → Head → Escalation Desk) on nearing-breach and breach
• Department pending queues with follow-up reminders and interim customer updates
• Controlled reopen policy within a configurable window with a full audit trail

• Channel-wise inflow/outflow and backlog (Email/Voice/WhatsApp/Web Chat/App/Web API)
• SLA compliance by queue/team/category and breach analysis
• Backlog aging and breach risk heatmap for supervisors
• Escalation + reopen trends; repeat query drivers
• Agent Productivity: response time, resolution time, case throughput, KB usage
• Bot Analytics: deflection rate, top intents, handoff volume, resolution outcomes

• Role-based access controls for L1/L2/TL/Compliance with queue-based visibility
• PII protection via field-level security, masking (where applicable), and strict export controls
• Audit trail for status changes, assignments, approvals, and communications
• Controlled templates + KB approvals to ensure compliant outbound messaging
• Integration logging, retries, DLQ patterns, and reconciliation reports for STP requests

A phased implementation is typically recommended for this solution to realize immediate adoption.

• Phase 1: FSC customer model + Service Cloud case/taxonomy, Email-to-Case, baseline CTI, SLAs, dashboards, Knowledge foundation
• Phase 2: WhatsApp + Website Chatbot with KB-first responses, enhanced routing, supervisor controls, department pending workflows
• Phase 3: Backoffice STP integrations for statement requests and inquiry APIs; then profile updates with maker-checker governance
• Phase 4: Agentforce automation rollout (sentiment, auto-tagging, summarization, drafting) + continuous optimization using analytics