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

# Community & support

Where to ask for help, share patterns, and report issues.

## Support tiers

| Channel                         | Available on               | Response time                 |
| ------------------------------- | -------------------------- | ----------------------------- |
| **Email** `support@ipdunar.com` | All plans, including trial | 1 business day                |
| **In-dashboard chat**           | All plans                  | 24/7, median <30 min          |
| **Priority queue**              | Pro plan and above         | 1 hour during business hours  |
| **Dedicated CSM**               | Enterprise                 | Slack or Teams shared channel |
| **Phone / video call**          | Enterprise on request      | Scheduled                     |

Trial accounts get the same SLA as paid — we don't want you to be confused before becoming a customer.

## What to include in a support ticket

Help us help you faster. Useful info:

* **`X-IPdunar-Request-Id`** from a failing request (the single most useful field)
* The **status code** and **`X-IPdunar-Error-Code`** header
* The **sub-user** name involved
* What you tried, and what you expected vs got
* A **minimal reproduction** if it's a complex issue (curl command, or a small script)

A ticket with just "doesn't work" takes us hours to triage. A ticket with the trio above takes minutes.

## Community

### Discord

The ipdunar Discord is open to all customers and trial users — link in your dashboard under **Resources → Community**, or at [ipdunar.com/discord](https://ipdunar.com/discord).

Channels:

* `#announcements` — official updates from us
* `#general` — chat with other users
* `#showcase` — share what you're building
* `#help` — peer support (faster than email for some questions)
* `#feature-requests` — request features publicly so others can upvote

ipdunar staff hang out daily. Treat it like a colleague office hour, not a 24/7 ticket queue.

### Newsletter

Monthly summary of changes, new integrations, and pattern guides. Opt in at **Settings → Notifications → Product newsletter**.

## Status page

Real-time service health at [status.ipdunar.com](https://status.ipdunar.com). Subscribe via:

* Email
* RSS / Atom
* Webhook (for ops dashboards)
* Slack channel (Enterprise)

We post during incidents (every 15 minutes typically) and after with a postmortem.

## Security disclosure

For security-related reports — not regular bug reports — use **<security@ipdunar.com>**. PGP key on [ipdunar.com/.well-known/security.txt](https://ipdunar.com/.well-known/security.txt).

We follow coordinated disclosure: report → we triage → we fix → public credit when shipped (if you want it). We don't have a formal bug-bounty program yet but pay out at our discretion for impactful finds; email <security@ipdunar.com> to discuss.

## Abuse reports

Receiving abuse from a ipdunar IP? **<abuse@ipdunar.com>** with:

* The IP address
* A timestamp (UTC)
* A copy of the offending request, including full headers

We respond within 1 business day.

## Office hours (Enterprise)

For Enterprise customers, the CSM team runs:

* Weekly office hours
* Architecture reviews on request
* Pattern consultations (e.g. "is this scaling shape right for our service?")

Schedule via your CSM.

## Feedback on the docs

This documentation is in active development. Two ways to give feedback:

* **Per-page** — every page has a "Was this helpful?" widget at the bottom
* **General** — `docs@ipdunar.com`

If you've found something inaccurate, misleading, or missing, tell us at **<docs@ipdunar.com>**.


---

# 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.ipdunar.com/resources/community.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.
