Salesloft platform help — config, Rhythm, Conversations, Deals, Forecast, Analytics, Drift, integrations, admin, API. Use when Salesloft settings aren't configured right, Rhythm signals feel noisy or unhelpful, Analytics dashboards don't show what you need, Drift chatbots aren't converting, or Salesloft integrations are broken. Do NOT use for building cadences (use /sales-cadence), reviewing calls (use /sales-call-review), inspecting deals (use /sales-deal-inspect), or forecasting (use /sales-forecast).
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Salesloft platform help — config, Rhythm, Conversations, Deals, Forecast, Analytics, Drift, integrations, admin, API. Use when Salesloft settings aren't configured right, Rhythm signals feel noisy or unhelpful, Analytics dashboards don't show what you need, Drift chatbots aren't converting, or Salesloft integrations are broken. Do NOT use for building cadences (use /sales-cadence), reviewing calls (use /sales-call-review), inspecting deals (use /sales-deal-inspect), or forecasting (use /sales-forecast).
Help the user with Salesloft platform questions — from configuration and Rhythm signals through Analytics dashboards, Drift chatbots, and integrations.
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated knowledge.
What's your role? (rep / AE / BDR, sales manager, RevOps / Sales Ops, admin / IT, or other)
What are you trying to accomplish? (describe your specific goal or question)
Note: If the user needs one of the specialized skills (Cadence, call review, deal inspection, forecasting), route them there with a brief explanation of why that skill is a better fit.
Step 2 — Route or answer directly
If the request maps to a specialized skill, route:
Cadence/sequence building → /sales-cadence
Call review/coaching → /sales-call-review
Deal health/risk analysis → /sales-deal-inspect
Revenue forecasting → /sales-forecast
Otherwise, answer directly from platform knowledge using the reference below.
Step 3 — Salesloft platform reference
Provide module-by-module guidance based on the user's area:
Rhythm
What it is: AI-powered workflow engine that prioritizes daily seller actions based on buyer signals
Common configs: Custom report builder, scheduled reports, export settings, team vs. individual views
Best practices: Set up weekly automated reports, track leading indicators (activities) not just lagging (revenue), benchmark reps against team averages
Drift (Conversational Marketing)
What it is: Chatbots, playbooks, live chat, meeting scheduling, site visitor identification
Common configs: Bot playbook builder, routing rules, meeting calendar integration, ABM targeting, Fastlane for qualified leads
Metrics: Conversations started, meetings booked via chat, bot deflection rate, response time
Best practices: Use ABM targeting for high-value accounts, keep bot flows under 4 steps, always offer human handoff, A/B test opening messages
Admin & Settings
User management: Roles, permissions, teams, hierarchies
CRM sync: Salesforce/HubSpot sync settings, field mapping, conflict resolution, sync frequency
SSO: SAML configuration, provisioning
Data management: Import/export, duplicate management, data hygiene
Common issues: Sync conflicts, permission errors, API rate limits
Salesloft data model
Core entities in the Salesloft platform — understand these to navigate the UI, build reports, and work with the API:
Entity
What it represents
Key relationships
Person
An individual prospect or contact
Belongs to an Account, can be enrolled in Cadences
API basics: REST API, authentication (OAuth 2.0), rate limits, common endpoints
Webhooks: Available events, payload structure, retry logic
Common use cases: CRM sync customization, custom reporting, workflow automation, data enrichment
Salesloft API reference
For detailed API documentation including endpoints, rate limits, webhooks, and automation patterns, consult references/api-reference.md.
Quick reference: Base URL https://api.salesloft.com/v2, OAuth 2.0 auth, 600 req/min rate limit. Full docs: https://developers.salesloft.com/
Using Membrane for direct Salesloft access
For Claude to interact with Salesloft directly — pull live data (people, accounts, cadences, emails, calls), create/update records, or automate workflows — install the Membrane Salesloft skill. It handles auth, pagination, and rate limits automatically, so prefer it over raw API calls:
Common configs: Category definitions, submission cadence, rollup rules, override permissions
Best practices: Submit forecasts weekly, use AI forecast as a benchmark, document override reasons
Step 4 — Actionable guidance
Based on the user's specific question:
Step-by-step instructions — numbered steps to accomplish their goal in Salesloft
Configuration recommendations — specific settings to change, with where to find them in the Salesloft UI (Settings > [section] > [page])
Common pitfalls — what can go wrong and how to avoid it
Verification — how to confirm the change worked as expected
Step 5 — Related skills
Point to related skills based on what they asked about:
/sales-cadence — Design and optimize multi-channel outbound cadences, plus general outreach message writing (not Salesloft-specific)
/sales-call-review — Review sales calls and extract coaching insights
/sales-deal-inspect — Inspect individual deal health and identify risks
/sales-forecast — Build and validate revenue forecasts, plus portfolio-level pipeline management and deal prioritization
/sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do
Gotchas
Don't confuse Salesloft "Cadence" with a generic sales cadence concept. Salesloft Cadence is a specific product feature with its own data model (Cadence Memberships, Steps, etc.). When the user says "cadence," clarify whether they mean the Salesloft feature or the general concept of a multi-touch sequence.
Don't recommend deprecated API v1 endpoints. The current Salesloft API is v2 (api.salesloft.com/v2). Claude defaults to v1 patterns from older training data — always use v2.
Don't assume all Salesloft orgs have Drift enabled. Drift is a separate product that was acquired and integrated. Many Salesloft customers don't have it. Ask before referencing Drift features.
Don't confuse Salesloft Deals with CRM Opportunities. Deals in Salesloft are synced from the CRM — they are not the source of truth. Changes should usually be made in the CRM, not in Salesloft Deals directly.
Don't suggest Rhythm configurations that don't exist. Signal weighting and play creation have specific options in the UI — don't invent settings or suggest configurations that aren't available in the current product.
Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.
Examples
Example 1: Rhythm configuration
User says: "How do I set up Rhythm signals to prioritize inbound leads?"
Skill does:
Identifies this as a Rhythm configuration question
Provides step-by-step instructions for signal weighting in Settings > Rhythm
Recommends best practices for inbound vs. outbound signal priority
Result: User has configured Rhythm signals with recommended weighting
Example 2: CRM sync troubleshooting
User says: "My Salesloft-Salesforce sync keeps creating duplicates"
Skill does:
Identifies this as an Admin/CRM sync issue
Walks through sync settings, field mapping, and conflict resolution
Identifies common duplicate causes and fixes
Result: User has diagnosed and resolved the duplicate creation issue
Troubleshooting
Salesloft MCP not connecting
If using the Membrane Salesloft skill and connections fail:
Verify your OAuth token is valid and not expired
Check API rate limits — 600 cost/minute at the team level (shared across all integrations, not per user)
Ensure the Membrane CLI is authenticated: membrane login --tenant
CRM sync conflicts
Symptom: Records overwritten or duplicated between Salesloft and CRM
Cause: Bidirectional sync with conflicting field mappings
Solution: Review Settings > CRM Sync > Field Mapping. Set conflict resolution to "CRM wins" for fields your CRM owns, "Salesloft wins" for activity data.
Rhythm signals not appearing
Symptom: Focus zone is empty despite active cadences and deals
Cause: Signal sources not connected or signal weights set to zero
Solution: Check Settings > Rhythm > Signal Sources. Ensure Cadence, Deals, and email tracking are enabled.
