Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Help the user with Omnisend platform questions — from email/SMS campaign setup and automation workflows through popups, segmentation, reporting, ecommerce integrations, and API.
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated knowledge.
Ask the user:
What area of Omnisend do you need help with?
A) Email campaigns — creating, designing, sending broadcasts
J) Admin — billing, plan features, account settings
K) Something else — describe it
What's your ecommerce platform?
A) Shopify
B) WooCommerce
C) BigCommerce
D) Wix
E) Custom / other
F) Not using ecommerce
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.
Step 2 — Route or answer directly
If the request maps to a specialized skill, route:
Otherwise, answer directly from platform knowledge using the reference below.
Step 3 — Omnisend platform reference
Read references/platform-guide.md for detailed module documentation, pricing, integrations, and data model.
You no longer need the platform guide details — focus on the user's specific situation.
Step 4 — Actionable guidance
Based on the user's specific question:
Step-by-step instructions — numbered steps with Omnisend UI navigation paths
Configuration recommendations — specific settings to change
Common pitfalls — what can go wrong and how to avoid it
Verification — how to confirm the change worked
For API questions — always include a pointer: "For the full endpoint catalog, request/response schemas, and rate limits, see references/omnisend-api-reference.md."
Gotchas
Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
Don't confuse "campaign" with "automation." In Omnisend, a campaign is a one-time broadcast. An automation (workflow) is a trigger-based sequence. Claude often generates automation advice when the user asks about campaigns and vice versa.
Don't assume SMS is included on all plans. The Free plan has only 60 trial SMS. As of May 4, 2026 SMS is a volume-based add-on (from ~$0.007/SMS) on both Standard and Pro — Pro no longer bundles SMS credits equal to the subscription price (that legacy benefit was retired). Per-message cost is destination-country-dependent. Legacy/grandfathered accounts may still see the old model. Always check the user's plan and SMS billing before recommending SMS workflows.
Don't skip SMS consent. Omnisend requires separate SMS opt-in consent. Email opt-in does NOT grant SMS permission. Multi-step popups (email first, then SMS) are the recommended approach.
Don't recommend features without checking the plan. Campaign Booster, advanced reporting, and higher SMS allowances are plan-gated. A/B testing for automations requires Standard+.
Don't overlook the ecommerce platform connection. Most Omnisend features depend on an active ecommerce integration. Product recommendations, cart abandonment, browse abandonment, and order-based segments all require product/order data syncing from Shopify/WooCommerce/BigCommerce.
Segment-based audience filters can silently block automations. If a workflow uses a segment-based audience filter, there's a race condition: it can take 1-2 minutes for a contact to be added to a segment, but the automation trigger fires immediately. The contact isn't in the segment yet → exits the workflow. Use contact property filters instead of segment filters for time-sensitive triggers, or add a short delay before the filter check.
Template customization has real limits. G2's top complaint about Omnisend is limited design control. If the user needs pixel-perfect layouts or highly custom visual elements, set expectations early — Omnisend trades deep design flexibility for ease of use. For advanced designs, suggest coding custom HTML templates or using a dedicated email design tool and importing.
Reporting is shallower than Klaviyo. Users migrating from Klaviyo frequently miss the depth of analytics — custom reporting, data visualization, cohort analysis. If the user needs advanced reporting, recommend exporting data to Google Sheets/Looker or using the API to build custom dashboards.
Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.
/sales-audience-growth — Growing your email/SMS list (lead magnets, popups, cross-promotion)
/sales-integration — Connect Omnisend to other tools via webhooks, Zapier, or API
/sales-klaviyo — Klaviyo platform help (if using Klaviyo instead of Omnisend)
/sales-mailchimp — Mailchimp platform help (if using Mailchimp instead of Omnisend)
/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: Cart abandonment automation
User says: "How do I set up abandoned cart emails in Omnisend?"
Skill does:
Confirms ecommerce platform is connected (Shopify/WooCommerce/BigCommerce required)
Walks through enabling the pre-built Abandoned Cart workflow: Automation > Pre-built Workflows > Abandoned Cart
Recommends 3-step sequence: email at 1 hour (reminder + product image), email at 24 hours (social proof), SMS at 48 hours (urgency + discount)
Explains exit conditions (auto-stop on purchase) and split testing options
Result: User has abandoned cart automation active with multi-channel sequence
Example 2: Setting up SMS marketing
User says: "I want to start sending SMS campaigns in Omnisend. I'm on the Standard plan with Shopify."
Skill does:
Explains SMS credit add-on requirement for Standard plan
Walks through SMS opt-in setup: create a multi-step popup (email → SMS consent)
Shows how to add SMS steps to existing automation workflows
Warns about character limits and per-country credit costs
Result: User has SMS opt-in collection, compliance configured, and SMS added to key automations
Example 3: API product sync
User says: "I'm on a custom ecommerce platform and need to sync products and orders to Omnisend via API"
Skill does:
Points to references/omnisend-api-reference.md for full API docs
Explains Product and Order endpoints — POST to sync catalog, POST events for order tracking
Shows how to send custom events for cart/browse tracking without a native integration
Result: User has an API integration plan for product sync, order tracking, and event-based automation
Troubleshooting
Low open rates on campaigns
Symptom: Campaign open rates below 15%
Cause: Sending to full list without segmentation, missing domain authentication, or poor subject lines
Solution: Authenticate your sending domain (Settings > Sender Domains — add SPF/DKIM/DMARC). Segment by engagement — send to 90-day active contacts first. Use Campaign Booster to auto-resend to non-openers. A/B test subject lines. See /sales-deliverability for a full diagnosis.
Automation not triggering
Symptom: Workflow is active but contacts aren't entering
Cause: Trigger conditions not met, ecommerce platform not connected, contacts don't match entry conditions, or segment-based filter race condition
Solution: Each trigger has four stages contacts must pass in sequence: Trigger & Trigger Filters → Audience Filters → Frequency → Exit Conditions. Use the Trigger Preview Tool to identify which stage blocked entry. Common culprits:
Workflow not published — unpublished workflows don't fire, even if events occur. Click Start Workflow.
Ecommerce integration disconnected — check Settings > Integrations is active and syncing.
Segment-based audience filter timing — if the workflow uses a segment filter, contacts may not be in the segment yet when the trigger fires (1-2 min delay). Switch to contact property filters or add a delay before the filter.
Multi-channel subscription gaps — in a workflow with email + SMS steps, contacts not subscribed to SMS will skip those steps. Check Workflow Channel Settings.
Exit conditions firing early — if the exit condition (e.g., "placed order") is met before the first message sends, the contact exits silently.
Verify by checking the Events tab on a test contact to confirm the trigger event is firing.
Double order confirmation emails (Omnisend + Shopify)
Symptom: Customers receive two order confirmation emails — one from Omnisend and one from Shopify
Cause: Both Omnisend's transactional automation and Shopify's built-in order notification are active
Solution: Disable one of them. If using Omnisend's order confirmation automation (recommended — more customizable), go to Shopify Admin > Settings > Notifications > Order Confirmation and uncheck the notification. If using Shopify POS, note that POS order confirmations are separate from online order confirmations — you may need to disable both.
Subscriber count mismatch between Omnisend and Shopify
Symptom: Omnisend shows more (or fewer) subscribers than Shopify's customer list
Cause: Omnisend and Shopify track subscriptions independently. Omnisend collects subscribers via its own popups/forms that may not sync back to Shopify's marketing consent field. Conversely, Shopify customers who opt in at checkout may not immediately appear in Omnisend if the sync is delayed.
Solution: Check Settings > Integrations > Shopify and verify the sync is active. For contacts collected via Omnisend forms, they'll be in Omnisend but may not have Shopify marketing consent. For an accurate count, treat Omnisend as your source of truth for email marketing subscribers.
SMS credits running out fast
Symptom: SMS credits depleted faster than expected
Cause: Messages exceeding 160 characters (split into multiple segments), sending to international numbers (higher credit cost), or automation sending more frequently than expected
Solution: Keep SMS messages under 160 characters (GSM-7 encoding — avoid emojis and special characters which switch to Unicode at 70 chars). Check per-country credit costs in Settings > SMS. Review automation frequency — add rate limiting or cooldown periods between SMS steps.
