sales-reply

name	sales-reply
description	Reply.io platform help — multichannel sequences (email, LinkedIn, calls, SMS, WhatsApp), Jason AI SDR, B2B database, email warmup, deliverability tools, unified inbox, analytics, Salesforce/HubSpot integration, agency features. Use when Reply.io emails are landing in spam, sequences aren't getting replies, Jason AI isn't handling responses correctly, warmup isn't improving sender reputation, or Reply.io data isn't syncing to your CRM. Do NOT use for general outbound cadence strategy (use /sales-cadence), cross-platform email deliverability (use /sales-deliverability), email tracking strategy (use /sales-email-tracking), building prospect lists (use /sales-prospect-list), or connecting Reply.io to other tools via Zapier (use /sales-integration).
argument-hint	[describe what you need help with in Reply.io]
license	MIT
version	1.0.0
tags	["sales","outbound","cold-email","sequences","platform"]
github	https://github.com/replyio

Reply.io Platform Help

Help the user with Reply.io platform questions — from multichannel sequence setup and Jason AI SDR through B2B database, email warmup, deliverability, unified inbox, analytics, integrations, and agency features.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated knowledge.

Ask the user:

1. What area of Reply.io do you need help with?

   • A) Sequences — creating, managing, or optimizing multichannel sequences
   • B) Jason AI SDR — configuring the autonomous AI agent for prospecting and reply handling
   • C) Deliverability — email warmup, domain health, SPF/DKIM/DMARC, branded links
   • D) Integrations — Salesforce, HubSpot, Pipedrive, Zapier, Make, n8n
   • E) Analytics — sequence performance, channel efficiency, team reporting
   • F) Agency — managing multiple clients, agency-specific features
   • G) B2B Database — finding contacts, email finder, Chrome extension, data credits
   • H) Unified Inbox — managing conversations across channels
   • I) Templates — creating, sharing, and tracking message templates
   • J) API — automation, programmatic access, webhooks
   • K) Something else — describe it

2. What's your role?

   • A) Sales rep / AE / BDR
   • B) Sales manager / team lead
   • C) RevOps / Sales Ops
   • D) Admin / IT
   • E) Agency owner / operator
   • F) Founder / solo seller
   • G) Other

3. What are you trying to accomplish? (describe your specific goal or question)

If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.

Note: If the user needs a specialized skill, 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 strategy / sequence design → /sales-cadence
• Cross-platform email deliverability → /sales-deliverability
• Email tracking strategy → /sales-email-tracking
• List building / prospecting strategy → /sales-prospect-list