> For the complete documentation index, see [llms.txt](https://www.kauneonga.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.kauneonga.com/docs/portals-and-app/admin-portal/clients-and-accounts.md).

# Clients and accounts

Client setup, account features, phone information, and related configuration.

Clients hold the customer relationship. Accounts hold the operational configuration under each client.

An account usually maps to a phone number, location, brand, or service line.

This structure helps Liberty support multi-account client operations while keeping workflow settings organized at the right level.

### What you manage here

Use this area to manage:

* client records and account structure
* account-level features and phone information
* offices, billing identifiers, and phone number setup

### In this section

* [Account features](/docs/portals-and-app/admin-portal/clients-and-accounts/account-features.md)
* [Account phone information](/docs/portals-and-app/admin-portal/clients-and-accounts/account-phone-information.md)

### Account features

Admins can turn features on or off per account. Common features include:

* **Agent Form Builder**
* **API Access**
* **Audit Logs**
* **Caller Passthrough**
* **Call Recording**
* **Chat**
* **Closing Actions**
* **Data Dip**
* **Escalation Delay**
* **FAQs**
* **Instant Replay**
* **On-call Calendar**
* **Online Payment Access**
* **Scheduled Emails**
* **Scheduled Fax**
* **Secure Messaging**
* **SMS Acknowledgement**
* **To Dos**
* **Use CallerID as DID**

Choose features based on the client workflow, notification method, and compliance needs.

### Accounts

Accounts let you manage multiple phone numbers, service lines, locations, or brands under one client.

#### Add an account to a client

1. Open the client.
2. Go to **Accounts**.
3. Select **Add Account**.
4. Assign the phone number.
5. Complete the form.
6. Save the account.

{% hint style="info" %}
Only the company name and company phone are required to create an account.
{% endhint %}

### Phone information

The **Phone Information** area stores operational details used by scripts, routing, and messaging.

Common fields include:

* company name, number, and address
* skills
* industry and time zone
* holidays
* website
* email subject and SMS template
* company information and office hours
* special instructions
* escalation defaults for non-message, SMS, chat, and voicemail workflows

### Offices

Offices store business locations tied to an account.

#### Add an office

1. Open the account.
2. Go to **Offices**.
3. Select **Add Office**.
4. Enter the location details.
5. Select **Create Office**.

### Billing

Billing stores reference data tied to the client or account. In the front end, this value is labeled **Billing ID**.

It often matches the identifier used in billing systems such as TBS, Tasbiller, or QuickBooks.

{% hint style="info" %}
Exports may still show **Customer Reference #** until backend changes are made.
{% endhint %}

### Phone numbers

The global **Phone Numbers** area manages the number inventory available in Liberty.

#### Add a phone number

1. Go to **Phone Numbers**.
2. Select **Add Phone Number**.
3. Enter the number, account number, location, availability date, and status.
4. Select **Create**.

#### Edit or deactivate a phone number

Open the phone number record, update the fields, then save. To deactivate it, clear **Active**.

{% hint style="warning" %}
Deactivating a phone number can interrupt agent and user access tied to that number.
{% 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 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://www.kauneonga.com/docs/portals-and-app/admin-portal/clients-and-accounts.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.