> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/general/proposals-and-invoices/initial-settings/proposals-and-invoices-initial-settings-guide/proposals-and-invoices-sales-channel.md).

# Proposals and invoices - Sales channel

<figure><img src="/files/948db74e8a57046a0ea59729682ba91789da65e4" alt=""><figcaption></figcaption></figure>

The **Sales Channels** indicate where each opportunity came from (e.g.: Google, WhatsApp, Website, Referral). Registering these channels helps with reports and organizing proposals and invoices.

***

### Where it is located

**Proposals and Invoices Settings → Sales Channels**

You will see the list with: **First name**, **Alias**, **Creation/Update Date** and the action **Delete**. There is also the search and the button **+ New Sales Channel**.

<figure><img src="/files/e36cd241809b46b8e657fda4a8a094e18f8bd48a" alt=""><figcaption></figcaption></figure>

***

### Create a channel (step by step)

Access **Settings → Sales Channels and c**lick on **+ New Sales Channel**.

1. On the **Edit Sales Channel**, fill in **Sales channel name**
   * Ex.: `Google`, `WhatsApp`, `Website`, `Instagram DM`, `Referral`.
2. Click **Register** to save.

<figure><img src="/files/4d49df613e8c58586fc24c92e674f55a13bab871" alt=""><figcaption></figcaption></figure>

> Tip: the **Alias** is generated automatically from the name (e.g.: `google`, `whatsapp`) and appears in the listing.

***

### Edit or rename

<figure><img src="/files/a6edc3b0c7c36d24afced119c5599995e32fac3f" alt=""><figcaption></figcaption></figure>

In the channel list, click on the desired channel, change the **Sales channel name and c**lick on **Register** to apply.

<figure><img src="/files/7c2313c7909b403fdf9ddadcf971960392ebb6e9" alt=""><figcaption></figcaption></figure>

***

### Delete (careful!)

* Use the button **Delete** (on the channel row or at the top of the edit screen).
* Before removing, check that there are no proposals/tasks using this channel. Prefer **renaming** over deleting, to keep the history.

***

### Change logs

* Click **Change logs** (bottom right corner of the list) to see who created/changed/deleted and when. Useful for auditing.

<figure><img src="/files/955c7bb96d6e35137510e5f329dbf1f5716ed630" alt=""><figcaption></figcaption></figure>

***

### Naming best practices

* **Short and clear:** “Google”, “WhatsApp”, “Website”, “Referral”.
* **No unnecessary variations:** avoid “whats”, “wpp”, “Whats App”.
* **Useful categories:**
  * **Paid:** Google Ads, Meta Ads.
  * **Organic:** Website, SEO, Instagram DM.
  * **Partnerships:** Referral, Reseller, Fair/Event.

***

Done! With the channels created, your reports become more accurate and it becomes easy to understand which sources bring more business.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sprinthub.com/en/topics/general/proposals-and-invoices/initial-settings/proposals-and-invoices-initial-settings-guide/proposals-and-invoices-sales-channel.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
