> ## Documentation Index
> Fetch the complete documentation index at: https://omni.fireflo.au/llms.txt
> Use this file to discover all available pages before exploring further.

# Resellers

> How a reseller sets up customers, puts them on a plan, funds them, sets its markup and suspends them.

Resellers answers **"who are my customers, and how are they set up?"** A reseller runs
OMNI for businesses of its own. Each customer is a full OMNI account, under the
reseller's [brand](/using/branding), funded from the reseller's balance.

**Who can use it:** the **Owner** or **Reseller** role.

**Plan:** the account must be a reseller. FireFlo turns this on; until it does, the
screen explains that the account isn't set up as a reseller.

## Your customers

The screen opens with three figures:

* **Your balance**, to fund customers with;
* **Held by this page's customers**, the credit already allocated;
* **Customers**, and how many are suspended.

The table lists each customer with its product (plan), status, balance, your markup and
when it joined. Filter by status (*Trial*, *Active*, *Payment due*, *Suspended*) or
search by name.

## Set up a customer

<Steps>
  <Step title="Start">
    Choose **New customer**.
  </Step>

  <Step title="Who they are">
    Enter the **company**, and the **owner's email** and **name**. The owner is the first
    person who can sign in.
  </Step>

  <Step title="What they are on">
    Pick the **product** (plan), the **trial** in days before they owe anything (0 for
    none), and an optional **opening credit** from your balance.
  </Step>

  <Step title="How they send SMS">
    Decide whether they **may connect their own SMS gateway**. If not, SMS goes through
    the gateway you sell them, and the choice is hidden from them.
  </Step>

  <Step title="Create">
    Choose **Create customer**.
  </Step>
</Steps>

Anyone who signs up at your own web address also becomes your customer. See
[Branding](/using/branding).

## One customer

Open a customer to manage them.

<Tabs>
  <Tab title="Overview">
    * **What they're on**: change their product, and see their balance, when their
      trial ends and how many people they have.
    * **How they send**: allow or stop their own SMS gateway.
    * **Suspend**: nobody at the customer can sign in until you **let them back in**.
  </Tab>

  <Tab title="Credit">
    * **Add credit** moves credit from your balance to theirs. Give an amount and a
      reference; the reference shows on both ledgers.
    * **Your terms**: the **markup** you add on top of your prices (0 to 1000 percent),
      and notes for yourself.
  </Tab>

  <Tab title="Team">
    **Their people**: who can sign in, their roles, when they last signed in, and
    invitations still pending. They run their own team.
  </Tab>
</Tabs>

Credit you move shows on your [Transactions](/using/billing#transactions) as *Credit
allocated*, and on theirs as *Credit received*.

## What a customer can and can't do

* A customer runs its own account: its team, contacts, channels and messages.
* A customer can never do more than you can. Its roles are limited to what your account
  may do.
* A customer can't have customers of its own.

FireFlo's side of running resellers is described in
[For operators: Resellers](/operators/resellers).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.