来自 TikTok Shop 官方资料快照 ·
- 当前资料结构化阅读页
- 固定快照已留存,可追溯
- 官方原文可核对
资料正文
§1 Meet Partner Assistant — Your AI Q&A Copilot in Partner Center
Meet Partner Assistant — Your AI Q&A Copilot in Partner Center
§2 1. What is Partner Assistant
1. What is Partner Assistant
Partner Assistant is an AI Q&A copilot built into TikTok Shop Partner Center. Ask it a question in plain language and get an answer without leaving your current page. Partner Assistant helps you understand the docs, diagnose API errors, find the right reference, and check read-only config — then routes you to a human when you need one.
- Knows the docs and the Open Platform.
- Aware of the page you're on, so you don't have to re-explain context.
- A human is one click away anytime via "Submit a Ticket".
§3 2. Where to find it
2. Where to find it
Partner Assistant lives on every page of both the documentation site and the main TTSPC site.
- Look for the floating button — drag it anywhere on screen that suits you.
- Hover over it to see "Ask Partner Assistant for Help".
- Click to open the slide-out drawer on the right side of the page.
<div style="text-align: center"><img src="https://p16-arcosite-sg.ibyteimg.com/tos-alisg-i-k9wyc2ijk0-sg/27e9da0984404bc4bf85ee0a44fab955~tplv-k9wyc2ijk0-image.image" width="800px" /></div>
§4 3. What Partner Assistant can do today — and what it can't yet
3. What Partner Assistant can do today — and what it can't yet
About Partner Assistant today: it's available to all developers and focuses on read-only help — answering questions and looking things up — with answers grounded in the latest published TikTok Shop docs. Write actions are coming later. It can:
- Answer knowledge questions about the platform, APIs, and concepts.
- Diagnose API errors — paste an error code or message and Partner Assistant helps you interpret it.
- Search the documentation and point you to the right page.
- Run read-only config lookups (GET-semantics only) — e.g. your app's current callback URL, subscribed event topics, and granted scopes. It reads these values; it doesn't change them.
It can't yet:
- Write actions — changing configs, subscribing to events, or applying for permissions/scopes.
For anything that requires a write action, Partner Assistant tells you the capability is coming and points you to the right page or to a ticket.
§5 4. How to ask Partner Assistant well
4. How to ask Partner Assistant well
Best for: quick questions about the docs and APIs, decoding an error, finding the right reference page, and checking a read-only config value. Not the right tool for: write actions, or anything needing a human judgment call — send those to a ticket. Example prompts
| You want to… | Try asking |
|---|---|
| Decode an error | "Why does Create Products return error 12345678?" · "What does this Request ID's failure mean?" |
| Find a doc | "Where's the doc for the webhook retry policy?" · "Which API returns a shop's order list?" |
| Understand a concept | "What is shop_cipher and when do I use it?" · "Sandbox shop vs. production shop — what's the difference?" |
| Check read-only config | "What's the current callback URL for my app?" · "Which event topics is my app subscribed to?" |
<div style="text-align: center"><img src="https://p16-arcosite-sg.ibyteimg.com/tos-alisg-i-k9wyc2ijk0-sg/62478c75adc646b89202a8e26895d755~tplv-k9wyc2ijk0-image.image" width="800px" /></div>
What you can give Partner Assistant
- Paste an error code, error message, endpoint name, or Request ID — the more specific, the better the answer.
- Ask in plain language — no special syntax or keywords needed.
- No need to restate which page you're on — Partner Assistant already has it (see Section 5).
What you get back
- A plain-language explanation.
- Links to the relevant documentation.
- A suggested next step.
- A one-click "Submit a Ticket" path when it can't fully resolve your issue.
§6 5. How to use it
5. How to use it
§7 Page-context awareness — don't repeat your page
Page-context awareness — don't repeat your page
Partner Assistant auto-detects the TTSPC page you're on and uses it as context. You'll see a line like:
I see you're on Product API - Create Products.
Just ask your question. No need to say which page or which API you're working with.
§8 Session rules
Session rules
- Reopen on the same page → your conversation continues where you left off.
- Open on a new page (after closing) → starts a fresh session with the new page's context.
- New Chat button → clears the current conversation and starts over.
Partner Assistant has no history list, search, or rename yet. To keep something, use Copy before you start a new chat.
§9 6. Feedback & getting human help
6. Feedback & getting human help
Under every Partner Assistant reply you have:
- 👍 / 👎 — tell us if the answer helped.
- Copy — grab the reply text.
- Regenerate — get another take.
- Submit a Ticket — reach a human.
<div style="text-align: center"><img src="https://p16-arcosite-sg.ibyteimg.com/tos-alisg-i-k9wyc2ijk0-sg/e7a65680e777458fa5a4bdc7f83d5875~tplv-k9wyc2ijk0-image.image" width="800px" /></div>
§10 If Partner Assistant can't answer — what to do next
If Partner Assistant can't answer — what to do next
- Answer looks off or incomplete? Rephrase the question, add the error code or Request ID, or hit Regenerate.
- Still stuck? Hit Submit a Ticket — Partner Assistant drafts it from your conversation and a human takes over.
- Need a write action (changing a config, subscribing to events, applying for permissions/scopes)? Partner Assistant can't do these yet — go straight to Submit a Ticket.
§11 The new ticket flow: chat first, a human always one click away
The new ticket flow: chat first, a human always one click away
The old "directly open a ticket" entry is gone. Every ticket now starts with at least one round of AI Q&A, so your issue reaches a human with context attached. "Submit a Ticket" stays available under replies and in fallback states — a human is always reachable. When you submit, Partner Assistant drafts the ticket from your conversation (a "Summarize & Standardize" step):
- Title — a Summary under 15 words.
- Body — Context (API name / Endpoint / Error Code / Request ID), Steps already tried, and Expected Result.
You can edit everything before sending.
