Chatling Response Quality Checklist

Before sending an answer, check whether it meets these standards.

The answer should:

• Directly address the customer's question.
• Name the product and platform when known.
• Separate confirmed facts from likely next steps.
• Avoid vague advice such as "check everything" or "try updating" unless the KB gives a specific update path.
• Include ordered steps when there is a procedure.
• Include a success signal or expected result.
• Include what to send support if the steps fail.
• Avoid promising outcomes that require human review.
• Avoid internal labels like ticket id, audit note, KB Sync, Freshdesk private note, Shopify lookup, or automation.

For setup answers, include:

• Required hardware or adapter.
• Correct connection path.
• Mode or firmware state when relevant.
• Platform-specific limitation.
• How to test that the setup works.

For troubleshooting answers, include:

• The simplest test first.
• A way to isolate hardware vs software vs configuration.
• A reversible fix before opening hardware or changing firmware.
• A support handoff with photos or video if the issue continues.

For compatibility answers, include:

• Whether the KB says the combination is supported.
• Required adapter or mode.
• Known limitations.
• What the customer should test before assuming the product is defective.

If the answer cannot pass this checklist because the KB is missing information, say that support should review the specific setup and ask for the minimum details needed.