> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/contact-us.md). # Contact us There are two ways to get in touch. Use whichever suits you. *** ### Email Email us at . This is the best option for anything that needs a detailed reply, or when you want to attach screenshots, files, or examples. To help us get you an answer faster, try to include: * A clear description of what you're trying to do * What you expected to happen, and what happened instead * The name of the account, campaign, form, audience, or import you're working with * Any screenshots or error messages *** ### Live Chat If you're logged in to UbiQuity, you can chat with us directly using the live chat button in the bottom corner of the screen. Live chat is good for quick questions and getting pointed in the right direction. If your question turns out to be more involved, we may follow it up by email so we can give it proper attention.
A screenshot of the purple live chat icon shown when logged in to UbiQuity.

When logged in, click the purple chat icon to use live chat.

--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ubiquity.co.nz/contact-us.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.