Skip to content
Aptirodocs
Menu: Manage accounts, contacts and deals

Manage accounts, contacts and deals

Accounts, Contacts and Deals are the three record lists you will spend the most time in. All three work the same way: search at the top, sortable columns you can show or hide, and a choice of 25, 50 or 100 rows a page. Those choices are remembered the next time you open the page.

Accounts

Clicking a row opens a quick-view drawer with the fields you edit most often. The icon at the end of the row opens the full account page instead, which is where everything about an account lives together: overview, contacts, deals, scan history, triggers, upcoming calendar events and the full activity feed, so a call needs no tab-hopping to prepare for.

Clients, under its own sidebar entry, is the same list filtered to client accounts, with health score and renewal date shown as colour-coded bars and chips so an account sliding towards risk is visible at a glance.

Contacts

A contact belongs to one account and can be marked as that account's primary contact. Import Contacts accepts a CSV: Aptiro looks at the column headers to guess which column is the name, account, role, email, phone and LinkedIn URL, shows you a preview before anything is saved, and reports how many contacts and accounts were created or updated, with any rows it could not use listed separately.

Deals and pipeline stages

A deal sits in one pipeline stage and carries a type: new business, renewal, expansion or repeat project, each shown as its own coloured chip. Filter the Deals list by type, and watch the toolbar's running total update as you do.

The stages a deal can be in, and the probability each stage implies for forecasting, are set up in Settings > Pipeline stages. A stage with active deals in it cannot be deleted, so reordering or renaming is always safe to try.

Bringing in your own fields

Add a custom field to accounts or contacts from Settings > Custom fields when something your business tracks has nowhere to live yet. A custom field can also be the field a trigger source reads from, such as the account field that holds a YouTube channel URL.

See also: build and share a report over any of these record types.