sf-service-messaging-conversation-toolkit

Integrate Salesforce Messaging API for sessions, messages, and agent handoffs.

15|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/sfdc-brendan/Demo-Lab --skill sf-service-messaging-conversation-toolkit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sf-service-messaging-conversation-toolkit
Source: https://github.com/sfdc-brendan/Demo-Lab/tree/main/Service%20Cloud/skills/sf-service-messaging-conversation-toolkit
Command: npx skills add https://github.com/sfdc-brendan/Demo-Lab --skill sf-service-messaging-conversation-toolkit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integrates and standardizes Salesforce Messaging API usage for custom messaging clients.

Core Features & Use Cases

  • Standardized Messaging API integration across channels and sessions
  • Conversation Toolkit for consistent context, transcript continuity, and handoff readiness
  • Handoff orchestration to live agents with routing context and queue management

Quick Start

Configure a Messaging API integration to manage sessions, messages, and agent handoffs.

Frequently Asked Questions about sf-service-messaging-conversation-toolkit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Does the Salesforce Conversation Toolkit support idempotency for messaging API requests?

Yes, the Conversation Toolkit supports idempotency by requiring idempotency keys for messaging API requests. This mechanism handles replays and enforces timeout rules to prevent duplicate messages and ensure auditable conversations.

How do I orchestrate live agent handoffs within Salesforce Service Cloud messaging sessions?

Agent handoffs in Salesforce Service Cloud are orchestrated by routing conversation context and managing queues. This ensures live agents receive full transcript continuity and standardized handoff readiness across all integrated messaging channels.

What is the best way to ensure reliable Salesforce Messaging API integration for custom messaging clients?

Reliable Salesforce Messaging API integration is achieved by imposing idempotency keys, replay handling, and strict timeout rules. This enforces a robust event contract to guarantee auditable conversation sessions across custom clients.

Can I use the Salesforce Conversation Toolkit to standardize messaging across multiple channels?

Yes, custom messaging clients can standardize API usage across multiple channels. The toolkit applies a unified event contract to manage sessions and maintain consistent context regardless of the underlying messaging platform.

Why do my Salesforce conversation sessions drop context during agent routing?

Conversation sessions drop context without standardized event contracts and transcript continuity rules. Applying idempotency and robust replay handling ensures conversation data persists reliably during cross-channel agent routing.

Does the Salesforce Conversation Toolkit support idempotency for messaging API requests?

Yes, the Conversation Toolkit supports idempotency by requiring idempotency keys for messaging API requests. This mechanism handles replays and enforces timeout rules to prevent duplicate messages and ensure auditable conversations.