tw-ecom-operations-line-oa

asgard-ai-platform ｜ 行銷與 SEO ｜ 原文 ｜ MIT

用 LINE 官方帳號做會員 CRM：群發、標籤、圖文選單（內文待補）

---
name: "tw-ecom-operations-line-oa"
description: "透過 LINE 官方帳號做 CRM 與會員留存：群發成本模型、圖文選單、自動回覆、標籤、一對一聊天，以及 LINE Pay 整合。當要為台灣品牌設計 LINE OA 策略、為群發分眾會員，或衡量 LINE OA 的 ROI 時使用。一般的 CRM「不要」用這個（用 `ecom-rfm-analysis` 或 `biz-cac-ltv`）。STATUS: SKELETON — 內文待補。"
metadata:
  category: "WP-01 電商"
  domain: "ecommerce-tw"
  layer: "operations"
  related_mcps: []
  related_skills: ["ecom-rfm-analysis", "biz-cac-ltv", "tw-ecom-compliance-pdpa"]
  last_verified: "2026-04"
  status: "skeleton"
  tags: ["taiwan", "e-commerce", "crm", "line-oa"]
---

# LINE OA CRM 營運

> **STATUS: SKELETON**：內文待補。

## 何時使用這個 skill

- 為台灣品牌設計 LINE OA 策略
- 設定圖文選單、自動回覆、標籤
- 為群發分眾會員
- 把 LINE Pay 整合進 OA 流程
- 衡量 LINE OA 對比 EDM 的 ROI

## 何時「不要」使用

- 一般 RFM → `ecom-rfm-analysis`
- CAC/LTV 框架 → `biz-cac-ltv`

## 核心概念

TODO: LINE OA 方案定價（輕用量 / 中用量 / 高用量）、群發 vs 分眾發送的成本不對稱、標籤策略。

## 決策樹

TODO: 會員行為 → 標籤 → 通路。

## 實作指引

TODO: 導入流程、標籤邏輯、群發範本、ROI 衡量。

## 常見陷阱

TODO: 5-6 個陷阱（月中升級方案的成本、封鎖用戶造成名單膨脹、群發的個資法同意、尖峰時段的一對一延遲、LINE Notify 停用的影響）。

## IRON LAW

TODO.

## 輸出格式

TODO.

## 相關

- `ecom-rfm-analysis`
- `tw-ecom-compliance-pdpa`

_Last verified: 2026-04_

---
name: "tw-ecom-operations-line-oa"
description: "Run CRM and member retention via LINE Official Account — broadcast cost model, rich menu, auto-response, tagging, 1-to-1 chat, and LINE Pay integration. Use when designing LINE OA strategy for a TW brand, segmenting members for broadcasts, or measuring LINE OA ROI. Do NOT use for generic CRM (use `ecom-rfm-analysis` or `biz-cac-ltv`). STATUS: SKELETON — body pending."
metadata:
  category: "WP-01 電商"
  domain: "ecommerce-tw"
  layer: "operations"
  related_mcps: []
  related_skills: ["ecom-rfm-analysis", "biz-cac-ltv", "tw-ecom-compliance-pdpa"]
  last_verified: "2026-04"
  status: "skeleton"
  tags: ["taiwan", "e-commerce", "crm", "line-oa"]
---

# LINE OA CRM Operations

> **STATUS: SKELETON** — body pending.

## When to use this skill

- Designing LINE OA strategy for a TW brand
- Setting up rich menu, auto-response, tagging
- Segmenting members for broadcasts
- Integrating LINE Pay into OA flow
- Measuring LINE OA ROI vs EDM

## Do NOT use when

- Generic RFM → `ecom-rfm-analysis`
- CAC/LTV framework → `biz-cac-ltv`

## Core concepts

TODO: LINE OA tier pricing (輕用量 / 中用量 / 高用量), broadcast vs narrowcast cost asymmetry, tagging strategy.

## Decision tree

TODO: member behavior → tag → channel.

## Implementation guidance

TODO: onboarding flow, tagging logic, broadcast template, ROI measurement.

## Gotchas

TODO: 5-6 pitfalls (tier upgrade mid-month cost, blocked-user bloat, PDPA consent for broadcast, 1-to-1 latency during peak, LINE Notify deprecation impact).

## IRON LAW

TODO.

## Output Format

TODO.

## Related

- `ecom-rfm-analysis`
- `tw-ecom-compliance-pdpa`

_Last verified: 2026-04_