wuling-overseas-dealer-expansion-skill/references/facebook-conversation-sync.md

Facebook Conversation Sync

Use this reference when the user asks to read Facebook/Messenger replies, translate customer messages into Chinese, or write Facebook reply records back to the outreach workbook.

Source Of Customers

Read matched customers from 客户信息汇总表, not from a separate Facebook channel sheet. Match by Facebook主页链接, Messenger thread ID when known, Page slug, Page ID, and company name. If a thread cannot be reliably matched to a summary-table customer, skip it and report the reason.

Unified Reply Definition

Unified Facebook reply definition: the Skill no longer distinguishes reply quality. Any real customer-side Messenger reply is counted as Facebook回复. Reply rate, dashboard metrics, and workbook status are based only on whether the customer replied, not on reply quality, cooperation intent level, or deal probability.

Count as Facebook reply:

• Customer-side real text message.
• Customer-side voice, image, file, attachment, or other message that clearly comes from the customer.

Do not count as Facebook reply:

• Our sent messages.
• Read receipts.
• Facebook/Messenger system notices.
• Automated page prompts.
• Pure likes/reactions or standalone emoji without business content.

Conversation Sheet

Write message records to the separate event-log Sheet Facebook对话记录:

记录ID, 客户序号, 客户姓名/公司, Facebook主页链接, Messenger线程ID, 消息时间, 消息方向, 发件人, 原文语言, 对话原文, 中文翻译, 消息类型, 是否有效客户回复, 合作意向, 意向判断依据, 下一步建议, 同步时间, 来源账号/Profile ID, 风险标记

This Sheet stores message history only. It is not a customer source sheet and must never be counted as customer rows in 客户信息汇总表.

For backward compatibility, keep 合作意向 and 意向判断依据 columns in the event-log Sheet, but do not require them and do not use them for reply-rate, dashboard, or customer status. 是否有效客户回复=? means "customer real reply" under the unified reply definition, not reply quality.

Workbook Write-Back

Preserve both sides' original text. Translate non-Chinese customer messages to Chinese. Write the latest customer reply summary back to the matched row in 客户信息汇总表.

• 建联状态: set or merge Facebook已回复.
• 备注: replace the structured Facebook回复记录 block with latest reply time, Chinese summary, and next manual-review suggestion.
• 下次跟进: only write a date if the analysis explicitly provides one; otherwise keep the existing value.
• Do not write cooperation intent levels as the main customer status. If old analysis files contain intent fields, keep them out of summary-table status metrics.
• Do not erase existing email status or email evidence.

Safety

Read only. Do not send replies, reactions, attachments, or follow-up messages. Use AdsPower + Playwright for browser access and keep the browser open.