> For the complete documentation index, see [llms.txt](https://docs.ochats.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ochats.io/use-cases/for-procurement-team.md).

# For Procurement Team

Procurement team can use these functions to help their daily tasks.

<details>

<summary>Chat Management System</summary>

They can communicate with all their existing vendors and potential vendors in 1 platform. Most importantly, they can reply to their customer whichever channels their customer contacts them.&#x20;

</details>

<details>

<summary>CRM System</summary>

Procurement team can manage every proposal & contacts sent by their vendors using tag management system. They will be able to filter out the contact based on the tag they have inserted in every contact.&#x20;

</details>

<details>

<summary>Multiple Team Member Access</summary>

oChats.io allows businesses to invite more users to use this software. Users can transfer the conversation from 1 person to another easily.&#x20;

</details>

<details>

<summary>Brand Management System</summary>

Procurement team can juggle from 1 brand/business to another easily and manage all the proposal for different brands/businesses in 1 platform.

</details>

View more features at here

{% content-ref url="/pages/fOsBj14IhmiNDUtsfJck" %}
[Our Features](/overview/our-features.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ochats.io/use-cases/for-procurement-team.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.