> For the complete documentation index, see [llms.txt](https://trywink.gitbook.io/wink/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://trywink.gitbook.io/wink/product/crm-tools.md).

# CRM Tools

Wink provides creators with various CRM tools such as account permissions for multiple account management and earnings split to enhance workflow. Wink also offers earnings and fan analytics to provide insight into identifying and engaging with loyal, paying fans.

### Features

* **Account Permissions:** Allows creators to bring in multiple staff members to help with their workflow
* **Earn split:** Allows real-time revenue payouts to staff or agencies to ensure maximum trustlessness
* **Chatnotes:** Creators can add personal notes about fans within the messenger, allowing them to keep track of important details about the fan's preferences, past interactions or any special requests 
* **User analytics:** Provides in-depth information about paying and loyal users

<div align="left"><figure><img src="/files/eXm877btWxi47WWebyL2" alt="" width="563"><figcaption></figcaption></figure></div>


---

# 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://trywink.gitbook.io/wink/product/crm-tools.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.