# PYLO documentation

What PYLO is, how these docs are organised and where to start for your role.

PYLO runs the operation behind a sales team that sells on calls. It sits on top of your CRM, Close or GoHighLevel, rather than replacing it: your CRM keeps the contacts and PYLO runs the operation around them. Every call gets a post-call form, every rep files an end of day report, every instalment is tracked, and commission is worked out from those records. Because every figure comes from rows PYLO holds, you can trace a number back to what produced it.

## Start with your role

What you see in PYLO depends on your role in the workspace. Each getting-started page covers what that role can see and do, what to set up on day one, and the screens you will use most.

| Role | Start here |
| --- | --- |
| Owner | [Getting started as an owner](/docs/getting-started/owner) |
| Admin | [Getting started as an admin](/docs/getting-started/admin) |
| Closer | [Getting started as a closer](/docs/getting-started/closer) |
| Setter | [Getting started as a setter](/docs/getting-started/setter) |
| SDR | [Getting started as an SDR](/docs/getting-started/sdr) |
| Agency operator, running several client workspaces in Agency OS | [Getting started as an agency operator](/docs/getting-started/agency-operator) |

## How the docs are organised

- The workspace sections follow the sidebar's hubs, in the same order: **Home and My Board**, **Dashboard**, **Leads**, **Calls**, **Webinars**, **Team**, **Money**, **Marketing** and **Resources**. Each page is one tab of its hub, such as [Post-call form](/docs/features/post-call) in Calls or [Payouts](/docs/features/payouts) in Team.
- **Settings** follows the settings page's five groups: Workspace, Team and access, Integrations and automations, Billing, and Data. Start at the [Settings overview](/docs/settings/overview).
- **Agency OS** covers running several client workspaces from one place, starting at the [Agency dashboard](/docs/agency/dashboard).
- **Connectors** lists every tool PYLO connects to and how to set each one up.
- **Reference** documents the API and the MCP server for developers and agents.

Inside the app, the help icon in the header opens the page for the screen you are on.

## Connectors

PYLO reads your calls, bookings, forms and payments from the tools you already use. The [connectors page](/docs/connectors) lists them all with their current status. Common starting points are [Close](/docs/connectors/close), [GoHighLevel](/docs/connectors/ghl), [Calendly](/docs/connectors/calendly), [Typeform](/docs/connectors/typeform) and [Slack](/docs/connectors/slack). Owners and admins connect them in [Integrations](/docs/settings/integrations).

## The rep app

Closers, setters and SDRs can file post-call forms, log past calls and DM closes, and send their end of day report from a phone. The rep app installs to the home screen and can send push notifications when a call is booked or a form is due. See [The rep app and push notifications](/docs/rep-app).

## Billing

PYLO has two plans, Basic and Pro, and Pro includes Agency OS. [Billing and plans](/docs/billing-and-plans) explains what each plan unlocks, how seats and extra workspaces are charged, the free trial, how to change plan, and what happens if a payment fails.

## Claude and agents

You can work with PYLO from Claude. [The Claude plugin and its skills](/docs/claude-plugin) covers the plugin and what its skills do, and the [MCP server reference](/docs/mcp) lists every tool the server exposes.

## API reference

[The PYLO API](/docs/api) introduces the API for developers. The [Public API reference](/docs/reference/public-api) and the [Agent API reference](/docs/reference/agent-api) are generated from what PYLO actually serves, so they always match the live API.