# Open a support ticket, xSpeed Cache

> Tell us what is going on. A question, a bug, a licence problem or an idea. It all lands in the same place, and the reply comes to your email.

Page: https://xspeedcache.com/support/new-ticket

## The form

| Field | Required | Notes |
|---|---|---|
| Your name | yes | |
| Email address | yes | where the reply goes |
| Website | no | `example.com` is fine, scheme optional |
| Topic | yes | one of the four below; no default, a choice is required |
| Subject | yes | one line |
| How can we help? | yes | up to 8000 characters |

Topics: `general` General Help · `bug` Bug Report · `suggestion` Suggestions ·
`other` Others.

## Worth including

- Your site URL, and one page where you can see the problem.
- What you expected, what happened instead, and when it started.
- Anything you already tried: purging the cache, disabling a module.

None of it is required. It is the difference between one reply and three.

## Who answers

The xSpeed team at WPDeveloper, the people who build the plugin. Free and paid
tickets go to the same place; paid plans are prioritised in the queue, and
Enterprise adds onboarding and an SLA. See https://xspeedcache.com/pricing

In a hurry? The chat bubble in the corner of any page is the fastest route for a
short question.

## Programmatic

`POST https://xspeedcache.com/api/support`

```json
{ "name": "Jane Doe", "email": "jane@example.com", "website": "example.com",
  "topic": "bug", "subject": "Cache not holding", "message": "..." }
```

Answers `{"status":"ok","ref":"XS-A1B2C3"}` on success; `400` with a
human-readable `message` for a bad field; `429` when rate-limited.

Prefer to talk? Book a free call instead: https://xspeedcache.com/support