FAQ | Gastx Content Admin

Primary fields

Question, answer, locale

问题、回答、语种、分类、优先级和支持 CTA 都应集中维护。

User angle

Friction removal

目标是降低购买疑虑和重复咨询，不是堆砌知识文章。

Live entries

14 FAQ entries are now served from a local JSON file.

Last updated: 2026-05-04T13:45:00.000Z

Why rent Energy instead of burning TRX every transfer?

If you move USDT often, renting Energy is usually cheaper and more predictable than repeatedly burning TRX.

en · energy-basic · published

为什么频繁转账时更适合租能量，而不是每次都燃烧 TRX？

如果你经常转 USDT，租能量通常比反复燃烧 TRX 更省，也更容易预估成本。

zh-CN · energy-basic · published

How do I judge whether renting Energy is worth it for my transfers?

Compare your expected transfer count and urgency with the cost of burning TRX. The more often you send, the more likely renting is the better deal.

en · energy-basic · published

高级源文件维护

Source payload

{
  "version": 1,
  "collection": "faq",
  "updatedAt": "2026-05-04T13:45:00.000Z",
  "records": [
    {
      "id": "faq-energy-vs-burn",
      "slug": "energy-vs-burn",
      "locale": "en",
      "category": "energy-basic",
      "audienceSegment": "regular-user",
      "question": "Why rent Energy instead of burning TRX every transfer?",
      "shortAnswer": "If you move USDT often, renting Energy is usually cheaper and more predictable than repeatedly burning TRX.",
      "detailedAnswer": "Renting Energy makes sense when transfer frequency is high, when you want a clearer operating cost, or when you need a stable path for batch transfers. Burning TRX is simpler for one-off actions, but repeated transfers can become more expensive and harder to budget.",
      "primaryCta": "to-pricing",
      "relatedKnowledgeSlugs": [
        "what-is-tron-energy"
      ],
      "visibleChannels": [
        "organic",
        "google"
      ],
      "sortOrder": 10,
      "status": "published",
      "updatedAt": "2026-05-04T13:20:00.000Z"
    },
    {
      "id": "faq-energy-vs-burn-zh",
      "slug": "energy-vs-burn-zh",
      "locale": "zh-CN",
      "category": "energy-basic",
      "audienceSegment": "regular-user",
      "question": "为什么频繁转账时更适合租能量，而不是每次都燃烧 TRX？",
      "shortAnswer": "如果你经常转 USDT，租能量通常比反复燃烧 TRX 更省，也更容易预估成本。",
      "detailedAnswer": "当转账频率较高、需要控制成本波动，或者要支持连续与批量操作时，租能量更合适。一次性小额操作直接燃烧 TRX 更省事，但高频场景下总成本通常更难控制。",
      "primaryCta": "to-pricing",
      "relatedKnowledgeSlugs": [
        "what-is-tron-energy"
      ],
      "visibleChannels": [
        "organic",
        "google"
      ],
      "sortOrder": 12,
      "status": "published",
      "updatedAt": "2026-05-04T13:45:00.000Z"
    },
    {
      "id": "faq-price-decision",
      "slug": "price-decision",
      "locale": "en",
      "category": "energy-basic",
      "audienceSegment": "mixed",
      "question": "How do I judge whether renting Energy is worth it for my transfers?",
      "shortAnswer": "Compare your expected transfer count and urgency with the cost of burning TRX. The more often you send, the more likely renting is the better deal.",
      "detailedAnswer": "A simple rule is to compare one rental cycle with the TRX you would otherwise burn across the same number of transfers. Renting is usually a better choice when you send repeatedly, need steadier unit economics, or want to avoid cost spikes during active periods.",
      "primaryCta": "to-pricing",
      "relatedKnowledgeSlugs": [
        "what-is-tron-energy"
      ],
      "visibleChannels": [
        "organic",
        "google"
      ],
      "sortOrder": 14,
      "status": "published",
      "updatedAt": "2026-05-04T13:45:00.000Z"
    },
    {
      "id": "faq-price-decision-zh",
      "slug": "price-decision-zh",
      "locale": "zh-CN",
      "category": "energy-basic",
      "audienceSegment": "mixed",
      "question": "怎么判断我的场景适不适合租能量？",
      "shortAnswer": "把预计转账次数、时效要求和直接燃烧 TRX 的成本放在一起比较；越高频，越可能适合租能量。",
      "detailedAnswer": "可以按一个租赁周期内的预计转账量，去对比如果全部直接燃烧 TRX 会花多少。若你有连续转账、批量代发、需要稳定成本或不想在忙时被链上波动放大费用，租能量通常更合适。",
      "primaryCta": "to-pricing",
      "relatedKnowledgeSlugs": [
        "what-is-tron-energy"
      ],
      "visibleChannels": [
        "organic",
        "google"
      ],
      "sortOrder": 16,
      "status": "published",
      "updatedAt": "2026-05-04T13:45:00.000Z"
    },
    {
      "id": "faq-route-selection",
      "slug": "route-selection",
      "locale": "en",
      "category": "routing",
      "audienceSegment": "mixed",
      "question": "Should I buy on the site, use the TG bot, or integrate the API?",
      "shortAnswer": "Manual users should start on the site, chat-driven buyers can use the TG bot, and stable programmatic demand should use the API.",
      "detailedAnswer": "The web path is best for first-time and occasional buyers. The TG bot is suited to operators who prefer chat notifications and repeat actions. The API path is for teams that need batching, status callbacks, and tighter automation in their own platform.",
      "primaryCta": "to-api",
      "relatedKnowledgeSlugs": [
        "buy-energy-via-api"
      ],
      "visibleChannels": [
        "organic",
        "google",
        "telegram"
      ],
      "sortOrder": 20,
      "status": "published",
      "updatedAt": "2026-05-04T13:20:00.000Z"
    },
    {
      "id": "faq-route-selection-zh",
      "slug": "route-selection-zh",
      "locale": "zh-CN",
      "category": "routing",
      "audienceSegment": "mixed",
      "question": "我该走网页下单、TG 机器人，还是直接接 API？",
      "shortAnswer": "人工偶发购买优先网页，偏聊天式操作可用 TG，稳定程序化需求应直接接 API。",
      "detailedAnswer": "网页适合首次购买、偶发使用和需要直观看价格的人。TG 机器人适合习惯在聊天里完成下单和接收提醒的操作者。API 更适合团队、商户和系统集成场景，尤其是要做批量、回调、自动化分发时。",
      "primaryCta": "to-api",
      "relatedKnowledgeSlugs": [
        "buy-energy-via-api"
      ],
      "visibleChannels": [
        "organic",
        "google",
        "telegram"
      ],
      "sortOrder": 22,
      "status": "published",
      "updatedAt": "2026-05-04T13:45:00.000Z"
    },
    {
      "id": "faq-partnership-path",
      "slug": "partnership-path",
      "locale": "en",
      "category": "routing",
      "audienceSegment": "partner",
      "question": "What should I do if I want a long-term or business partnership?",
      "shortAnswer": "If you need recurring volume, settlement coordination, or workflow integration, move from the retail path to the business contact or API path.",
      "detailedAnswer": "The self-serve site is fine for testing demand, but repeat commercial usage usually needs a more stable cooperation path. If you need volume planning, dedicated support, custom settlement flow, or platform integration, the business or API route is the right next step.",
      "primaryCta": "to-api",
      "relatedKnowledgeSlugs": [
        "buy-energy-via-api"
      ],
      "visibleChannels": [
        "organic",
        "google",
        "telegram"
      ],
      "sortOrder": 24,
      "status": "published",
      "updatedAt": "2026-05-04T13:45:00.000Z"
    },
    {
      "id": "faq-partnership-path-zh",
      "slug": "partnership-path-zh",
      "locale": "zh-CN",
      "category": "routing",
      "audienceSegment": "partner",
      "question": "如果我想长期合作或商务接入，应该走哪条路径？",
      "shortAnswer": "如果你有持续量级、结算协同或系统集成需求，应从零售自助路径转到商务或 API 路径。",
      "detailedAnswer": "网页自助更适合先验证需求，但长期稳定采购通常需要更明确的合作方式。如果你关心批量额度、对接支持、结算流程或平台嵌入，应该优先走商务沟通或 API 接入路径，而不是长期停留在临时手工下单。",
      "primaryCta": "to-api",
      "relatedKnowledgeSlugs": [
        "buy-energy-via-api"
      ],
      "visibleChannels": [
        "organic",
        "google",
        "telegram"
      ],
      "sortOrder": 26,
      "status": "published",
      "updatedAt": "2026-05-04T13:45:00.000Z"
    },
    {
      "id": "faq-energy-arrival-time",
      "slug": "energy-arrival-time",
      "locale": "en",
      "category": "troubleshooting",
      "audienceSegment": "regular-user",
      "question": "How long does it usually take for rented Energy to arrive?",
      "shortAnswer": "Most users should expect a short wait, but exact timing depends on order processing and chain conditions.",
      "detailedAnswer": "Energy normally arrives quickly after the order is accepted, but there can still be brief delays from processing queues, address validation, or network conditions. If you are operating on a tight deadline, check the order status first before retrying transfers or opening a support request.",
      "primaryCta": "to-help",
      "relatedKnowledgeSlugs": [
        "transfer-still-fails-after-rental"
      ],
      "visibleChannels": [
        "organic",
        "telegram"
      ],
      "sortOrder": 28,
      "status": "published",
      "updatedAt": "2026-05-04T13:45:00.000Z"
    },
    {
      "id": "faq-energy-arrival-time-zh",
      "slug": "energy-arrival-time-zh",
      "locale": "zh-CN",
      "category": "troubleshooting",
      "audienceSegment": "regular-user",
      "question": "租的能量一般多久到账？",
      "shortAnswer": "多数场景下到账很快，但具体时机仍会受订单处理和链上状态影响。",
      "detailedAnswer": "订单被受理后通常会较快到账，但也可能因为处理队列、地址校验或网络波动出现短时延迟。如果你有时效要求，建议先看订单状态，再决定是否重试转账或联系支持，而不是立即重复下单。",
      "primaryCta": "to-help",
      "relatedKnowledgeSlugs": [
        "transfer-still-fails-after-rental"
      ],
      "visibleChannels": [
        "organic",
        "telegram"
      ],
      "sortOrder": 29,
      "status": "published",
      "updatedAt": "2026-05-04T13:45:00.000Z"
    },
    {
      "id": "faq-transfer-fail-after-rental",
      "slug": "transfer-fail-after-rental",
      "locale": "zh-CN",
      "category": "troubleshooting",
      "audienceSegment": "regular-user",
      "question": "租了能量后为什么转账还是失败？",
      "shortAnswer": "通常要先检查资源到账时机、地址状态、带宽和转账金额是否超出预估。",
      "detailedAnswer": "先确认租赁是否已经到账，再检查目标地址是否处于可用状态，以及当前操作是否同时需要带宽和能量。对于批量或高频转账，还要确认预估模型是否覆盖了真实链上波动和附加操作成本。",
      "primaryCta": "to-help",
      "relatedKnowledgeSlugs": [
        "transfer-still-fails-after-rental"
      ],
      "visibleChannels": [
        "organic",
        "telegram"
      ],
      "sortOrder": 30,
      "status": "published",
      "updatedAt": "2026-05-04T13:20:00.000Z"
    },
    {
      "id": "faq-transfer-fail-after-rental-en",
      "slug": "transfer-fail-after-rental-en",
      "locale": "en",
      "category": "troubleshooting",
      "audienceSegment": "regular-user",
      "question": "Why did my transfer still fail after I rented Energy?",
      "shortAnswer": "Check whether the Energy has arrived, whether bandwidth is also required, and whether the transfer pattern costs more than expected.",
      "detailedAnswer": "A failed transfer after rental usually points to timing, address state, or resource mix. Confirm the rental is already active, then check whether the wallet also needs bandwidth, whether the address is valid for the operation, and whether extra contract steps or batch actions pushed the real cost above the estimate.",
      "primaryCta": "to-help",
      "relatedKnowledgeSlugs": [
        "transfer-still-fails-after-rental"
      ],
      "visibleChannels": [
        "organic",
        "telegram"
      ],
      "sortOrder": 32,
      "status": "published",
      "updatedAt": "2026-05-04T13:45:00.000Z"
    },
    {
      "id": "faq-batch-usage",
      "slug": "batch-usage",
      "locale": "en",
      "category": "troubleshooting",
      "audienceSegment": "batch-user",
      "question": "Can I use rented Energy for batch transfers or repeated sends?",
      "shortAnswer": "Yes, but batch usage needs better estimation, enough balance for complementary resources, and a route that matches your automation level.",
      "detailedAnswer": "Batch and repeated transfers are one of the strongest reasons to rent Energy, but they also make estimation mistakes more visible. You should verify transfer frequency, timing window, bandwidth needs, and whether the web, TG, or API path fits the way your operation actually runs.",
      "primaryCta": "to-api",
      "relatedKnowledgeSlugs": [
        "buy-energy-via-api"
      ],
      "visibleChannels": [
        "organic",
        "google",
        "telegram"
      ],
      "sortOrder": 34,
      "status": "published",
      "updatedAt": "2026-05-04T13:45:00.000Z"
    },
    {
      "id": "faq-batch-usage-zh",
      "slug": "batch-usage-zh",
      "locale": "zh-CN",
      "category": "troubleshooting",
      "audienceSegment": "batch-user",
      "question": "租来的能量可以用于批量转账或连续代发吗？",
      "shortAnswer": "可以，但批量场景更依赖准确预估、补充资源准备，以及正确选择网页、TG 或 API 路径。",
      "detailedAnswer": "批量和连续转账正是租能量最常见的使用场景之一，但也最容易暴露资源估算不足。你需要同时确认转账频率、时间窗口、带宽补充，以及当前业务更适合手工下单、聊天式操作还是 API 自动化接入。",
      "primaryCta": "to-api",
      "relatedKnowledgeSlugs": [
        "buy-energy-via-api"
      ],
      "visibleChannels": [
        "organic",
        "google",
        "telegram"
      ],
      "sortOrder": 36,
      "status": "published",
      "updatedAt": "2026-05-04T13:45:00.000Z"
    }
  ]
}

Frontend Contract

前台接线目标

服务官网 FAQ、购买疑虑自助判断和帮助中心的短问答集合。

Consumer

gastx-web /[locale]/faq 与首页 FAQ 摘要区块

Primary key: slug

Status field: status

Collection shape

后续前台应按这个集合形状取数，而不是继续在页面里硬编码文案常量。

Fields: 14

Records: 3

Schema

统一内容 schema

Field	Type	Required	Notes
id Record ID	string	Required	后台内部标识，不暴露给最终 URL。
slug Slug	string	Required	前台锚点、筛选或知识文章回链用。
locale Locale	enum	Required	与前台语言段一一对应。
category Category	enum	Required	例如 payment、energy-basic、api、tg-bot。
audienceSegment Audience segment	enum	Required	普通用户、批量用户、开发者、代理合作。
question Question	string	Required	列表展示标题。
shortAnswer Short answer	text	Required	用于摘要和首页引用。
detailedAnswer Detailed answer	rich-text	Required	用于 FAQ 详情内容。
primaryCta Primary CTA	string	Optional	例如 to-pricing、to-bot、to-api。
relatedKnowledgeSlugs Related knowledge slugs	string[]	Optional	关联知识文章。
visibleChannels Visible channels	string[]	Optional	为投放页裁剪问答集合。
sortOrder Sort order	number	Optional	前台固定排序。
status Status	enum	Required	draft、review、ready、published。
updatedAt Updated at	date-time	Required	前台可显示 freshness 标记。

Records

用于前台替换静态内容的记录

解释租赁相较直接燃烧更省成本，适合频繁 USDT 转账用户。

Categoryenergy-basic
Audienceregular-user
CTAto-pricing
Related knowledgewhat-is-tron-energy

按手动用户、批量运营和程序化接入三类场景分流。

Categoryrouting
Audiencemixed
CTAto-api
Visible channelsorganic, google, telegram

说明资源到账时机、地址状态和带宽/能量不足的排查路径。

Categorytroubleshooting
Audienceregular-user
CTAto-help
Related knowledgetransfer-still-fails-after-rental

Editor

编辑面板

先把编辑器分区收口，后续不论接真实 CMS 还是 API，都能按这个面板结构推进。

Identity & routing

定义 slug、语种、分类和目标受众，保证前台能做稳定分组。

slug
locale
category
audienceSegment
sortOrder

Answer payload

把短回答和详细回答拆开，便于首页、FAQ 页和弹层复用。

question
shortAnswer
detailedAnswer
relatedKnowledgeSlugs

Conversion hooks

内容页只声明 CTA 与支持升级，不接真实客服工单。

primaryCta
visibleChannels
status
updatedAt

Module Flow

上下游协作关系

Upstream inputs

Locale Content确认哪些语种必须同步 FAQ。Site Settings复用统一支持入口和 CTA 目标。

Feeds into

Knowledge复杂问题跳转到知识文章或教程。Channel Landing按渠道裁剪问答和风险说明。

Checkpoints

运营收口要求

每条 FAQ 要明确适用语种、目标受众和升级入口。
付款、TG Bot、API、批量购买类问题要有清晰分流。
不要把 FAQ 扩成客服工单或售后处理台。

Field Planning

第一阶段字段边界

Core copy

Question
Short answer
Detailed answer
Audience segment
Locale

Publishing

Status
Category
Priority
Sort order
Visible channels

Support hooks

CTA label
CTA target
Related article
Escalation note

Workflow

内容工作流说明

Draft

Content editor

录入文案、FAQ、SEO 字段和基础 CTA，不在这里接真实业务执行。

Review

SEO / Growth ops

检查索引策略、多语言一致性、渠道文案边界和合规提示。

Ready

Site owner

确认发布窗口、关联页面和投放节奏，避免内容与渠道错配。

Publish

System hook later

后续由 CMS 发布流或内容 API 接管；当前阶段只保留流程说明。

Future Hooks

后续扩展预留

后续可接真实 FAQ 分类树、富文本答案和内链推荐，但不把它扩成客服工单系统。
可为 TG Bot、API、付款说明和代理合作预留 FAQ 受众标签。
发布态后续可接审核记录与版本历史，但当前先保持说明级骨架。

FAQ management