> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.beatapi.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.beatapi.io/_mcp/server.

# How should I hand Douyin comments to teammates without losing exact text and sources?

> Keep quotes, summaries and decisions separate, preserving provenance, thread roles, duplicates and missing states while the automatic CSV mapping remains unverified.

Organize saved Douyin comments into a UTF-8 CSV with one row per comment. From the saved response, keep the video ID, the comment ID, the exact wording, the parent relationship and the request ID. Put your interpretation and the next step in separate columns. To fetch comments first, start with the [video comment guide](/guides/douyin-video-comments). The table is built by hand from saved responses; an automatic converter first needs a verified field mapping (see the last section).

For example, for the comment “Can I install this shelf in a rental without drilling?”, keep the quote verbatim and group the comment under “No-drill installation.” Write “Check supported wall types in the installation guide” in the next-step column. Give your teammate the original response so the teammate can verify the quote.

## What should the working table preserve?

| Information          | How to record it                                                   | Purpose                                                                |
| -------------------- | ------------------------------------------------------------------ | ---------------------------------------------------------------------- |
| Video/comment source | Original link, confirmed IDs, raw file, request ID and actual time | Trace the material to its observation.                                 |
| Exact statement      | Text actually returned, verbatim                                   | Verify evidence rather than replacing it with an AI summary.           |
| Role and context     | Verified root/reply role, parent relationship and missing context  | Avoid counting replies as independent roots or guessing relationships. |
| Summarized question  | Human interpretation in a separate column                          | Distinguish the author's expression from our reading.                  |
| Review decision      | Included/excluded/unverified with reason                           | Keep more than the rows supporting a preferred conclusion.             |
| Next action          | Context reading, condition checks or clearer instructions          | Turn material into research work.                                      |

Fill a cell only with information the response provides or that you verified. Mark missing text, missing IDs and missing relationships separately. Similar names or similar wording do not show that two rows are the same person or the same record.

## What errors should I avoid when merging pages?

Deduplicate by verified comment ID together with the video the comment belongs to, and keep every raw file and every observation. When two versions of the same comment conflict, keep both versions for review instead of silently choosing one text. Report root-comment coverage and reply coverage separately; a reply that appears both in a preview and in a separate reply query counts once.

Leave missing like counts empty and keep a real zero as 0. A row count is not a count of people, and a missing row does not prove the comment was deleted. In the delivery notes, state the date window, the pages actually read, the ordering and the reason you stopped; do not multiply the requested `count` by the number of pages to claim completion.

## What should a teammate be able to spot-check?

Pick a row and find the same video, the same comment and the exact quote in the original response. Check that the summary stays within the statement and that no reply corrects the statement. Reconcile the included, excluded and unverified counts with the actual records, and list the scope nobody read.

When a comment asks a **hypothetical** compatibility question, do not rewrite the question as a confirmed product failure. When a comment quotes a third party's experience, do not record the experience as the author's own purchase. Mark unsupported detail as unresolved instead of asking a model to fill the detail in.

Import IDs as text so spreadsheet software does not alter long identifiers. Treat comments that start with formula characters as text in spreadsheets, and keep the original wording in the raw files. Remove private details before sharing, and keep the raw material internal.

## What remains for automatic export?

An automatic converter first needs the real list path, IDs, text, relationships and pagination of `data:douyin.app.v3.fetch_video_comments` verified, plus tests for missing values, duplicates, failures and protection of old output files. This page supplies no script with guessed paths and does not reuse another platform's `data.items` mapping.

Inspect `data:douyin.app.v3.fetch_video_comments` for free to check the current status, inputs and price. Rereading saved material, relabeling rows and exporting a manual CSV add no query; new pages, replies and other actions are separate calls.