Saltar al contenido
NuevoVer cómo
Nuevo

Attach files to any contact or deal

Upload, browse, download, and delete files right on a contact or deal, so contracts, proposals, and documents live next to the record they belong to instead of scattered across email and drives.

Publicado
Lectura
2 min de lectura

The signed contract is in someone's email. The proposal is in a shared drive folder nobody can find. The one-pager you sent is attached to a thread three weeks deep. Documents that belong to a deal end up everywhere except on the deal. Now they can live where they belong, attached directly to the contact or deal they're about.

What changed

Both contacts and deals now have a Files section. Drag a file onto the dropzone, or click to browse, and it uploads. The file list shows each file's name and size, so you can see what's there at a glance. Click a file to download it through a secure, time-limited link, or delete one you no longer need and it's removed right away. When there's nothing attached yet, a clear empty state tells you so.

There are sensible limits to keep things fast and tidy: up to 25 MB per file, and 100 MB total across all files on a single contact or deal. Enough for the contracts, decks, and documents that actually belong on a record, without turning your CRM into a file dump.

How to use it

  1. Open a contact (from Contacts) or a deal.
  2. Go to its Files tab.
  3. Drag a file onto the dropzone, or click to browse and pick one.
  4. It appears in the list with its name and size.
  5. Click a file to download it, or use delete to remove it.

Why it matters

A record is only as useful as the context attached to it, and for a lot of deals the most important context is a document: the contract, the signed order form, the proposal that set the terms. When that file lives in a personal inbox or a drive folder, it might as well not exist for anyone else on the team. Covering a deal means first going on a scavenger hunt for its paperwork.

Keeping files on the contact and deal itself means the paperwork travels with the relationship. A teammate opening the deal sees the contract without asking you for it. The document, the conversation, and the timeline are all in one place, which is the whole promise of a CRM built into your outreach tool, extended to the files that close deals. It sits right alongside the Contact 360 and Deal 360 view where the rest of a record's story lives.

Todas las novedades

Prospección que sigue cuando te desconectas.Leads, emails, seguimientos y respuestas, resueltos.

Conecta buzones ilimitados y deja que los agentes de IA busquen leads, escriban cada email y hagan seguimiento. O envía tus propias plantillas en modo manual. Desde $29/mes.

Empieza tu prueba de $1 Ver precios

$1 por 3 días · Cancela cuando quieras · Sin contrato

Instalar con IA

Tu agente de código configura la CLI y las skills de FirstSales por ti.

Prompt para Claude Code

I'm setting up FirstSales (https://firstsales.io), an AI outbound sales platform: campaigns, contacts, a reply inbox, deliverability and lead signals. Help me get my workspace sending real, good emails end to end, from Claude Code.

Read these first so you know how FirstSales works:
- Developer docs and API: https://developer.firstsales.io
- CLI: https://www.npmjs.com/package/@firstsales.io/cli
- Skills for coding agents: https://github.com/firstsalesio/firstsales-skills (read README.md and GUIDE.md)

Setup
1. Install the CLI: npm install -g @firstsales.io/cli
2. Install the FirstSales skills:
   claude plugin marketplace add firstsalesio/firstsales-skills
   claude plugin install firstsales@firstsales
3. Ask me if I already have a FirstSales account. If not, send me to https://app.firstsales.io to sign up.
4. Ask me to create an API key under Settings → API → API Keys, with only the scopes we need.
   Never ask me to paste the key into this chat. Tell me to run this in my own terminal, so the key stays hidden:
   read -rs FS_KEY && firstsales auth login --api-key "$FS_KEY"; unset FS_KEY
5. Run `firstsales whoami` and tell me which workspace and organisation we are connected to.

Then ask me about my business: what I sell, who I sell to (roles, company size, countries), my best customers, and what I use today for outbound (tools, lists, mailboxes). Walk me through:
1. Teaching FirstSales my business: website, offer, proof points and case studies in the knowledge base, so the AI writes like someone who knows the product.
2. Connecting my sending mailboxes and checking my sending domain: SPF, DKIM, DMARC and warm-up. If anything is unhealthy, tell me the exact DNS record to add.
3. Bringing in contacts: import my CSV or CRM export into a clean list, remove duplicates and bad emails, and block domains I must never email (customers, competitors, my own).
4. Building my first campaign: the right list, senders, steps and timing. Write the sequence with me, show me the drafts, and do not launch until I say yes.
5. Setting up Signals if it fits: find people engaging with LinkedIn posts about topics my buyers care about, and turn them into leads.
6. Inviting my team and giving each person the right access.

Once campaigns run, show me how to work the reply inbox from here: which replies need an answer, draft responses in my voice, and move good conversations into deals. If I use Cal.com, connect it so follow-ups can offer my booking link (not the first email).

Throughout, as you learn about my business, proactively suggest and help create:
- Reply templates for the questions and objections my prospects are likely to raise, based on my product, site and codebase if you can see them.
- Campaign ideas and segments worth testing, with the reason for each.

Safety rules:
- Show every change as a dry run (--dry-run) first and wait for my yes. Never send emails, launch campaigns or delete anything without my yes.
- Tell me before anything that spends credits, and how many.

Be opinionated. If the docs give a sensible default, just use it. Don't make me choose between five options.
Developer docs ↗npm: @firstsales.io/cli ↗GitHub: firstsales-skills ↗