Knowledge & Replies
This covers the two kinds of saved answers: FAQs, which the AI retrieves to answer customers, and canned responses, which your agents reuse by hand. They serve different audiences — one automates the reply, the other speeds up a human — and the Copilot manages both.
| Audience | Used by | |
|---|---|---|
| FAQ | The customer | The AI, automatically |
| Canned response | The agent (drafting a reply) | A human, on demand |
FAQs
Add, update, delete, or check the business knowledge-base answers the AI draws on — including fixed "if the customer says X, reply Y" rules for questions that must always be answered a specific, approved way.
"Add an FAQ: our return window is 30 days." "When customers ask about COD availability, tell them it's available above ₹500." "Update the shipping-time FAQ to say 5–7 business days." "Add a fixed reply for warranty questions pointing to the registration page." "Delete the duplicate gift-card FAQ and keep the newer one."
The Copilot proposes FAQ changes on an FAQ card and saves nothing until you accept them. Each item shows what it does: Add, Merge (an update to an existing FAQ), Delete, Skipped (already covered) or Needs info. Accept or reject items one at a time, or use Accept All. An accepted item shows as Accepted (or Deleted) and can't be accepted again, even after you reload the page, so the same FAQ is never saved twice.
- Deleting FAQs. The Copilot deletes an FAQ only when you ask it to delete or remove one, never as a way to change it. A Delete item shows the full question and answer that will be removed. You can name the FAQ by its question or by its id. If the Copilot can't find the FAQ you named, it says so instead of guessing. When the Copilot applies a delete itself (with auto-apply on), Undo under Applied changes puts the FAQ back with the same question and answer. A delete you accept on the card can't be undone, so check the question and answer first.
- When the Copilot can't make a change (for example, every item is already covered), the reply lists why for each item. If working out the FAQ changes takes too long, it says that nothing was changed and asks you to try again with fewer FAQs at once.
Keep FAQ answers specific and approved — the AI uses them verbatim as its source of truth, so a vague or outdated entry becomes a vague or outdated customer reply. Review them whenever a policy, price, or product detail changes.
The FAQ prompt (business prompt)
Separate from the entries themselves, there's an optional FAQ prompt — a short description of which topics should always be answered from the knowledge base (for example, "returns, refunds, warranty, shipping timelines, and store policy"). It's set once for the business, not per FAQ. When a customer's message touches those topics, the AI is required to search the knowledge base first instead of answering from general knowledge. Leave it blank to let the AI decide on its own. See Knowledge Base (FAQs) for the full explanation.
Canned responses
Agent-facing saved replies and macros — the canned responses a human can drop into a reply while handling a ticket. Unlike FAQs, these aren't sent automatically; an agent chooses them.
The Copilot can make a response available in chat, email, or both. An email response only needs the saved body when it is created through the Copilot; a subject is not required.
"Save a canned response for asking the customer to share a screenshot." "Add a canned reply that apologizes for a delayed delivery and asks for the order id." "Create a macro for confirming a refund has been initiated." "Save this reply for email only: We have received your documents and will review them shortly." "Make the refund confirmation available in both chat and email."
Policies with Copilot
Once your account has policies, the Copilot can write and maintain them: short sections that state one business rule and why, linked to the flows, settings, FAQs and data points that carry it out. It proposes a Policies card for you to save. It can also confirm a policy that was flagged for review once you say the flagged change is fine.
The Copilot doesn't write an account's first policies. Generate them from Generate policies in the Copilot workspace's Policies tab and save the ones you keep; after that, the Copilot can add and change policies.
"Write a refunds policy from our Refund request flow and the refund FAQs." "Refunds are now accepted for 10 days instead of 7. Update the policy and everything that uses it." "The COD policy needs review. Is the flow wrong, or the policy?"
Policies state the rule, not how a flow is built, so the Copilot keeps flow steps in the flow. Before it changes something a policy links to, it reads the policy and tells you if the change would contradict it.
When a rule change touches both a policy and a flow, the flow change is a draft until you publish it. The policy change waits for that publish, so a policy never tells customers a rule the live flow doesn't follow yet. The Policies card says which flow it's waiting for.
Which one to use
- If the AI should answer the customer directly and consistently → FAQ.
- If a human agent needs a reusable, ready-to-send reply → canned response.
- If you want one record of a business rule and why, checked against the configuration that carries it out → policy.
- If you're pasting mixed content — some policy facts plus flow-style instructions — the Copilot will split the facts into FAQs and the instructions into flows, so ask for both in one go.
Related
- Knowledge Base (FAQs) — the FAQ store the AI answers from, and the FAQ prompt.
- Settings → Canned Responses — agent reply macros.
- Policies — business rules linked to your configuration.
- Copilot overview