Brainforge Knowledge

omni-quickstart-guide

4 min read

Omni Quickstart Guide

Source: Omni partner materials
Last synced: 2026-03

Welcome to the Omni Quickstart Materials! We’re so happy to have you as a partner delivering services with Omni.

Before delivering Quickstarts, you will need to be Omni Platform and Quickstart Certified. If you have not done so already, please reach out to Peter Whitehead (peter@omni.co) and Paul Goddard (paul@omni.co) to complete those.

Every customer deserves an expert that can guide them to the best use of the platform for their specific needs. Omni sees the Quickstart as an essential component to creating a healthy account and customer evangelists. We see its key function is to transfer a way of thinking about Omni that will enable the customer to solve their own problems with the power of the platform.

Overview of Quickstart Sessions (~20 Hours Total)

Below is an overview of the Quickstart process for Omni

  • Kickoff with Customer – 30-60m
  • Developer Training – 90m
  • Co-Dev Session (Typically 4) – 60m each
  • User Training – 60m
  • Wrap-Up with Customer – 30-60m
  • Remaining Hours: Support or Preparation

Quickstart Template Materials Included from Omni

Omni provides materials to support Quickstart delivery; partner can utilize as is or customize with partner-specific branding

Overview of Rules of Engagement

  • Omni provides support to customers via Slack, which will include our support team as well as Omnis from across the company. Our Support team offers very fast support and we aim to have our partners be active in channels as well during implementations. This can be treated as billable time during the Quickstart.

  • Recommend having the customer add partners to their Omni instance and, if applicable, previous BI Tool instances to help with training and implementation.

  • If you’re not sure about the answer to a specific question, please tell the customer you’ll take it offline and get back to them. If you’re debugging an issue or error, give an honest effort toward the root cause, but be mindful of how much time is being spent on a single issue and document to then take offline. This creates a much better customer experience than trying to navigate around or experiment live when you’re not totally sure of the answer.

  • While there are no hands-on-keyboard deliverables as part of a Quickstart, on occasion, as part of troubleshooting or co-development, always use a branch or a duplicated version of content. Never make changes directly to their Omni instance or queries without their explicit consent.

  • Treat customers as friends and utilize professional, but casual language.

  • Keep communications professional by avoiding controversial subjects as much as possible (e.g. religion, politics).

  • Things to not do:

    • Anything security related within a customer’s instance – guidance can be given, but the customer should own any changes made.
    • Adding users to a customer’s instance – the customer should own user management given data sensitivity.
    • Make commentary on data – only discuss the data or query in the context of building vs the contents of the data itself.

Activities Owned by Omni

If any of these come up, please message us on Slack and we can help with logging tickets or getting these configured.

  • Log a Bug
  • Log a Feature Request
  • Enabling Feature Flags
  • Setting up an SSH Tunnel
  • Setting up a Vanity URL
  • Requesting Audit Logs
  • Requests for BAA/MNDA
  • Manage Omni Platform Contract and Contractual Terms
  • Auto-Generating Customer-Specific Decks to Shared Slack Channel

If you have any questions, please reach out to us. We’re excited to work with you to make our customers successful!

Graph View

Backlinks