# Boards and Fields

Source: https://docs.qvoice.net/desk-center/boards-and-fields/

A **board** is where one kind of work lives. It has columns, it has fields, and it has people who can see it.

## Columns

**Desk Center → Workflows → (board) → Columns**

A column has a **name** your team chose and a **category** the software reads. The categories are fixed — Open, Active, Review, Done, Cancelled — and every report, the archive and every automation reads the category rather than the name.

| Operation | What happens |
| --- | --- |
| **Rename** | Nothing else changes. Nothing is keyed on the name. |
| **Reorder** | The board's left-to-right order. |
| **Add** | Choose a name and a category. |
| **Change a category** | Applies to every item in that column, including finished work. Changing a column to **Done** starts the archive clock for everything in it. |
| **Remove** | You are asked where its work goes. Nothing is stranded. |

**Review is not a fifth kind of Active:**

**Review** means *waiting on somebody who is not us* — an approval, a customer reply, a part on order. If your team invents a column for that, give it the Review category rather than Active, or it will count as work in progress for as long as the wait lasts.

## Fields

**Desk Center → Fields** defines them; **Workflows → (board) → Fields** attaches them.

A field is a question the work item asks. Defining it in one place and attaching it in another is deliberate: the same *Order number* can be asked on three boards and mean the same thing in all three.

Fields come in the usual shapes — text, number, date, a list to choose from, a yes/no. A field can be **required**, which is a decision of the board rather than of the field: the same field can be required on one board and optional on another.

**Contact fields** are the same idea for the people rather than the work: what you record about a customer, under **Desk Center → Contact Fields**.

**Company fields** are the third, under **Desk Center → Company fields**: what you record about a *company* rather than about a person at it. An account number belongs to the company and is the same for all six people there, so asking it of each of them would be six places for one fact to disagree. Only a company that has been made a **record** can hold them — which is one of the reasons to make one.

Where **contact** fields appear, once defined:

| Where | What you see |
| --- | --- |
| **New contact** | every contact field, empty, ready to fill in |
| The contact's own screen | only the fields that have an **answer**, under the note |
| **Edit** on a contact | every contact field again, so an empty one can be filled in later |

A field with no answer is left off the contact's screen on purpose: an account with ten contact fields would otherwise put nine blanks around the one fact you opened the person to read. **Edit** is where the empty ones are, because that is where you fill them in.

**No and 0 are answers:**

A yes/no field left unticked reads as **No**, and a number field holding zero reads as `0`. Both are things somebody recorded, so both are shown — *Under contract: No* is information, and *Owed: 0* is usually the most reassuring row on the screen.

**Retiring a field does not erase what was recorded:**

If you remove a contact field from the library, the answers already stored on contacts stay stored. They stop being shown, and they are not destroyed by somebody editing that contact afterwards. Define the field again and the answers reappear.

## Types

**Desk Center → Types**

A **type** is a named set of fields — *Complaint*, *Installation*, *Quote*. When one board carries several kinds of work that each need different questions, a type carries its questions onto whichever board the work lands on, on top of whatever that board already asks.

A type never changes behaviour. It does not move work, it does not change columns, it does not decide who sees anything. It only adds questions.

**Fields first, then types:**

A type is a set of fields, so an account with no fields has nothing to build one from. That is also the order the menu is in.

## Tags

**Desk Center → Tags**

A **tag** is a label the account sorts its people by — `vip`, `churn risk`, `renewal q3`. Unlike a field, it asks no question and holds no answer: a contact either wears it or does not.

Tags are an **account-wide catalogue, and this screen is where it is kept**. They are not Desk Center's own: they are the same tags the portal shows under **Configuration → Account → Tags**, on the same account. A tag renamed here is renamed there, and one created there appears here on the next load. Nothing is copied and nothing is synchronised — there is one list, read from two places.

|  |  |
| --- | --- |
| **Name** | what people see on the contact |
| **Colour** | the dot and the border on the label, everywhere it is shown |
| **Description** | a line for whoever maintains the catalogue |
| **Where it can be used** | which parts of the platform may put this tag on something |

### Where it can be used

A tag can be used in more than one place, and the three are independent.

| Scope | What it means |
| --- | --- |
| **Internal users** | the tag may be put on the people who work for you, in the portal |
| **Contacts** | the tag may be put on a customer — **this is the one Desk Center uses** |
| **Queues** | the tag may be put on a call queue, in the portal |

**A tag made in Desk Center is a contact tag.** The box is ticked when the dialog opens, because a tag created on this screen that could not be used on a contact would be invisible to the only place in this product that offers tags. It is a default and not a rule: untick it, tick the others, or tick all three.

**An existing tag is usually scoped to internal users only:**

Accounts that have been using the portal for a while commonly have every tag scoped that way — they were made for staff. Those tags are listed here, wearing an **Internal users** badge, and **they will not be offered on a contact until somebody ticks Contacts**. That is one line of work per tag, done once, and it is the usual first thing to do on this screen.

**Queues are configured in the portal:**

The scope is shown and editable here so the catalogue reads the same in both places, but ticking it changes nothing you will see in Desk Center.

### Changing and removing

**Edit** changes any of the four. **Delete** removes the tag from the catalogue — and what it does to the people already wearing it is the portal's decision, not Desk Center's, so a label may go on being shown on a contact after the catalogue entry is gone.

**A description can be changed but not emptied:**

The endpoint behind this screen treats a blank value as *leave it alone* rather than *clear it*. Desk Center says so under the field instead of appearing to work and changing nothing. To empty a description, edit the tag in the portal.

A name that is already in use is refused, in the portal's own words — *Tag with specified name already exists.*

## Naming a board

Two boards cannot carry the same name, and the comparison ignores capitals and
spaces at the ends — *Support*, *support* and `Support` are one name. Creating
or renaming a board to a name already in use is refused in the moment, with the
reason: *another board is already called that*.

This is why: a board is chosen by name everywhere it matters — the routing
dropdown, a disposition's target, the picker that moves a case — and two boards
with one name are told apart only by an identifier nobody is shown.

**An archived board does not hold its name:**

Archived boards are not offered anywhere a board is chosen, so they do not
stand in the way of a name. The consequence is worth knowing: a board
archived under a name you then reuse will come back sharing it if you
un-archive it. Rename one of the two if that happens.

## Settings that belong to the board

**Desk Center → Workflows → (board) → Settings**

- **Archive window** — how long finished work stays visible. Overrides the account's.
- **Who can see this board** — see [Who Sees What](https://docs.qvoice.net/desk-center/permissions/).
- **Do not allow work to be moved to another board** — off, a case can be [moved to another board](https://docs.qvoice.net/desk-center/for-agents/#moving-a-case-to-another-board) when the work turns out to belong there; on, work leaves this board only by being finished.
- **Define the path work follows** — off, work moves between any two columns; on, each column says where its work may go, and the columns and the diagram of them appear directly below. See [Automation](https://docs.qvoice.net/desk-center/automation/).

  **These two are separate settings:**

  Ordering a board's columns says nothing about whether a mis-filed case may be re-filed elsewhere. A board can restrict where work moves **and** still release it, which is the ordinary case.

  Turn **Do not allow work to be moved** on for a board whose cases carry something another board has no way to finish — a quote out for signature, an order with a supplier. Everywhere else, leaving it off is what lets somebody fix a case opened on the wrong board without closing it and typing the work again.

  Turning either on **moves nothing**. Everything already on the board stays exactly where it is, including cases that arrived from another board. What changes is the next move.

## Settings that belong to the account

**Desk Center → Workflows → Settings**

- **Default board** — where work goes when nothing else decided. Also editable from **Desk Center → Routing**, which is the screen that tells you what it currently is; it is one setting read and written from two places, not two.
- **Key prefix** — the short code in front of every item's number (`SUP-412`). Assigned once, at birth, and never changed, so a link anybody pasted keeps working.

  **The numbers can skip, and nothing is missing when they do:**

  Numbers are handed out in order, but they are reserved in batches — so after a release or a restart the next case may jump, say from `SUP-412` to `SUP-443`. The skipped numbers were never used by anything and no case is hidden behind them.

  This is what lets a whole queue of agents finish their calls at once without any of them waiting for a number. **Do not count cases by their numbers**: the board's own counts and the reports are the figures to use.

  - **Archive window** — the default for boards that do not override it.
  - **Email notifications** — the account's ceiling. See [Notifications](https://docs.qvoice.net/desk-center/notifications/).
  - **Attachment storage** — what the account has used and what it may use. Read only; see [Attachments and Storage](https://docs.qvoice.net/desk-center/attachments/).

## Archiving a board

A board that is no longer used can be **archived**. Its work stays, and stays searchable; no new work can be filed on it. It is the board-level equivalent of cancelling a work item rather than deleting it.

**There is a ceiling, and archiving does not lower it:**

An account is listed up to **200 boards and prospect pipelines, counted together** — and an archived board still counts, because it still exists. No real account approaches two hundred: one that does is usually creating boards where a **type** or a saved **view** was meant. If you need the limit raised, that is a question for whoever provides your service.

## Deleting a board

An archived board that holds **nothing at all** can be deleted, from the board's own settings. The button appears only once the board is archived.

Deleting is permanent and there is no undo, so Desk Center asks for both conditions before it will do it:

| Condition | Why |
| --- | --- |
| The board is **archived** | Archiving is the reversible step. It is what you do to a board you think you are finished with; deleting is what you do once you are sure. |
| The board holds **no work and no contacts** | A board is where work lives. Deleting one that still held cases would destroy them, so Desk Center refuses instead of asking you to confirm something you cannot take back. |

If either is not true the delete is refused and says which one — *the board is not archived*, or *the board still holds work*. To delete a board that has cases on it, move them to another board first, or cancel them and let them archive out.

**This is what archiving is for most of the time:**

**Archiving is the normal answer** to a board nobody uses any more: the work stays, stays searchable, and nothing new can be filed on it. Deleting exists for the boards that were never used — the ones that arrived with the account and did not fit how your business works. Deleting those is how you get a sidebar that lists only your own boards.

It is the only action on these screens that cannot be undone.
