Contacts & leads

What it is

Aden has three related but distinct contact surfaces:

1. Contacts: a per-team address book of people: collaborators, fans, booking agents, studio engineers. Each contact can optionally be linked to an Aden user account.

2. Demo submissions: artists submit tracks to a team (e.g. a label or publisher) for review. The receiving team rates, accepts, or rejects each submission. Submitters see live status updates.

3. Org enquiries: organisations interested in joining Aden fill out a landing-page form. The Aden admin team triages these in the admin panel and optionally pushes them to a CRM such as Attio.

The internal leads pipeline (admin-only) is the sales counterpart to org enquiries. It tracks potential teams and organisations through a full sales lifecycle with contacts, activity logs, and CRM sync.

Using it

Managing your team's contacts

From your team's Contacts page you can add and edit people in your team's address book. Each contact can hold a name, email, phone, role, and optional link to a platform Spotify/Google account.

Every contact also has a free-form Notes box on its detail page. Dietary requirements, who their manager is, what they asked for last time. It saves with the rest of the record and is what stays true about the person; dated contact points (calls, meetings, follow-ups) belong on the Activity timeline next to it.

Importing contacts in bulk

Open Add contact → Import to bring in many people at once. Organisations have the same importer at Contacts → Import; contacts imported there are owned by the organisation rather than a team. Three sources:

1. CSV files: drag in one or more CSV files. Each file is mapped independently: you choose which column maps to which contact field per file, so files with different layouts can be imported together in one go. The mapping screen shows, for every column, a live sample value from your data, an include/exclude checkbox, and the field it maps to. Columns we auto-detect are pre-filled. High-confidence matches are applied silently, while looser guesses are marked as suggestions (✨) you can reject with one click. LinkedIn connection exports are auto-detected and mapped for you. The "Import N contacts" button (and ⌘/Ctrl+Enter) imports straight from the mapping screen, or step into Preview & edit for per-row editing. Columns that don't match a built-in field can be imported as custom fields: they extend the standard contact schema, are stored against each contact, and show up on the contact's detail page. Accept the auto-suggested custom field, rename it, or reject it.
2. Google Contacts: connect a Google account (one click, via the same app-connect flow used for the inbox) and pull your address book directly. Name, email, phone, company, job title, address, website, social links, birthday, notes and your Google contact groups all come across, and land in the same preview list as a CSV. Fields Google has no column for arrive as custom fields. Auto-saved pulls the contacts Google saved for you automatically rather than the ones you saved yourself. Only contacts with an email address can be imported; the import tells you how many were left out.
3. People you've emailed: with the same Google account connected, Scan sent mail reads the recipients of your recent sent messages and rolls them up per person, most-emailed first. It's the address book you never got around to making: everyone you've actually written to, checked against your existing contacts so only the missing ones are new. No-reply and system addresses are skipped, and message bodies are never read.
4. Imported rows are run through spam detection (built-in rules you can toggle on/off individually, plus your own custom rules) and duplicate detection against your existing contacts before anything is saved. You can review and edit every row before confirming the import.

Submitting a demo

To submit music to a team (label, publisher, or playlist curator):

1. Go to the team's public profile and find their Demos page, or navigate to Demos in your own team's sidebar to manage your submissions.
2. Click Submit demo, choose or paste a track URL, add a description and an optional peak-moment timestamp.
3. The receiving team is notified. You can track the status (pending → accepted or rejected) from your demos list.

Receiving and reviewing demos

As a team receiving demos:

1. Open Demos in your team sidebar to see all incoming submissions.
2. Rate and leave a status on each demo. Accepted demos can be linked to a track in your library.
3. Rejected demos trigger an email notification to the submitter.