sales-omnisend

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Omnisend Platform Help

Omnisend 平台帮助

Help the user with Omnisend platform questions — from email/SMS campaign setup and automation workflows through popups, segmentation, reporting, ecommerce integrations, and API.

为用户解答Omnisend平台相关问题——覆盖邮件/SMS活动搭建、自动化工作流、弹窗、受众分群、报表、电商集成、API等全场景。

Step 1 — Gather context

步骤1 — 收集上下文

Ask the user:

What area of Omnisend do you need help with?
- A) Email campaigns — creating, designing, sending broadcasts
- B) SMS campaigns — setting up SMS marketing
- C) Automation workflows — welcome, cart abandonment, browse abandonment, win-back, custom
- D) Popups & forms — signup forms, exit-intent, wheel of fortune
- E) Segmentation — creating segments, targeting by behavior/purchase history
- F) Web push notifications — browser push setup and campaigns
- G) Reporting & analytics — campaign performance, revenue attribution
- H) Integrations — Shopify, WooCommerce, BigCommerce, Zapier, API
- I) Deliverability — domain authentication, warmup, sender reputation
- 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.

询问用户以下信息：

你需要Omnisend哪个模块的帮助？
- A) 邮件营销活动——创建、设计、发送广播邮件
- B) SMS营销活动——搭建SMS营销体系
- C) 自动化工作流——欢迎序列、弃购挽回、浏览挽留、赢回客户、自定义流程
- D) 弹窗与表单——注册表单、退出意图弹窗、幸运大转盘
- E) 受众分群——创建用户分群、按行为/购买历史定向触达
- F) 网页推送通知——浏览器推送设置与活动搭建
- G) 报表与分析——活动表现、收入归因
- H) 集成——Shopify、WooCommerce、BigCommerce、Zapier、API
- I) 送达率——域名认证、账号预热、发件人信誉
- J) 管理后台——账单、套餐权益、账户设置
- K) 其他——请描述具体问题
你使用的电商平台是什么？
- A) Shopify
- B) WooCommerce
- C) BigCommerce
- D) Wix
- E) 自定义/其他
- F) 未使用电商平台
你想要实现什么目标？（请描述具体的目标或问题）

**如果用户的请求已经提供了大部分上下文，可以直接跳转到对应的步骤。**优先基于合理假设（需明确说明假设内容）给出尽力而为的回答，最后仅补充1-2个最关键的澄清问题即可——不要等收集完所有信息再回复用户。

Step 2 — Route or answer directly

步骤2 — 路由或直接解答

If the request maps to a specialized skill, route:

Email marketing strategy (platform-agnostic) →
```
/sales-email-marketing
```
SMS marketing strategy (platform-agnostic) →
```
/sales-sms-marketing
```
Cross-platform deliverability →
```
/sales-deliverability
```
Push notification strategy →
```
/sales-push-notification
```
Tool integration architecture →
```
/sales-integration
```
List/audience growth strategy →
```
/sales-audience-growth
```

Otherwise, answer directly from platform knowledge using the reference below.

如果用户请求对应更专业的技能，请引导到对应模块：

邮件营销策略（平台无关）→
```
/sales-email-marketing
```
SMS营销策略（平台无关）→
```
/sales-sms-marketing
```
跨平台送达率问题 →
```
/sales-deliverability
```
推送通知策略 →
```
/sales-push-notification
```
工具集成架构 →
```
/sales-integration
```
列表/受众增长策略 →
```
/sales-audience-growth
```

否则基于下方的平台知识库直接回答用户问题。

Step 3 — Omnisend platform reference

步骤3 — Omnisend平台参考手册

Email Campaigns

邮件营销活动

What it is: Broadcasts sent to contacts or segments — newsletters, promotions, product announcements
Editor: Drag-and-drop email editor with 250+ templates, product picker (pulls from your store), dynamic discount codes, product recommendations
A/B testing: Test subject lines, sender name, and content on Standard+ plans. Split audience automatically, send winner to remainder.
Campaign Booster: Auto-resend campaign to non-openers with a different subject line after a configurable delay
Best practices: Use product recommendation blocks for ecommerce. Segment by engagement. A/B test subject lines on every campaign.

定义：发送给联系人或用户分群的广播内容——包括新闻资讯、促销活动、产品公告等
编辑器：拖拽式邮件编辑器，内置250+模板、产品选择器（可从店铺同步商品）、动态折扣码、产品推荐功能
A/B testing：Standard及以上套餐支持测试主题、发件人名称、内容。自动拆分受众，将表现更优的版本发送给剩余受众
Campaign Booster：可配置延迟时间，自动给未打开邮件的用户重新发送带有不同主题的活动邮件
最佳实践：电商场景建议使用产品推荐模块；按用户 engagement 分群触达；每次活动都做主题行A/B测试

SMS Marketing

SMS营销

What it is: SMS campaigns and automated SMS messages sent to opted-in contacts
Opt-in: Separate SMS consent required (not inherited from email opt-in). Collect via popups, checkout, or keyword opt-in.
SMS credits: Pro plan includes SMS credits; Standard plan has SMS as paid add-on. Credits vary by country.
Character limits: 160 chars (GSM-7) or 70 chars (Unicode). Messages over limit split into multiple segments at higher cost.
MMS: Supported — include images in SMS messages for higher engagement
Two-way SMS: Contacts can reply to SMS messages. Replies visible in Omnisend.
Compliance: TCPA compliance built in — automatic quiet hours, opt-out handling ("STOP" keyword), consent tracking

定义：发送给已授权联系人的SMS营销活动和自动短信
授权要求：需要单独收集SMS授权（不能继承邮件授权），可通过弹窗、结账页、关键词授权收集
SMS额度：Pro套餐包含SMS额度；Standard套餐需额外购买SMS增值服务；额度按国家不同有所差异
字符限制：GSM-7编码下160字符，Unicode编码下70字符，超出限制的消息会被拆分为多条发送，成本更高
MMS：支持在短信中添加图片提升 engagement
双向SMS：联系人可回复短信，回复内容可在Omnisend中查看
合规性：内置TCPA合规支持——自动静默时段、退订处理（"STOP"关键词）、授权记录追踪

Automation Workflows

自动化工作流

What it is: Trigger-based automated message sequences — the core of Omnisend's value
Pre-built workflows (ready to activate):
- Welcome series (new subscriber)
- Abandoned cart (cart created, not completed)
- Browse abandonment (product/category viewed, no purchase)
- Order confirmation & shipping updates
- Post-purchase follow-up (review request, cross-sell)
- Win-back / re-engagement (lapsed customer)
- Birthday / anniversary
- Back-in-stock notification
Custom workflows: Build from scratch with any trigger + conditions + actions
Multi-channel: Each workflow step can be email, SMS, or web push — mix channels in one automation
Splits and conditions: A/B split testing within workflows, conditional branches based on segment membership, purchase history, engagement
Timing: Configurable delays between steps (minutes, hours, days)
Exit conditions: Auto-remove contacts from workflow when they take the desired action (purchase, resubscribe)

定义：基于触发条件的自动消息序列，是Omnisend的核心价值点
预置工作流（可直接激活使用）：
- 欢迎序列（新订阅用户）
- 弃购挽回（创建购物车但未完成支付）
- 浏览挽留（查看产品/分类但未购买）
- 订单确认与物流更新
- 购后跟进（评价请求、交叉销售）
- 赢回/二次触达（流失客户）
- 生日/周年纪念
- 补货通知
自定义工作流：可从零搭建，支持任意触发条件+判断条件+执行动作
多渠道：每个工作流步骤可以是邮件、SMS、网页推送——单个自动化流程可混合使用多个渠道
拆分与条件判断：工作流内支持A/B拆分测试，可基于用户分群归属、购买历史、engagement设置条件分支
时间配置：步骤之间可配置延迟（分钟、小时、天）
退出条件：当用户完成目标动作（购买、重新订阅）时自动从工作流中移除

Popups & Forms

弹窗与表单

Types: Popup, embedded form, landing page, Wheel of Fortune (gamified spin-to-win), teaser (small persistent trigger)
Targeting: Show based on URL, device, referral source, time on page, scroll depth, exit intent, new vs returning visitor
Multi-step forms: Collect email first, then SMS on a second step (increases overall opt-in rate)
Discount delivery: Auto-apply discount codes to form submissions
A/B testing: Test form design, copy, and offers

类型：弹窗、嵌入表单、落地页、幸运大转盘（游戏化抽奖）、 teaser（常驻小型触发按钮）
触达规则：可基于URL、设备、引流来源、页面停留时长、滚动深度、退出意图、新/老访客展示
多步表单：先收集邮箱，第二步再收集SMS授权（提升整体授权率）
折扣发放：表单提交后可自动发放折扣码
A/B testing：可测试表单设计、文案、活动权益

Segmentation

受众分群

Segment types: Based on shopping behavior (purchased, viewed, added to cart), email/SMS engagement (opened, clicked, subscribed date), contact properties (tags, location, custom fields), and campaign activity
Dynamic segments: Auto-update as contacts match/unmatch conditions
Lifecycle stages: Omnisend auto-assigns lifecycle stages — New Subscriber, Active Customer, At Risk, Lapsed, Champions
Product-based segments: Contacts who bought/viewed specific products or categories
RFM analysis: Built-in Recency-Frequency-Monetary scoring for customer value segmentation

分群类型：可基于购物行为（购买、浏览、加购）、邮件/SMS engagement（打开、点击、订阅时间）、联系人属性（标签、地理位置、自定义字段）、活动参与情况分群
动态分群：当联系人满足/不再满足分群条件时自动更新
生命周期阶段：Omnisend自动分配生命周期阶段——新订阅用户、活跃客户、高风险流失、已流失、核心客户
基于产品的分群：购买/浏览过特定产品或分类的联系人
RFM分析：内置最近消费时间/消费频次/消费金额评分，用于客户价值分群

Web Push Notifications

网页推送通知

What it is: Browser push notifications to opted-in website visitors
Unlimited on all plans: Including free plan — no extra cost
Triggers: Manual send or automation workflow step
Content: Title, message, image, URL, action buttons
Limitation: Web push only — no native mobile app push (use with Shopify's native push or a dedicated push tool for mobile)

定义：发送给已授权网站访客的浏览器推送通知
所有套餐无限制使用：包括免费套餐，无额外成本
触发方式：手动发送或作为自动化工作流的步骤触发
内容配置：标题、消息、图片、跳转URL、行动按钮
限制：仅支持网页推送，不支持原生移动端App推送（移动端推送可搭配Shopify原生推送或专用推送工具使用）

Reporting & Analytics

报表与分析

Campaign reports: Opens, clicks, unsubscribes, revenue attributed per campaign
Automation reports: Revenue per workflow, conversion rate, per-step performance
Sales dashboard: Revenue attribution across all channels (email, SMS, push), customer lifetime value trends
Segment performance: Compare performance across segments
Click maps: Visual heatmap of where contacts click in your emails

活动报表：每个活动的打开、点击、退订、归因收入数据
自动化报表：每个工作流的收入、转化率、单步骤表现数据
销售看板：全渠道（邮件、SMS、推送）收入归因、客户终身价值趋势
分群表现：对比不同用户分群的表现差异
点击热力图：可视化展示联系人在邮件中的点击位置

Omnisend data model

Omnisend数据模型

Core entities — understand these to navigate the UI and work with the API:

Entity	What it represents	Key relationships
Contact	A person in your audience (email, phone, or both)	Has Tags, belongs to Segments, has Events
Campaign	A one-time email/SMS broadcast	Sent to a Segment or list of Contacts
Automation (Workflow)	A trigger-based multi-step sequence	Contains Steps (email, SMS, push, delay, split)
Product	A product from your ecommerce store	Synced from Shopify/WooCommerce/BigCommerce
Order	A completed purchase	Belongs to a Contact, contains Products
Event	A tracked action (page view, cart, purchase)	Belongs to a Contact, triggers Automations
Segment	A dynamic group of contacts based on rules	Used as campaign audience or workflow condition
Form	A popup, embedded form, or landing page	Creates/tags Contacts on submission

核心实体——理解这些实体可帮助你操作UI和使用API：

实体	代表含义	核心关联关系
Contact	你的受众中的单个用户（可包含邮箱、手机号或两者都有）	拥有标签、属于某个分群、关联事件
Campaign	一次性的邮件/SMS广播	发送给某个分群或联系人列表
Automation (Workflow)	基于触发条件的多步骤序列	包含多个步骤（邮件、SMS、推送、延迟、拆分）
Product	你的电商店铺中的商品	从Shopify/WooCommerce/BigCommerce同步
Order	已完成的购买订单	属于某个联系人、包含多个产品
Event	被追踪的用户行为（页面浏览、加购、购买）	属于某个联系人、可触发自动化流程
Segment	基于规则的动态联系人群组	用作活动受众或工作流判断条件
Form	弹窗、嵌入表单或落地页	提交时创建/标记联系人

API & Integrations

API与集成

For detailed API documentation including all endpoints, authentication, rate limits, and data models, always consult
references/omnisend-api-reference.md
. Point the user to this file for the full endpoint catalog, request/response schemas, and rate limit details.

Quick reference: Base URL

https://api.omnisend.com/api/

, API key auth (

X-API-KEY

header), header-based versioning (

Omnisend-Version: 2026-03-15

), cursor-based pagination. Key capabilities: contact management, campaign CRUD, product sync, event tracking, segment management, analytics.

如需包含所有端点、鉴权、限流、数据模型的完整API文档，请始终参考
references/omnisend-api-reference.md
。可引导用户查看该文件获取完整的端点目录、请求/响应 schema、限流规则详情。

快速参考：Base URL

https://api.omnisend.com/api/

，API密钥鉴权（

X-API-KEY

请求头）、基于请求头的版本控制（

Omnisend-Version: 2026-03-15

）、游标分页。核心能力：联系人管理、活动CRUD、产品同步、事件追踪、分群管理、分析数据获取。

Native integrations

原生集成

Ecommerce: Shopify (deep — products, orders, carts, customers, browse events), WooCommerce (plugin), BigCommerce (native), Wix, Ecwid
Ecommerce features: Product sync, order sync, cart tracking, browse tracking, customer data sync, revenue attribution
Automation: Zapier (triggers for new subscriber, new order; actions for adding contacts), Make
Reviews: Shopify product reviews, Loox, Judge.me, Yotpo, Stamped
Loyalty: Smile.io, LoyaltyLion
Other: Google Ads (audience sync), Facebook Ads (audience sync), Gorgias, Zendesk

电商平台：Shopify（深度集成——产品、订单、购物车、客户、浏览事件）、WooCommerce（插件）、BigCommerce（原生集成）、Wix、Ecwid
电商功能：产品同步、订单同步、购物车追踪、浏览追踪、客户数据同步、收入归因
自动化工具：Zapier（新订阅用户、新订单触发；添加联系人动作）、Make
评价工具：Shopify产品评价、Loox、Judge.me、Yotpo、Stamped
忠诚度工具：Smile.io、LoyaltyLion
其他：Google Ads（受众同步）、Facebook Ads（受众同步）、Gorgias、Zendesk

Pricing (as of April 2026 — verify current pricing)

定价（2026年4月数据——请核实最新定价）

Free: 250 contacts, 500 emails/mo, unlimited web push, all features, 60 SMS credits
Standard: From $16/mo (500 contacts, 6,000 emails/mo, SMS add-on)
Pro: From $59/mo (unlimited emails, advanced reporting, higher SMS allowance)
Scales by contact count. 30% discount for 3-month prepay on first subscription.

Free：250个联系人、每月500封邮件、无限制网页推送、全功能可用、60条SMS额度
Standard：每月16美元起（500个联系人、每月6000封邮件、SMS为增值服务）
Pro：每月59美元起（无限制邮件、高级报表、更高SMS额度）
定价随联系人数量阶梯上涨，首次订阅按季度预付可享30%折扣

Step 4 — Actionable guidance

步骤4 — 可落地的指导建议

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
```
."

基于用户的具体问题提供以下内容：

分步操作指引：带有Omnisend UI导航路径的编号操作步骤
配置建议：需要修改的具体设置项
常见陷阱：可能出现的问题以及规避方法
验证方法：如何确认修改已生效
API相关问题：始终补充提示：「如需完整的端点目录、请求/响应 schema 和限流规则，请查看
```
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 SMS credits. Standard plan requires SMS credits as a paid add-on. Pro plan includes SMS credits but they're country-dependent and limited. Always check the user's plan 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.

基于调研的最佳实践——请仔细查看，尤其是套餐限制功能、集成相关可能过时的注意点

不要混淆「campaign」和「automation」：在Omnisend中，campaign是一次性广播，automation（workflow）是基于触发条件的序列。用户询问campaign时Claude经常会给出automation的建议，反之亦然，请多加注意
不要默认所有套餐都包含SMS服务：免费套餐仅包含60条SMS额度，Standard套餐需要额外购买SMS增值服务，Pro套餐包含的SMS额度有国家限制且总量有限。推荐SMS工作流前请先确认用户的套餐类型
不要跳过SMS授权环节：Omnisend要求单独收集SMS授权，邮箱授权不能等同于SMS权限。推荐使用多步弹窗（先收集邮箱，再收集SMS授权）的方案
不要推荐不在用户套餐范围内的功能：Campaign Booster、高级报表、更高SMS额度都是套餐限制功能，自动化的A/B测试需要Standard及以上套餐
不要忽略电商平台连接状态：大部分Omnisend功能都依赖活跃的电商集成，产品推荐、弃购挽回、浏览挽留、基于订单的分群都需要从Shopify/WooCommerce/BigCommerce同步产品/订单数据

Step 5 — Related skills

步骤5 — 相关技能

```
/sales-email-marketing
```
— Cross-platform email marketing strategy (broadcasts, nurture, automation, segmentation)
```
/sales-sms-marketing
```
— Cross-platform SMS marketing strategy (opt-in, compliance, campaign types)
```
/sales-deliverability
```
— Cross-platform email deliverability — SPF/DKIM/DMARC, warmup, inbox placement
```
/sales-push-notification
```
— Cross-platform push notification strategy (opt-in, timing, frequency)
```
/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 --skills sales-do
```

```
/sales-email-marketing
```
—— 跨平台邮件营销策略（广播、培育、自动化、分群）
```
/sales-sms-marketing
```
—— 跨平台SMS营销策略（授权、合规、活动类型）
```
/sales-deliverability
```
—— 跨平台邮件送达率——SPF/DKIM/DMARC、账号预热、收件箱 placement
```
/sales-push-notification
```
—— 跨平台推送通知策略（授权、时机、频率）
```
/sales-audience-growth
```
—— 增长邮件/SMS列表（诱饵、弹窗、交叉推广）
```
/sales-integration
```
—— 通过webhook、Zapier或API连接Omnisend与其他工具
```
/sales-klaviyo
```
—— Klaviyo平台帮助（如果用户使用Klaviyo而非Omnisend）
```
/sales-mailchimp
```
—— Mailchimp平台帮助（如果用户使用Mailchimp而非Omnisend）
```
/sales-do
```
—— 不确定该使用哪个技能？路由工具会将任何销售目标匹配到合适的技能。安装命令：
```
npx skills add sales-skills/sales --skills sales-do
```

Examples

示例

Example 1: Cart abandonment automation

示例1：弃购挽回自动化

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

用户问题：「我怎么在Omnisend里搭建弃购挽回邮件？」 技能响应逻辑：

确认用户已连接电商平台（需要Shopify/WooCommerce/BigCommerce）
引导用户启用预置的弃购挽回工作流：自动化 > 预置工作流 > 弃购挽回
推荐3步序列：1小时后发送邮件（提醒+产品图）、24小时后发送邮件（社交证明）、48小时后发送SMS（紧迫感+折扣）
解释退出条件（购买后自动停止）和拆分测试选项结果：用户成功启用多渠道弃购挽回自动化流程

Example 2: Setting up SMS marketing

示例2：搭建SMS营销

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)
Configures SMS compliance settings (quiet hours, STOP keyword handling)
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

用户问题：「我想在Omnisend里开始发送SMS营销活动，我用的是Shopify，套餐是Standard。」 技能响应逻辑：

说明Standard套餐需要额外购买SMS额度
引导用户搭建SMS授权收集流程：创建多步弹窗（先收集邮箱→再收集SMS授权）
配置SMS合规设置（静默时段、STOP关键词处理）
展示如何在现有自动化工作流中添加SMS步骤
提示用户注意字符限制和不同国家的额度成本结果：用户完成SMS授权收集配置、合规设置，已将SMS添加到核心自动化流程

Example 3: API product sync

示例3：API产品同步

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
Covers authentication (X-API-KEY header) and versioning (Omnisend-Version header)
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

用户问题：「我用的是自定义电商平台，需要通过API把产品和订单同步到Omnisend。」 技能响应逻辑：

引导用户查看
```
references/omnisend-api-reference.md
```
获取完整API文档
解释产品和订单端点——POST请求同步商品库，POST事件跟踪订单
说明鉴权方式（X-API-KEY请求头）和版本控制（Omnisend-Version请求头）
展示如何在没有原生集成的情况下发送自定义事件用于购物车/浏览追踪结果：用户获得产品同步、订单跟踪、基于事件的自动化的API集成方案

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.

症状：活动打开率低于15% 原因：未分群直接发送给全量列表、缺少域名认证、主题行质量差 解决方案：认证发件域名（设置 > 发件人域名——添加SPF/DKIM/DMARC记录）；按engagement分群——优先发送给过去90天活跃的联系人；使用Campaign Booster自动给未打开用户重发邮件；做主题行A/B测试。完整诊断请参考

/sales-deliverability

Automation not triggering

自动化未触发

Symptom: Workflow is active but contacts aren't entering Cause: Trigger conditions not met, ecommerce platform not connected, or contacts don't match entry conditions Solution: Check that the ecommerce integration is active and syncing (Settings > Integrations). Verify the trigger event is firing (check Events tab on a test contact). Ensure the workflow's audience filter isn't excluding contacts. Test with a known contact by triggering the event manually.

症状：工作流已激活但没有用户进入原因：未满足触发条件、未连接电商平台、用户不满足进入条件 解决方案：检查电商集成是否处于活跃同步状态（设置 > 集成）；验证触发事件是否正常触发（在测试联系人的事件标签页查看）；确认工作流的受众过滤规则没有排除用户；手动触发事件用已知联系人测试

SMS credits running out fast

SMS额度消耗过快

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.

症状：SMS额度消耗速度远快于预期原因：消息超出160字符（被拆分为多条）、发送给国际号码（额度成本更高）、自动化发送频率过高 解决方案：保持SMS内容在160字符以内（使用GSM-7编码——避免emoji和特殊字符，否则会切换为Unicode编码仅支持70字符）；在设置 > SMS中查看不同国家的额度成本；检查自动化发送频率——在SMS步骤之间添加频率限制或冷却期