> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/support/how-to-reach-us/questions.md). # Questions You can use any of these methods if you have follow-up questions about alerts, investigations, incidents, or detections. If you need more help with any of these methods, see [Technical Support](/support/how-to-reach-us/technical-support.md).


Email	To reach us through email, send your message to support@expel.com.
Workbench	To reach us through Workbench, go to your profile in the upper right corner and select Submit a ticket in Zendesk.
Slack or Teams	Use `@Ruxie` and choose the Open a support ticket option to access the support ticket form, where you can ask your question. This will create a Zendesk ticket and also provide a link to it. You can add additional information or ask for updates by threading a response to the Ruxie message. Your threaded responses will be added as comments to the Zendesk ticket. The responses that Expel adds in Zendesk will also be threaded within Slack/Teams.
Phone	Please use this method only when you require immediate confirmation that a SOC analyst is reviewing activity in Workbench or a request that you have submitted through the other methods shown here. The SOC will be unable to share sensitive data over the phone. To reach our SOC by phone, refer to the SOC floor number provided in Workbench by navigating to Dashboards > Welcome.

--- # 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.expel.io/support/how-to-reach-us/questions.md?ask=&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.