# Save contacts from the extension into Reply

> Store revealed people in your account, add them to lists, push them into a sequence step, and know what the extension does with duplicates and list membership.

**Use Save or Edit and Save on a card to write the person into your account, then Move to.. and pick lists, a sequence and the step to start on. Lists in that dialog are a complete selection rather than an addition, so tick every list the contact should remain in. A contact who is already running in another sequence is moved out of it when you confirm, and a person who already exists in Reply is enriched instead of duplicated.**

_Status: Reviewed – written against Reply's product documentation on 2026-09-22, not yet confirmed against the running product._

## Goal

People found in the browser become real records on your [People](/specifications/contacts/)
page, filed into the [lists](/specifications/lists/) you chose and, where you want it,
started on a [sequence](/specifications/sequences/) step.

## Preconditions

At least one card sitting in the extension's **Search** or **CRM Sync** tab, plus the
permission to create and edit contacts in your workspace; sharing rules decide whether you
may touch records that belong to a teammate. If the destination sequence should start
immediately rather than after its configured wait, have it open so you can check its first
step.

## Steps

1. On a single card, click **Save** to store the person as they stand, or **Edit and Save** to correct a field first: the title, company, domain, city or phone are all editable before the record is written. For a selection, tick the cards and use **Save contacts** below them.
2. Click **Move to..** to open the destination dialog. Its subtitle counts what you are about to move, which is worth a glance when you used the select-all control.
3. Fill the **Lists** field. It accepts several lists at once, and typing a name that does not exist offers to create it; a list born this way belongs to you personally rather than to the whole team. Treat the field as the contact's complete list membership: with the current behavior, a list you leave unticked is removed from that contact, so re-tick the ones they should keep.
4. Choose a **Sequence** and then the **Step** the contact should begin on. Turn on **Ignore step delay** when you want the first message to go out on the next scheduled send rather than waiting out the step's delay.
5. Confirm. If any of the people are already running somewhere else, a dialog says so; "Contact is currently in another sequence. Would you like to move this contact to a new sequence?", and agreeing takes them out of the sequence they are in now. A second wording appears when the contacts carry personalization, and warns that the personalization is dropped in the move.
6. To build a person by hand instead of from a page, open the create-contact screen and fill it in. If the address is already known to Reply you are offered **Open** to jump to the existing record or **Overwrite** to replace its data with what you entered.
7. With Accounts turned on for your team, the company travels with the person and is linked to them. You can also create one on the spot from the contact screen, giving it an account name, a domain, an industry and a size.

## Expected result

The People page in the web app shows the new records, each one carrying the LinkedIn or CRM
link it came from, and the chosen lists appear on the contact. Contacts you pushed to a
sequence appear on that sequence's People tab on the step you picked.

## Verification

Open one saved contact in the web app and read its activity trail. Records created through
the current extension are marked as added via Findy, while ones added by the older
extension flow read as added via the Chrome extension: the wording tells you which path
wrote the record, which is the quickest way to confirm a save really came from the browser.

## What happens next

A contact placed on a step is live as soon as the sequence is running, subject to the usual
[enrollment checks](/behavior/contact-enrollment/); 
[launch the sequence](/how-to/launch-a-sequence/) if it is still paused. From the **People**
tab of the extension you can keep working the record: **Move to...**, **Send email**,
**Send WhatsApp message**, **Change status**, **Call**, and blacklisting either the person
alone or their whole domain.

## Common mistakes

- Using the list picker as an add button. It writes the membership you see, so a contact already filed in three lists keeps only the ones still ticked when you confirm.
- Reading "move" as "copy" for sequences. Confirming the prompt pulls the contact out of their current sequence; leave them where they are if you only meant to add a list.
- Expecting to edit a colleague's record. "Such contact already exists and you don't have the permissions to edit Team contacts" means the person is owned elsewhere in the team, not that the save failed technically.
- In teams that run on roles and permissions, members who are not the team owner may currently find that saving from the extension matches nothing at all; raise it with support rather than retrying.
- Assuming a saved person is enrolled. Saving files the contact; only the sequence half of the dialog starts outreach.

## Related

- [Contacts](/specifications/contacts/) · [Lists](/specifications/lists/)
- [Contact was duplicated](/troubleshooting/contact-was-duplicated/)
- [Permissions](/reference/permissions/)
- [Work tasks in the Chrome extension](/how-to/work-tasks-in-the-extension/)

## Build with Reply

- REST API: [docs.reply.io](https://docs.reply.io/api-reference/introduction) – create contacts and add them to a sequence programmatically
- CLI: [agents.reply.io/cli](https://agents.reply.io/cli) – bulk moves without a browser in the loop