> For the complete documentation index, see [llms.txt](https://learning.contextqa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learning.contextqa.com/business-use-cases.md).

# Business Use Cases

- [Business Use Cases Overview](https://learning.contextqa.com/business-use-cases/business-use-cases.md): Map ContextQA capabilities to business outcomes, implementation patterns, evidence, and measurable QA success criteria.
- [Requirements to Release](https://learning.contextqa.com/business-use-cases/requirements-to-release.md): Turn requirements, tickets, spreadsheets, designs, videos, and natural-language workflows into reviewed, traceable ContextQA tests.
- [Complex Web and Authentication](https://learning.contextqa.com/business-use-cases/complex-web-and-authentication.md): Automate multi-system web journeys involving MFA, email, browser extensions, file handling, APIs, and databases.
- [Regression Risk and Evidence](https://learning.contextqa.com/business-use-cases/regression-risk-and-evidence.md): Build a risk-based regression program with targeted execution, self-healing, root cause analysis, and auditable run evidence.
- [Specialized Quality Gates](https://learning.contextqa.com/business-use-cases/specialized-quality-gates.md): Add performance, accessibility, visual, security, compatibility, and export checks to a functional ContextQA release workflow.
- [Document, OCR, and KYC Validation](https://learning.contextqa.com/business-use-cases/document-mobile-and-ocr.md): Validate document extraction and identity-verification applications with web, mobile, API, and data-driven ContextQA tests.
- [Salesforce and Enterprise Workflows](https://learning.contextqa.com/business-use-cases/salesforce-and-enterprise-workflows.md): Protect Salesforce lead, opportunity, CPQ, revenue, and service workflows with reusable sessions, UI/API validation, and evidence.
- [Connected Delivery Workflows](https://learning.contextqa.com/business-use-cases/connected-delivery-workflows.md): Connect ContextQA requirements, tests, CI/CD execution, notifications, defects, reports, and AI agents across the delivery lifecycle.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learning.contextqa.com/business-use-cases.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.