1. When Ask ADZA Does Not Return an Answer

If Ask ADZA does not return a response, this is usually due to one of the following:

• The question is outside the system’s current scope
• The query is too vague or difficult to interpret
• There is insufficient data available to generate a response

What you can do:

Start by simplifying your question. Focus on one variable at a time and make the query more specific.

For example, instead of asking:

“Tell me about agriculture in Africa”

Try:
“What are the main crops produced in Nigeria?”

If the issue persists, it may indicate that the system does not currently support that type of query.

2. When the Answer Is Too General

If the response feels too broad or lacks detail, it is often because the query itself is too general.

Ask ADZA responds based on how clearly the question maps to available data.

What you can do:

Refine your question by:

• Adding a specific country
• Including a timeframe
• Focusing on a single crop or variable

For example:

Instead of:

“Tell me about maize”

Ask:
“How has maize production in Kenya changed over the last five years?”

More specific queries produce more precise outputs.

3. When the Answer Feels Incomplete

An incomplete answer may reflect:

• Limited data availability
• Partial coverage in the dataset
• The system prioritizing clarity over speculation

What you can do:

Break your question into smaller parts.

For example:

Instead of asking a complex, multi-layered question, ask:

• One question about production
• Another about prices
• Another about trends

This allows you to build a more complete picture step by step.

4. When the Answer Does Not Match Expectations

Sometimes users expect a specific type of answer that the system does not provide.

This can happen when:

• The expected answer is not supported by data
• The question was interpreted differently
• The system is designed not to provide that type of output (e.g., recommendations)

What you can do:

• Rephrase the question more clearly
• Adjust expectations to focus on data, not advice
• Ask follow-up questions to clarify

If needed, compare how the question is framed and refine it accordingly.

5. When Responses Are Slow

Response time can vary depending on:

• The complexity of the query
• The amount of data being processed
• System usage at that time

What you can do:

• Wait a few moments and allow the system to complete processing
• Try simplifying the query
• Refresh and retry if necessary

Persistent delays may indicate a temporary system issue.

6. When You Encounter Errors or System Issues

Occasionally, you may experience:

• System errors
• Failed queries
• Unexpected behavior

What you can do immediately:

• Refresh the page
• Re-enter your query
• Check your internet connection

If the issue continues, it should be reported.

7. Reporting Issues

If you encounter a problem that cannot be resolved through basic troubleshooting, you should contact support.

When reporting an issue, include:

• The exact query you entered
• What you expected to see
• What actually happened
• Any relevant screenshots (if available)

Providing clear information helps us identify and resolve issues more effectively.

8. Getting Support

Support is available to assist with:

• Technical issues
• Access problems
• Questions about how to use the system
• Clarifications on outputs

Depending on the platform setup, support may be accessed through:

• A contact form
• Email support
• Partner or institutional channels

9. Continuous Improvement Through Feedback

Ask ADZA is continuously improving.

User feedback plays a key role in:

• Identifying gaps
• Improving usability
• Enhancing data coverage

If you encounter recurring issues or have suggestions, sharing them helps improve the platform for everyone.

10. When to Escalate

If an issue significantly impacts your ability to use the platform, or relates to:

• Data integrity concerns
• Security or privacy concerns
• Access or account issues

It should be escalated through official support channels as soon as possible.