> For the complete documentation index, see [llms.txt](https://callgraph.gitbook.io/callgraph-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://callgraph.gitbook.io/callgraph-docs/copy-trading/quick-start.md).

# Quick start

Set up your first PumpFun Callouts copy in Telegram.

Start from a caller you want to follow, then choose how the bot should act when that caller trades.

{% stepper %}
{% step %}

### Open New copy

In Telegram, tap **Copytrade → New copy**. You can also use **Copy Trade** on a supported caller alert. Read and acknowledge the risk information shown before continuing.
{% endstep %}

{% step %}

### Select a caller

Send the tracked Pump.fun profile link or supported Solana wallet when prompted. Check the matched caller before continuing.
{% endstep %}

{% step %}

### Choose your trade rules

Pick **Buy only**, **Auto sell** or **Copy sells**. Set **All trades** or **Callouts only**, buy sizing, exposure limits and the relevant guards.

[Compare copy modes](/callgraph-docs/copy-trading/modes-and-sizing.md) · [Review trading safeguards](/callgraph-docs/copy-trading/guards-and-exits.md)
{% endstep %}

{% step %}

### Review and start

Check the caller, amount, maximum exposure, exit rules and available SOL. Confirm the final **Start copying** action shown by the bot.
{% endstep %}

{% step %}

### Manage the copy

Return to **Copies** to check the status and recent activity. Use **Pause**, **Resume**, **Edit** or **Stop** as available.
{% endstep %}
{% endstepper %}

{% columns %}
{% column %}
![Copies list in the Telegram bot showing active relationships and New copy](https://1024313129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F19fy6z4ax7jX5gvABuYZ%2Fuploads%2Fgit-blob-f5efaf60b5159076dce1b1b8259795a42adaa4cd%2Fshot-05.png?alt=media)

**Copies** shows your existing caller relationships.
{% endcolumn %}

{% column %}
![Active copy detail showing activity, status and management actions](https://1024313129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F19fy6z4ax7jX5gvABuYZ%2Fuploads%2Fgit-blob-60b9ee1ac05b9847506122e13fd275ab44c0a039%2Fshot-06.png?alt=media)

Open a copy to inspect activity and change its settings.
{% endcolumn %}
{% endcolumns %}

{% hint style="warning" %}
**Stop copying is not Sell.** Open positions remain yours to manage. Review your exits under [Positions](/callgraph-docs/trading/positions-and-sells.md).
{% endhint %}


---

# 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://callgraph.gitbook.io/callgraph-docs/copy-trading/quick-start.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.