> 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/documentation/keep-learning/training.md).

# Training

Learn how to get more out of UbiQuity with guided training delivered by our team.

### Training Overview <a href="#training-overview" id="training-overview"></a>

UbiQuity training is designed to help your team build confidence using the platform and get value faster. Training is delivered by our Marketing Automation Consultants and can be tailored to your setup, use cases, and level of experience. Whether you're just getting started or looking to go deeper, training helps ensure you're using the platform effectively.

***

### What training covers <a href="#what-training-covers" id="what-training-covers"></a>

Training sessions are typically tailored, but may include:

* Platform fundamentals and navigation
* Managing your database and imports
* Creating and sending mailouts
* Building journeys and automations
* Using forms and data capture
* Reporting and optimisation best practices

***

### How training works <a href="#how-training-works" id="how-training-works"></a>

Training is delivered remotely and scheduled directly with your UbiQuity consultant. Sessions can be structured as:

* Initial onboarding training
* Role-based training for different team members
* Follow-up or advanced sessions as your usage evolves


---

# 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.ubiquity.co.nz/documentation/keep-learning/training.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.
