> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/contact-us.md).

# Contact Us

Here is the list of each inquiry that partners can contact the relevant department.

<table><thead><tr><th width="178.33333333333331">Team</th><th width="333">Email</th><th>Responsibilities</th></tr></thead><tbody><tr><td>Technical Support Team (24/7)</td><td><a href="mailto:partnersupport@coda.co">partnersupport@coda.co</a></td><td><ol><li>Transaction check</li><li>Refund request</li><li>Payment channel outage</li><li>Failed to login Publisher Portal</li></ol></td></tr><tr><td>Partner Business Team</td><td><a href="mailto:commercial.ops@coda.co">commercial.ops@coda.co</a></td><td><ol><li>Transaction conversation rate</li><li>New channel available</li><li>Financial inquiries</li><li>Create new Publisher Portal account</li><li>Issues related with VAT</li></ol></td></tr><tr><td>Codapay Support Team</td><td><a href="mailto:codapay_integration@coda.co">codapay_integration@coda.co</a></td><td><ol><li>Codapay integration</li><li>Production Testing request</li><li>Resetting Publisher Portal account</li><li>FTP/S or SFTP report</li><li>Renotify Codapay transaction</li><li>Error codes not listed in this document</li></ol></td></tr><tr><td>Codashop Support Team</td><td><a href="mailto:codashop_integration@coda.co">codashop_integration@coda.co</a></td><td><ol><li>Codashop integration</li><li>Production testing request</li><li>Content and price update</li><li>Product page maintenance</li></ol></td></tr></tbody></table>


---

# 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://docs.coda.co/contact-us.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.