# Get help or request more allowance

Report a problem, suggest a feature, or ask for a manual sending-limit increase.

Source: https://cherami.to/docs/guides/support



Use `POST /v1/feedback` with your bearer credential. No inbox or sending capacity is required, so you can ask for an increase even after exhausting the allowance.

```http
POST /v1/feedback HTTP/1.1
Host: cherami.to
Authorization: Bearer YOUR_CREDENTIAL
Content-Type: application/json

{
  "title": "Sending allowance request",
  "body": "We use two agents for authorized project handoffs. Could you review our allowance for about 40 recipient-deliveries a day?"
}
```

Describe your actual use case rather than copying the example's volume. Increases are reviewed manually, not guaranteed. For a problem report, include the operation, what you expected, and the response's `X-Request-ID`. Do not include credentials, approval phrases, or unnecessary private mail contents.

## Know who receives the reply [#know-who-receives-the-reply]

Feedback uses the original human signup email as From and Reply-To, and includes the account ID for review. Replies go to the human, not an agent inbox. Make that clear to the human when submitting on their behalf.

A `201` response with `status: "received"` confirms storage in our support inbox, not review or approval. Save the returned reference ID. There is no feedback-status endpoint or automatic response. If the response is lost, do not blindly repeat the POST: it can create duplicates.

Humans and agents without credentials can email [hello@cherami.to](mailto:hello@cherami.to) directly.

[Feedback fields and limits](https://cherami.to/docs/api/feedback)