Q&A Pairs

Add manual question-answer pairs for precise, controlled responses to specific questions.

What Are Q&A Pairs?

Q&A pairs are manually created question-answer entries that give your agent exact answers to specific questions. They take priority over crawled content when there's a strong match.

Use Q&A pairs when you need:

Precise answers for frequently asked questions
Corrections to answers the agent gets wrong
Responses for questions not covered by your website
Company-specific information (pricing, hours, policies)

Adding Q&A Pairs

Open the Knowledge Tab

Navigate to your agent's Sources tab and find the Q&A Pairs section.

Create a Pair

Click Add Q&A Pair and fill in:

Question — write it as a visitor would ask it
Answer — write the exact response you want the agent to give

Q: What are your business hours?
A: We're open Monday through Friday, 9 AM to 6 PM EST.
Weekend support is available via email at support@yoursite.com.

Save and Train

Q&A pairs are embedded and indexed just like other content. They'll be available after the next training cycle completes.

Tip: Write questions in multiple variations. The AI understands semantic similarity, so "What are your hours?" and "When are you open?" will both match a well-written Q&A pair.

Best Practices

Do	Don't
Write natural, conversational questions	Use overly technical or robotic language
Keep answers concise and direct	Write essay-length responses
Include links and contact info	Leave answers vague or generic
Cover common question variations	Duplicate existing website content

Managing Q&A Pairs via API

You can also create Q&A pairs programmatically:

Create a Q&A pair

curl -X POST https://fetchply.com/api/v1/agents/YOUR_AGENT_ID/qa-pairs \
  -H "Authorization: Bearer fp_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "question": "What is your return policy?",
    "answer": "We offer a 30-day money-back guarantee on all plans."
  }'

Deleting Q&A Pairs

Remove pairs you no longer need from the Sources tab. Deleted pairs are removed from the knowledge base on the next training cycle.

On this page