> For the complete documentation index, see [llms.txt](https://docs.creativeconners.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creativeconners.com/docs/machinery/pushstick-mini/technical-support.md).

# Technical Support

If you get stuck, we’re here to help. The best way to get in touch with a tech expert is via email - even during normal business hours - because most days we are spread around the shop and may not be near the phone. There’s someone in the office from 8:30a-5pm EST Monday - Friday and will return an email or phone call quickly. After hours (honestly when most tech support issues arise) we have a crack team monitoring email and voicemail who will respond quickly to help get you moving.

* Online: [www.creativeconners.com](https://www.google.com/url?q=http://www.creativeconners.com\&sa=D\&source=editors\&ust=1660754042711689\&usg=AOvVaw1v1LFrFesgxn1twZ0_jG9Q)
* Email: <support@creativeconners.com>
* Phone: 401-289-2942


---

# 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.creativeconners.com/docs/machinery/pushstick-mini/technical-support.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.
