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

# Contacts

For enquiries and support, you can reach the relevant team at the following:

## **24/7 Support**

[Open a ticket](https://clients.terabix.net/submitticket.php) OR email `support@terabix.net`

For customer support, please [open a support ticket](https://clients.terabix.net/submitticket.php). Alternatively, you can send an email to the above address. Emails sent there will automatically open a support ticket and subsequent replies via email will be synchronized to the ticket. The ticket will be visible in your account if your email is registered with us.

## **24/7 NOC**

`noc@terabix.net`

For issues and communication pertaining to our network such as IP, routing, and peering. This is the suggested contact for NOC-to-NOC communication. Customers should open a support ticket instead. 

## **Abuse Department**

`abuse@terabix.net`

For abuse reports pertaining to our network.

## **General Enquiries**

`office@terabix.net`

For all other general enquiries.


---

# 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.terabix.net/general/contacts.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.