sales-sendr
Sendr platform help — AI-powered personalized outreach with lipsync video, dynamic landing pages, lead finder (479M+ contacts), and campaign sequencing. Use when setting up Sendr campaigns, lipsync video audio is out of sync, Sendr credits burning too fast, Lead Finder or Data Studio buttons are greyed out, dynamic pages not rendering for prospects, Sendr API or webhook integration not working, or Sendr Zapier automations failing. Do NOT use for general outbound strategy without a platform (use /sales-cadence), or general deliverability without Sendr (use /sales-deliverability).
What this skill does
# Sendr Platform Help
## Step 1 — Gather context
If `references/learnings.md` exists, read it first for accumulated platform knowledge.
Which area of Sendr do you need help with?
1. **Campaigns & sequences** — email campaigns, multi-step sequences, automation triggers
2. **Lipsync video** — recording, personalization, dynamic audio, video generation
3. **Dynamic pages** — personalized landing pages, GIFs, Chrome extension
4. **Lead Finder** — searching the 479M+ contact database, filters, ICP targeting
5. **Data Studio** — enrichment, email verification, personality analysis
6. **Automations** — Zapier flows, Make scenarios, webhook triggers, automation builder
7. **API & webhooks** — REST API, page generation, dynamic audio, video endpoints
8. **Billing & credits** — credit consumption, plan limits, upgrading
9. **Something else** — describe your situation
Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
## Step 2 — Route or answer directly
| Problem domain | Route to |
|---|---|
| General outbound sequence strategy (not Sendr-specific) | `/sales-cadence` |
| Email deliverability fundamentals (SPF/DKIM/DMARC, warmup) | `/sales-deliverability` |
| Enrichment comparison across tools | `/sales-enrich` |
| Building prospect lists across tools | `/sales-prospect-list` |
| CRM selection or comparison | `/sales-crm-selection` |
When routing to another skill, provide the exact command: "This is a {problem domain} question — run: `/sales-{skill} {user's original question}`"
If the question is Sendr-specific, continue to Step 3.
## Step 3 — Sendr platform reference
**Read `references/platform-guide.md`** for the full platform reference — modules, pricing, integrations, data model, workflows.
Answer the user's question using only the relevant section. Don't dump the full reference.
For API questions, **also read `references/sendr-api-reference.md`** for endpoint details.
## Step 4 — Actionable guidance
You no longer need the platform guide — focus on the user's specific situation.
- Start with the simplest solution before suggesting complex workflows
- Reference specific Sendr UI paths or API endpoints
- If a feature is plan-gated (e.g., API access requires Pro), mention which plan
- If you discover a gotcha or workaround not in `references/learnings.md`, append it there
## Gotchas
> *Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.*
- **Credits don't roll over** — unused monthly credits expire at reset. Plan usage carefully
- **Each contact costs ~3 credits** — dynamic audio + website background + landing page each consume a credit. At Growth plan (2,500 credits), that's ~833 personalized contacts/month
- **Lipsync video is not true lip-sync** — the video zooms into a circular bubble over the prospect's website background during personalized audio. This masks the lack of mouth animation. Don't promise full deepfake-style lip-sync to prospects
- **No built-in email warmup** — Sendr relies on external sending tools (Apollo, Instantly, Smartlead) for actual email delivery and warmup. Sendr creates the personalized content; you send it through your existing stack
- **API requires Pro plan ($249/mo)** — Growth plan users can't access API or webhooks. The automation builder is also Pro-only
- **Lead Finder data is 479M+ contacts, refreshed monthly** — accuracy varies by region (US data stronger than international)
- **Support is chatbot-first** — human support may be slow for pre-seed startup (1-10 employees). Community at community.sendr.io exists but is small
- **AppSumo lifetime deal sold out Jan 2026** — new users are on monthly plans only ($97-$249/mo)
## Related skills
- `/sales-cadence` — Multi-channel outbound sequence strategy across all platforms
- `/sales-deliverability` — Email deliverability fundamentals and platform-specific warmup guides
- `/sales-enrich` — Contact enrichment comparison and workflows across all tools
- `/sales-prospect-list` — Building targeted B2B prospect lists across all platforms
- `/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`
## Examples
**Example 1:** "My Sendr lipsync videos have audio out of sync — the prospect's name sounds delayed"
**Example 2:** "I'm burning through 2,500 credits in a week — how do I reduce credit consumption per contact?"
**Example 3:** "How do I use the Sendr API to auto-generate personalized pages when a lead enters my Clay workflow?"
## Troubleshooting
**Lipsync video audio out of sync**
- Sendr uses a zoom-out-to-bubble technique, not true lip animation — slight timing offsets are expected
- Try re-recording the base video with a clear pause where the personalized name will be inserted
- Use the dynamic audio endpoint to preview audio before generating video
- If using ElevenLabs voice ID, check that language code matches the audio content
**Lead Finder / Data Studio buttons greyed out**
- Verify your plan has remaining credits (check Settings → Usage)
- Some operations require specific credit types — lead search vs enrichment vs verification
- Clear browser cache and try again — Chrome extension state can get stale
- Contact support at [email protected] if the issue persists after credit top-up
**Credits burning faster than expected**
- Each personalized contact consumes ~3 credits (dynamic audio + background + page)
- Batch-generate pages via API instead of one-by-one in the UI — API calls are more efficient
- Skip dynamic audio for lower-priority prospects — text-only pages cost fewer credits
- Monitor consumption in your dashboard — credits don't roll over at month end
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".