# For Agents

Source: https://docs.qvoice.net/desk-center/for-agents/

If you take calls and work cases rather than configuring them, this is the page for you.

## Opening Desk Center

In **UCP**, click **Desk Center** in the sidebar.

It opens in a **new tab** and signs you in as yourself — nothing extra to type. Your phone stays registered in the UCP tab, so you can keep taking calls while you work a case in the other one.

If your account has **Embedded Softphone** switched on, that changes: Desk Center carries the phone itself and your UCP session ends when it opens. See [The phone beside the case](https://docs.qvoice.net/desk-center/for-agents/#the-phone-beside-the-case).

**Not in your sidebar?:**

Either the account does not have Desk Center, or you have not been given access to any board. Ask an administrator of your account.

## Signing in and out of Desk Center on its own

Desk Center can also be opened directly, without UCP. It then asks for the **account**, your **username** and your **password** — the same details you use for UCP. If they are not accepted, the message deliberately does not say which of the three was wrong; check all of them. Where your deployment has it set up, **Continue with Google** does the same with your Google address and no password.

By default a session lasts for that tab: a reload keeps you signed in, a new tab asks again. Tick **Remember me** and it outlives the tab — which is what you want on your own machine and not on a shared one.

To end it, use the **sign-out** control at the right-hand end of the header. It is not there when Desk Center is embedded in UCP — that session belongs to UCP, so you sign out of UCP.

## What you see

| Section | What it is |
| --- | --- |
| **Boards** | the work: columns to move items across |
| **Contacts** | the people and companies the work is about |
| **Prospects** | whoever you are trying to win, worked through the person you talk to |

**A prospect is whoever you are pursuing:**

Some businesses sell to people and some sell to companies, and the word means a different thing in each. Desk Center works it **through the person you are talking to**: the card in the pipeline is a contact, and the company is written on it.

If you are pursuing the **company**, that still works — the person you deal with is what moves along the pipeline. What to expect:

- **Several people at one company are several cards.** Use the company filter above the board to read them together.
- **A company cannot itself sit in a pipeline.** There is no card for Acme, only for the people there.

What is won *from* a company — a quote, a deal — is a different thing from a prospect, and it is not part of Desk Center yet.

**The Portal calls its own version a lead , and they are not the same thing:**

A prospect in Desk Center **is a contact** — the same person, the same record, carrying a stage. Nothing is copied, so every call, case and note taken while they were a prospect stays attached to them when they buy.

The Portal's CRM, campaigns and the API have a separate **lead** record, which is its own thing with its own numbers. If you use both, expect the two words and do not expect the two lists to match.

### Writing down a prospect

**New prospect** on the Prospects board asks for a name or a number — either on its own is enough — and the person appears in the pipeline's first column. The same button is there when the account has no pipeline yet: the first prospect creates it.

You can also mark somebody a prospect from **Contacts**, which does the same thing. Moving them along the pipeline is dragging their card from one column to the next.

**The Prospects board updates itself too:**

Somebody moving a prospect to another column, a prospect arriving from an
import, and a call wrapped up against one all reach your screen without a
reload — the same way the case boards do. **Last updated** above the board
says how current it is.

### What the Prospects board shows

**Everybody in the pipeline**, however long ago they were last touched. A prospect that has sat in *Qualified* since March is on the board beside one added this morning — which is the point of a pipeline: the ones nobody has moved are exactly the ones worth looking at.

Somebody who is a contact but is in no pipeline is not here. They have no column to be in, and putting them in one would mean choosing a place nobody chose for them. They are in **Contacts**, where everyone is.

**Up to 500 prospects:**

More than that and the board says so under the header. It is a board, not an export: a pipeline past five hundred open prospects is telling you something about the pipeline.

The **search box on this screen narrows what is already on the board** — it does not go and fetch the rest. To reach somebody who is past the five hundred, look them up in **Contacts**, whose search asks the server.

**Before this, old prospects went missing:**

The board used to show only the people the account had touched most recently — of **any** kind, not only prospects. Since contacts arrive on their own from calls, a busy morning of unknown callers was enough to push a real prospect off its own board.

If your pipeline looks fuller than you remember, nothing was created: those prospects were always there and the board was not showing them.

### Labelling people with tags

**Tags** are the words your account sorts its people by — `vip`, `churn risk`, `portugal`, `renewal q3`. They come from a **catalogue your administrator keeps**, under **Desk Center → Tags**: you pick from **Add tag**, and there is nothing to type.

They are set when you write a contact down, and changed later from **Edit** on the contact. The same menu is on a prospect's card.

**The menu offers the tags set up for contacts, and only those:**

A tag your account uses on its own staff or on its call queues is not a contact tag and is not on this menu. If what you are looking for is missing, it either does not exist yet or is scoped elsewhere — both are one change on **Desk Center → Tags**, which only an administrator can make.

An account that has never set a tag up for contacts gets an empty menu saying so. That is the ordinary first state, not a fault.

**A tag somebody typed before the catalogue stays on the person:**

Tags used to be free text, so contacts may be wearing words that are in no catalogue. Those are **kept, shown and removable** — a change to what the product offers never takes back what was recorded. They are simply not on the menu, and the contact says so in a line under the tags. To start offering one again, add it to the catalogue under the same name.

| Where | What you see |
| --- | --- |
| A row in the list | the first two, then a count: `vip` `portugal` `+3` |
| The contact itself | all of them |

**Filtering by them is the point.** The **All tags** menu above the list offers **every tag your account has set up for contacts**, whether or not anybody in front of you is wearing one — and picking one asks the server for **everybody** who carries it, not only those you can already see. A `vip` nobody has touched in months is in that answer.

**Words typed before the catalogue are in the menu too:**

A tag that is on somebody on screen but in no catalogue is still offered, so people labelled by hand before the catalogue existed stay findable.

This is also why one word can appear twice: `VIP` and `vip` are two different labels on two different people, and the filter matches the one that was typed. Both are listed, because each finds somebody the other does not.

Past 200 matches the list says so. Pick fewer labels, or use the search.

**VIP and vip can still be two different tags:**

This is what the catalogue exists to stop, and it does not reach backwards. A tag is stored exactly as it was written, so two spellings typed before the catalogue stay two labels, and the filter matches the one that was typed — anything else would disagree with the record.

The picker will not add a second spelling of a catalogue tag: a contact already wearing `VIP` is shown as carrying the catalogue's `vip`, and the menu does not offer it again.

### Correcting a contact

On a case, use **Edit contact** on its **Contact** panel. On the contact's own screen (from a case, **Open contact** takes you there), use **Edit**. Both open the same editor. It changes the **First name**, **Last name** and **Company**, the phone numbers and emails (the first of each is the primary, the one other screens show), the note, the tags and your account's own fields.

Only what you change is saved: opening **Edit** to fix a number leaves the name exactly as it was.

**Cases keep the name they were filed with:**

A case copies its contact's name when the two are linked, so a board can show it without looking the person up. After you correct a name, the contact's own screen shows the new one at once, and so does the case you corrected it from; other cases filed before the correction keep the name they were filed with.

### The rest of the company

When a contact has a **company** written on them, their screen carries an **Also at *company*** section, between their own open work and their history. It lists the other people in your account at that company, and what is open on each of them — so opening one person tells you that a colleague's renewal is mid-flight, or that somebody else already has a support case running.

| What it says | What that means |
| --- | --- |
| A name with cases under it | that colleague has open work; up to **five** of their cases are shown, most recently changed first |
| A name with **Nothing open** | nothing of theirs is open — *or* their work is on a board you have not been given |
| **Nobody else is recorded at *company*** | this is the only contact in your account carrying that company |
| **More people at *company* are not shown** | the company has more than **20** contacts, and the section stops there |

Anyone with open work is listed first, so what is in motion is at the top. Clicking a name opens that colleague; clicking one of their cases opens it.

A contact with no company has no such section at all.

**A company is the word that was typed, not a record:**

People are grouped by their company **spelled exactly the same way**. `Acme` and `Acme Ltd` are two companies here, and somebody filed under the second will not appear under the first. There is no company list to pick from and nothing to merge — correct the spelling on the contact and they join the rest.

**You only ever see work you are allowed to see:**

A colleague's case on a board you have not been given is simply absent, and reads exactly like them having nothing open. The section never tells you that something exists but is out of reach.

You will not see the setup screens — workflows, fields, routing. Those belong to the account's administrators.

If several boards exist and you only see some, that is deliberate: a board you have not been given is not listed.

## The board updates itself

A board shows what is true **now**. When somebody else moves a card, writes a
comment, blocks an item or re-files it on another board, your screen follows
within a second or so — nothing to press and nothing announced.

Above the board, **Last updated** says when what you are looking at was loaded,
with a refresh control beside it. You should rarely need the control; it is
there for the one case where you want to be certain, and for when the
connection is interrupted.

**If the connection drops, the board says so by getting old:**

The clock beside **Last updated** keeps counting, so a board that has
stopped hearing about changes shows its age rather than looking current. It
reconnects by itself and catches up in one step — you do not have to reload
the page.

**A column that was removed goes too:**

When an administrator renames, reorders or removes a column, the boards on
screen follow — the column list is part of what updates itself, not just
the cards on it. Before this, a column somebody had deleted stayed on your
screen until you reloaded the page, and work moved into it went somewhere
that no longer existed.

**A case open on your screen follows too:**

Open a case and it stays current the same way the board does: a **comment**
somebody else writes, a **status** they move it to, who it is **assigned**
to, whether it is **blocked**, a **file** they attach and the **fields**
they fill in all appear without reloading. **What you are typing is never
touched** — an unsent comment stays exactly as you left it.

An edited title, a priority, a custom field and an attachment arrive the
same way. The one thing that still waits for a refresh is a **link** to
another case.

**Only the board you are looking at:**

Desk Center listens for changes on the board on screen, not on every board
in the account. Opening the **Archived** section stops the listening
altogether: that list is a search through finished work, and it does not
change under you.

## A column shows a page at a time

A column shows at most **50 cards**. When it holds more, the header says so — `50+` rather than a flat count — and **the rest are not on screen**. There is no scrolling further: filtering is how you reach them.

So a column reading `50+` is an instruction, not a decoration. **Narrow it** by assignee, priority, type or text until the column is the question you actually have, and save that as a [view](https://docs.qvoice.net/desk-center/for-agents/#saving-the-way-you-filter) if you ask it every morning.

**Before this, the header lied by omission:**

A column of three hundred items used to read `50`, with nothing to say the other two hundred and fifty existed. If you have been working from a column's count, that is why it never seemed to go down.

**The number is what is loaded, not an audit:**

`50+` means "more than this page", not "exactly fifty". Desk Center deliberately does not count a whole column on every render — on a column of thousands that costs far more than the number is worth.

## Saving the way you filter

A board filters by status, priority, type, customer, assignee, text, attention and the fields your account added — and it remembers each one between visits. What **Views** adds is keeping *several* named sets and moving between them in one click.

**Views**, in the row of filters above the board.

- Filter the board the way you want it, then **Save this view…** and give it a name. *Mine, open* and *Waiting on customer* are the kind of name that earns its place.
- Pick a saved view from the same menu to apply it. The filters below change to match, so you can always see what a view is doing and adjust it by hand.
- The trigger says the view you are in — **View: Mine, open** — and goes back to plain **Views** the moment the filters stop matching it, including when you clear them.

Two things worth knowing:

- **They are yours.** Nobody else sees your views and you do not see theirs. They follow you to another machine and another browser.
- **They belong to one board.** *Mine, open* means different columns on different boards, so each board has its own list.

**A view filtered to you stays filtered to you:**

A view saved with **Assignee: me** is stored as *you*, not as your address — so it keeps meaning "mine" rather than naming a person.

## The clock on a card

If your account has agreed response times with its customers, a card carries the time left instead of the usual "days in this column" badge:

| Badge | Means |
| --- | --- |
| `2h 14m left` | there is room |
| `18m left`, amber | you are inside the last quarter of what was promised |
| `overdue 3h`, red | the time has passed |
| `on hold`, grey | the clock is stopped — the item is waiting in a column, or on the customer |
| `met` | finished, and the promise was kept |

Hover it for which clock it is: the **first answer**, until the customer has been written to, and then the **resolution**.

**A note only counts as an answer if the customer can read it.** An internal note between agents does not stop that clock — which is the point of the two visibilities.

The **Attention** filter gains **Breaching soon** and **Overdue** where promises exist, so you can work the list that is actually at risk.

**Nothing appears if your account has not set any:**

Most do not. A board with no promises looks exactly as it always did — see [Promises About Time](https://docs.qvoice.net/desk-center/promises/) if you are an administrator and want some.

## Working an item

- **Move it** by dragging between columns, or from the item itself.
- **Assign it** to yourself or somebody else. Unassigned is a real state, not missing information.
- **Comment.** Notes are append-only: they are the record of what was said, so they are not rewritten afterwards.
- **Mention somebody** by name in a note and they are emailed, whatever else they have switched off.
- **Attach a file** — up to 20 MB each. Attaching one leaves a note saying so, so the history says when the evidence arrived.
- **Block it** when you are waiting on somebody, and say which: another user, or the customer. Blocked work waiting on the customer clears itself when they reply.

**Finishing is not deleting:**

Work is **closed** or **cancelled**, never deleted. It leaves the board after the account's archive window and stays in the board's Archive, searchable.

## Finding finished work

**Open | Archived**, above the board. The two are the same board asked a different question: *Open* is live work, *Archived* is what has already left it.

Archived work is read through a period — **Last week**, **Last 4 weeks**, **Last 12 weeks**, **Last year** — and each one includes the ones before it, so "Last 4 weeks" contains last week.

The period and the page work against each other, and the screen says so when they do:

> Showing the most recently closed. There is more in this period than fits one page — choose a shorter one to see further back.

Read newest-first, a page at a time. Asking for a **longer** period does not show you more work, it shows you the same recent page out of a bigger pile — so when you are looking for something specific, **shorten the period** until the page reaches it, or search for the customer or the text.

**A board that archives nothing has an empty Archive:**

The archive is simply finished work older than the **archive window** — three days by default. It is a view, not a place work is moved to: nothing has to run for an item to appear here, and changing the window changes what the Archive holds the next time it is opened.

## Calling a customer

Where Desk Center shows a phone number — on a contact, in the contacts list, or on the case's contact card — the number is a button. Click it and **your own phone rings first**; answer it, and QVOICE Platform then rings the customer.

That is why it is your phone that rings and not the number straight away: the call is placed on the device you are already signed in on, so it is recorded, billed and reported like any other call you make.

**Nothing happens when the number is plain text:**

If the numbers are not clickable, click to call is not switched on for your account. It is the same setting that controls click to call in QVOICE Platform's softphone, and only an administrator can turn it on.

After you click, the number tells you where the call got to:

|  |  |
| --- | --- |
| **Calling…** | the request is on its way |
| **Your phone should ring now** | QVOICE Platform accepted the call and is ringing your device |
| **Could not place the call** | it was refused — nothing was dialled |

**“Your phone should ring now” and nothing rings:**

That message means the platform **accepted** the call, not that your phone received it — it is sent the moment the request is accepted, before anything rings. So if you see it and nothing happens, the call was placed and your device did not take it. The usual reason is that no device is registered: your softphone is closed, or your desk phone is offline. Open QVOICE Platform or check your handset and try again.

The message stays for a few seconds, because you are probably looking at your phone rather than the screen when it appears.

## The phone beside the case

If your account has **Embedded Softphone** switched on, Desk Center carries the softphone itself, in a **Phone** panel down the right-hand side. You take and place calls there, next to the case you are working on, instead of moving between two tabs.

You are signed in to it automatically when Desk Center opens — there is no second password to type. It opens on **Activity**, the list of your recent calls, rather than on the keypad: in Desk Center you place calls by clicking a number on the case itself, so the keypad is the screen you need least.

If the automatic sign-in fails, the panel says so and shows the phone's own sign-in form. Enter the same username, password and account you use for the softphone elsewhere, and carry on — you have not been signed out of anything, and the failure is for your provider to look at rather than something you did.

**Opening Desk Center signs you out of UCP:**

QVOICE Platform allows **one softphone session per person**, and the newest one wins. When the phone in Desk Center registers, your UCP session ends and UCP tells you *"New session detected"*.

This is not a fault, and it is not something to work around: it is what stops the same call ringing in two places. On an account with this switched on, **Desk Center is where you take calls**.

### Hiding it

The **⊟** button at the top of the panel hides it and gives the width back to the case. The **⊞** button in the header brings it back.

Hiding the phone does **not** hang up, does **not** sign you out and does **not** stop it ringing. The phone keeps running while hidden — a call in progress carries on, and a wrap-up you had half filled in is still there when you bring the panel back. Desk Center also remembers whether you left it open or shut.

**While it is hidden, nothing on screen tells you a call is ringing:**

The phone rings and the audio plays, but the header shows no badge. If you work with the panel shut, keep your sound on.

### If you do not see it

- **No Phone panel at all** — the account does not have **Embedded Softphone**. An administrator of your account asks their provider for it.
- **No Phone panel, although Embedded Softphone is switched on** — Desk Center on your cluster is a version from before the phone was added (the phone needs Desk Center **0.23.0** or later; the version is in the footer). Saving the switch again does not help; your provider upgrades Desk Center on the cluster.
- **"The phone is not installed here"** — the account has the switch on, but the softphone itself has not been deployed on your cluster. Nothing you can do from Desk Center fixes it; your provider installs it.
- **A panel that asks you to sign in**, under *"Could not sign the phone in automatically"* — your Desk Center session is fine and the phone is there; only the hand-off between them failed. Sign in with the same details and keep working.
- **"Enlarge the window to continue"** — the phone needs a window of at least 350 × 550 pixels to draw itself. Make the browser window taller.
- **You are being acted as by an administrator.** The phone is deliberately not shown then, so that nobody can register it as you and take your calls off you.

Signing out of Desk Center signs the phone out too.

## When a call arrives

If your account has it configured, the caller's details and their open work appear before you answer, and the disposition you choose at the end of the call can file the work for you — one wrap-up, not two.

### The caller's open cases, on the call card

While you are on a call, the card shows what that person already has open in Desk Center, with the number of calls each case has collected:

> **Desk Center · 2 open**
> Billing mismatch `3 calls`
> Porting delay `1 call`

That count is the useful part. *Billing mismatch, 3 calls* says this is the fourth time somebody has phoned about the same thing — before you have had to ask.

It appears on its own once the call connects. There is nothing to open and nothing to click.

**Nothing to see is also an answer:**

**No open cases for Ana Giménez** means exactly that, and it is worth reading: it tells you the new case you are about to create is the right one.

If the caller is not somebody your account knows yet, no panel appears at all. The contact is still created for you at wrap-up, as before.

### The wrap-up says what it will create

Most dispositions create nothing, and that is the normal outcome — *resolved on first call* is meant to leave nothing behind. Some open a case. Which of the two a wrap-up does is not something you can tell from the word in the dropdown, so the form says it, under the field, as soon as you choose:

> ✓ This disposition opens a work item in **Installations**.

The line only appears when something **will** be created. No line means no case, which is the ordinary answer and not a sign that anything is misconfigured.

Two variations you may see:

- **"...on the board for this call's queue."** The disposition creates a case but leaves the board to the queue you took the call on. Which board that is depends on how your account maps its queues, so the form does not guess.
- **"This disposition opens a work item."** with no board named. The case is created on a board you do not have access to read, so Desk Center does not name it.

**Changing a disposition afterwards does not open a case:**

The line appears while you are wrapping up a call. The disposition editor in **Call history** does not show it, because changing a disposition after the fact does **not** go back and create the case it would have created at the time.

### Filing the call on a case that already exists

When you choose a disposition, the same list gains a tick box per case:

> **Add this call to**
> ☑ Billing mismatch `3 calls`
> ☐ Porting delay `1 call`
> *Nothing ticked → a new case is opened.*

Tick one and the call joins that case — the recording, the notes and the wrap-up land on the thread the problem already has, instead of starting a fourth one about it. **You can tick more than one**, for the call that settles a billing question and chases a porting date in the same five minutes.

Tick nothing and a new case is opened, which is what happened on every call before this existed.

**The ticks are deliberately not offered during the call:**

You can read the list from the moment the call connects, but you choose at the end — because what the call was actually about is not always what it looked like in the first ten seconds.

**Two contacts with the same number:**

If more than one contact in your account carries the caller's number, the panel says so and lists them instead of showing anybody's cases. Desk Center will not guess which of two duplicates is calling. Merge them in **Contacts** and the cases appear from then on.

**Not seeing it?:**

It needs Desk Center on the account **and** at least one board you can read — the same two things the Desk Center link in the UCP sidebar needs. It also stays hidden on a campaign call whose lead caller ID your account has chosen to mask.

The panel shows at most three cases — it shares the card with the call's own details. When there are more, it says so, and the rest are in Desk Center.

### The company on a case

A case's sidebar carries a **Company** row when there is one to show, and it is worth knowing which of two things you are reading.

| What you see | What it means |
| --- | --- |
| **Company** · Acme Ltd | The case itself records Acme. It was about Acme when the work happened, and it stays that way whatever changes afterwards. |
| **Company** · Acme Ltd · *via contact* | Nobody recorded a company on this case, so this is **where the contact works today** — read just now. It will change if that contact is edited. |

Clicking it opens the company, when the company is a **record**. A company that is still the word typed on a contact has no page, so it reads as plain text.

**Most cases show via contact , and that is normal:**

A case only records a company when its contact was linked to a company **record** at the moment the case was created. Since most companies are a typed word, most cases carry nothing and the row is read from the contact instead.

**Merging two contacts does not move the recorded company:**

It moves everything else — every case of the absorbed contact becomes the survivor's, and the name on the card follows. The **recorded** company stays as it was, because it says who the work was for rather than who the person is now.

Which is why a case that records one company can sit next to a contact who is at another. Neither is wrong; they answer different questions.

A case with no contact, or a contact with no company, has **no Company row at all**.

### Linking one case to another

A case's sidebar has **Linked cases**. Type the key of another case — `SALE-1` — and press **Link**.

The commonest reason is that one piece of work produced another: a sale closes and an onboarding begins. Those are **two cases on purpose** rather than one case moved to the onboarding board — the teams are different, they finish on different conditions, and one case would lose the record of how long the first part took.

That is the difference between linking and [moving a case to another board](https://docs.qvoice.net/desk-center/for-agents/#moving-a-case-to-another-board): link when the work **produced** more work, move when the work was **filed in the wrong place**.

Each row says **which way round** the relation is:

|  |  |
| --- | --- |
| **Spawned** ONB-1 | this case produced that one |
| **Spawned by** SALE-1 | that one produced this |

**A link does not control anything:**

It records that two pieces of work are related and nothing more. Either case can move to any column, be closed, or be reopened with the other one still open — linking a sale to an onboarding does **not** stop you closing the sale.

**Type the key, not the title:**

`SALE-1` is what identifies a case. If nothing carries the key you typed the link is refused and says so — and a case on a board you have not been given reads exactly the same way, which is deliberate: the message never tells you that a case you cannot see exists.

Removing a link leaves both cases exactly as they were. Nothing is deleted except the statement that they were related.

### Moving a case to another board

A case's sidebar says which **Board** it is on, with a **Move** button beside it. Use it when the work turns out to belong somewhere else — a billing question opened on Support, an infrastructure job that arrived as a general enquiry.

The dialog asks two things:

|  |  |
| --- | --- |
| **Board** | where the case is going. Only boards you have been given appear, and the board it is already on does not. |
| **Lands in** | which column it arrives in. Already chosen for you — see below — and you can change it. |

You can add a line saying **why**. It is stored on the case's history beside the move, not as a comment.

**What comes with it:** the key, the title, every comment, every call and chat on it, its attachments, its links, who it is assigned to, and the time it is already promised. Nothing is retyped and nothing is left behind.

**The key does not change, so a board carries foreign prefixes:**

A case that was born on Support keeps `SUP-412` after it moves to Billing. The key says **where the work was born**, not where it is now — which is what keeps every link anybody pasted anywhere still working. So do not read a prefix as the board a case is on; the Board row is what says that.

**Which column it lands in.** Two boards almost never share column names — one says *Pending QA* and the other *Being checked* — so Desk Center matches the **stage** instead: work that was waiting on somebody arrives waiting on somebody, and finished work arrives finished. If the new board has no column at that stage, the case lands in that board's first column, and the dialog shows you which one before you press **Move**.

**What does not change:** the clock. A case that was promised a four-hour answer is still promised it, and a promise already broken stays broken — moving a case is not a way to reset either. See [Promises About Time](https://docs.qvoice.net/desk-center/promises/).

**Fields the new board does not ask for** stay on the case, out of sight. They are not deleted, and they come back if the case is moved back.

**Some boards do not let their work leave:**

A board can be set to keep its work — see [Boards and Fields](https://docs.qvoice.net/desk-center/boards-and-fields/#settings-that-belong-to-the-board). On one of those the **Move** button is there but will not press, and says why. Work leaves such a board by being finished.

## Companies

**Contacts** has two views, and the switch sits above the list: **People** and **Companies**. The second one is the same contacts read the other way round — grouped by the company written on each of them.

A company here is **the word somebody typed on a contact**, not a record you create or edit. There is no company list to maintain and nothing to merge: a company exists because a contact carries it, and it stops existing when the last contact stops carrying it.

### The list

Each row is a company and how many of your contacts are at it. The box above narrows the list as you type, and it ignores case while it does — so searching `acme` shows you both `Acme Ltd` and `ACME S.A.`, which is how you find out that both exist.

**Some companies may be missing, and the list says when:**

Building this list means reading your contacts, and that read has a limit. Past it the list says so — **“some companies may be missing”** — and the way to reach a person it did not cover is to look them up in **People**, whose search asks the server.

### One company

Opening a company gives you three tabs.

| Tab | What it answers |
| --- | --- |
| **People** | Who is at this company. Everyone is listed, including the people with nothing open, with their first number and address and any cases of theirs. |
| **Cases** | Where this company is in your process. Cases are grouped by **board**, open work first and closed work below it. A board with no case for this company is not shown. |
| **Timeline** | What has happened. Every call, chat and email that **produced work** for anybody at this company, newest first, each row naming the case it belongs to. |

**Closed cases stay here.** A board stops showing finished work once the archive window passes; a company does not, so you can see that this customer has paid and is live. The Cases tab says so where the closed ones are listed, because the two screens genuinely disagree and it is deliberate.

**A timeline row names its case for a reason.** A WhatsApp message sitting next to a go-live email does not mean those two are the same piece of work — they are two cases on one company — and the case name on each row is what tells them apart.

**The counts are what you can see:**

`6 people · 4 open · 11 closed` counts the work on boards **you have been given**. Somebody with access to a board you do not have opens the same company and sees larger numbers. Neither of you is seeing a bug: a page that hinted at the cases it was hiding would be telling you about a board you are not on.

### Making a company a record

Most companies stay what they are: a word typed on a contact. A company you deal with often can be turned into a **record**, with **Make this a company record** on its page.

Once it is one, the company page gains a block at the top holding what the account knows about it, and **Edit** there changes it:

|  |  |
| --- | --- |
| **Also known as** | the other spellings this company answers to |
| **Domain** | `acme.com` |
| **Notes** | one standing description, the way a contact's note works |
| **Tags** | typed here, as words separated by commas — the catalogue under **Desk Center → Tags** covers people, not companies |
| Fields | whatever your account defined under **Desk Center → Company fields** |

A tick beside a company in the list means it is a record.

**Aliases are the reason to make one:**

`Acme` and `Acme Ltd` are two companies until a record says otherwise. Add `Acme` as an alias of `Acme Ltd` and **everybody carrying either spelling appears on one page** — without editing a single contact.

Spelling still has to match **exactly**, so add a line per spelling your people actually typed. And **no two companies may answer to the same name**: if an alias is already taken, the save is refused and says so.

**Making a record does not move anybody:**

The contacts carrying that company are linked to it, and they also keep the company written on them. Somebody written down afterwards with the same company appears on the page without being linked, and a contact whose company you later correct to another spelling stays on the company they are linked to. Nobody is lost either way.

**Somebody may have made the record already:**

If two people press the button, the second gets **that company is already a record** — and nothing is duplicated. Refresh and the record is there.

You cannot start a case from a company page. Work is created against a **person**, on a board.

## Your own email

**Your name → Notifications**

Choose which kinds of update you want emailed: work assigned to you, status changes, blocked work, new notes, and being mentioned.

Some may be unavailable: the account has switched them off for everybody, and that is not something you can override.
