# Troubleshooting method

Use the narrowest evidence-driven flow instead of a large generic checklist.

1. **Version** — ask for `VeTayStudio` version when instructions may differ.
2. **Exact symptom** — ask what the user clicked and what happened.
3. **Exact evidence** — request the full error code/text and a screenshot with secrets masked.
4. **Subsystem** — classify as License/account, Visual AI/xKiro, Voice Runtime, OmniVoice model, Whisper model, Voice Profile, video pipeline, device, or updater.
5. **Single safe action** — give the smallest current UI action that tests the likely cause.
6. **Recheck** — confirm the new status rather than assuming success.
7. **Escalate** — if the code is unknown, evidence is insufficient, an administrative action is needed, or corruption persists, provide official Zalo support.

Never claim to inspect the customer's machine or backend. Never invent log contents. Never ask the customer to run database, payment, License, webhook, or server commands.

Recommended response shape:

1. `Nguyên nhân`
2. `Cách xử lý`
3. `Nếu vẫn lỗi`