Tw Ecom Operations Line Oa

---
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_