Skip to content
NewSee how

Delete your data: contacts, workspace & org

Self-serve data deletion. Bulk-delete contacts, or schedule workspace/organization deletion with OTP verification and a 72-hour grace window.

Tutorials
Billing & Credits
min read
5 min
steps
7 · Intermediate

  1. Two levels of deletion

    You can delete individual contacts, or schedule deletion of an entire workspace or organization. Both are self-serve — no support ticket required.

  2. Delete specific contacts

    Go to Contacts, select rows, and use the bulk Delete action. Contacts currently in use by an active campaign may need to be removed from it first, or deletion can fail for that contact.

  3. Open Settings → Privacy

    Find Workspace deletion and Organization deletion. You need workspace-delete permission for the workspace, or to be the org owner with org-delete permission for the organization.

    Open Settings → Privacy

  4. Confirm the target name

    Type the exact workspace or organization name to arm the request, then click Send verification code.

  5. Verify with the emailed OTP

    Enter the 6-digit code sent to your (masked) email, then click Schedule deletion. Deletion is scheduled for 72 hours from now.

  6. Understand the consequences

    Outbound jobs pause and queued sends are cancelled. Organization deletion also disables billing renewal and cancels your subscription when it finalizes. At least one active workspace must remain.

  7. Cancel within the grace window

    During the 72-hour window the workspace stays visible and you can hit Cancel deletion any time. After 72 hours it finalizes automatically.

Pro tips

  • Remove contacts from live campaigns first

    Deleting a contact used by a live campaign can fail. Remove them from the campaign (or complete/pause it) first, then delete.

  • The 72-hour window is your undo button

    If you scheduled deletion by mistake, hit Cancel deletion before it finalizes: there's no recovery after that.

  • Only the owner can delete an org

    Organization deletion requires the org owner role plus org-delete permission: a plain admin can't do it. Plan who runs it.

  • Delete the workspace, not the org, for a single client

    Org deletion cancels your subscription on finalize. If you only need to offload one client or workspace, delete just the workspace.

Frequently asked questions

Is data deletion self-serve or do I file a support ticket?

Self-serve. Contact deletion is a bulk action; workspace/org deletion is under Settings → Privacy with OTP verification.

How long until deletion actually happens?

Workspace and org deletions schedule for 72 hours out and can be cancelled any time during that grace window.

Why do I have to type the name and enter a code?

Deletion is destructive, so it requires typing the exact target name plus a 6-digit OTP emailed to the requester — two barriers against accidents.

Who can delete an organization?

Only the organization owner who also has org-delete permission. Workspace deletion needs workspace-delete permission.

What happens to sending when I schedule deletion?

Outbound jobs pause and queued sends are cancelled. Organization deletion also disables billing renewal and cancels the subscription when it finalizes.

Can I delete just one person's data?

Yes — select them in Contacts and use the bulk Delete action. Contacts tied to an active campaign may need removing from it first.

Billing & Credits

Outreach that keeps going after you log off.Leads, emails, follow-ups and replies, handled.

Connect unlimited mailboxes and let AI agents find leads, write each email and follow up. Or send your own templates in manual mode. From $29/mo.

Start your $1 trial See pricing

$1 for 3 days · Cancel anytime · No contract

Install with AI

Your coding agent sets up the FirstSales CLI and skills for you.

Prompt for 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 ↗