Workspace overview

The rest of these docs cover getting your data into Clivly. This section covers what your team does with it once it is there.

Everything here runs on the records your mapping produces. You do not build any of it: mapping a table to Contact is what populates the contacts list, and the same rows drive search, deal links, and the calendar.

Records

Contacts and Companies are the two record types every workspace has. Both list views page through large datasets rather than loading everything, and both support search and sort.

A company shows how many contacts belong to it, and can carry an email, a phone number and a point of contact — one named person to chase. That point of contact can be driven by your own data during sync, so it stays correct without anyone maintaining it by hand.

Records can be edited and archived from the workspace. Archiving keeps the record and its history; it stops appearing in the default lists.

Custom objects

A mapped entity that is not a contact or a company gets its own list, driven by the same machinery. See Advanced custom entities for building one from several tables.

Deals and pipelines

A workspace can have several pipelines — sales, renewals, subscriptions — and each is its own board, with its own stages, rules and pricing. Switch boards from the Deals page; a deal created there lands on the board you are viewing. Every workspace starts with a default pipeline, and deals synced from a mapping land on the pipeline that mapping feeds.

Deals have three views: a pipeline board, an all deals table, and a won list. Totals, win rate and the won list are scoped to the pipeline you are looking at.

A pipeline's stages are yours to define — name them, reorder them, and mark each as open, won or lost. Reporting reads win rate and revenue from those types, never from stage names, so renaming a stage never changes what a pipeline is worth.

Stage rules

Rather than dragging every deal by hand, a stage can carry rules that move deals into it from your app's own data — "deals land here when…". A rule is a list of conditions, all of which must be true; two rules on the same stage mean "or".

Rules only ever move a deal between stages. They never write to your application's tables.

Clivly warns you when a rule can never match — because it names a field your mapping no longer sends — and when two stages' rules could both claim the same deal.

Deal value

A deal's value can be typed by hand, or derived from your data: pick the column holding a seat count and the column holding a plan, then price each plan. Clivly computes seats × price and adds any flat fee. Say whether your prices are monthly rates or amounts charged each billing period; with the latter, annual amounts are normalised to a monthly figure so every card is comparable. A configuration made before this choice existed keeps its original calculation until you pick one.

Values are stored in cents. Editing a price does not retroactively revalue existing deals — each deal picks up the new price the next time its row syncs.

If an input is missing or unreadable, Clivly leaves the stored value alone rather than writing zero. A renamed column should look like a configuration problem, not a collapsed pipeline.

When someone overrides automation

Dragging a deal to a different stage, or editing its value by hand, tells Clivly that a human decided this one. Automation stops touching it — permanently, until you say otherwise.

Such a deal is marked "stage set by hand" or "value set by hand", and its detail panel offers Resume automation to hand it back. The two are independent: a deal can track your data for its value while you hold its stage.

Tasks and notes

Tasks and notes attach to any record — a contact, a company, a deal, or a custom object — and one item can link to several at once. They appear both on their own pages and on the record they relate to.

Tasks carry an assignee, a priority and a due date — all-day, or at a time shown in each member's own time zone — and appear on the calendar as soon as they have one. Neither tasks nor notes are hard-deleted; they archive.

Calendar

Month, week and day views over every dated task and deal close date, with quick add, drag-to-reschedule, keyboard shortcuts and shareable URLs. See Calendar.

Inbox

Chats from the chat widget and your team's email threads arrive in one shared Inbox. There your team claims, answers, closes and snoozes them, and email alerts mean nobody has to watch it. The optional support assistant greets visitors and can answer common questions first. See Inbox.

Mail

Write and send email to contacts from Clivly's shared sender, your company's own domain or a member's connected mailbox; send to a filtered audience; and keep drafts. See Mail and email sending.

Ask your CRM

Members can ask plain-language questions about their data and get read-only answers that name the records used. Off until an owner or admin turns it on. See Ask your CRM.

AI agents

External agents — Claude Code, or your own — can connect over MCP with their own token and permissions. Every change they make is recorded under their name, and sensitive ones wait for a person's approval in Drafts. See Connect an agent.

Reports and dashboard

The dashboard summarises open work and pipeline health. Reports cover pipeline value, win rate and activity over time — all computed from stage types, so they survive a stage being renamed or reorganised.

Settings worth knowing