All topics
English

Manage Open Enrollment · 5 min read

Select contacts and create cards in the renewal Kanban

Build a group from Contacts and create one linked Task per person in the appropriate board, with a recognizable title.

In this guide
  1. When to start from Contacts
  2. Filter by Immigration status and Contact Type
  3. Select contacts and set the destination
  4. Understand duplicate prevention and check results
  5. Check the context before issuing an update request
  6. Choose how to send
  7. Keep learning

For: CRMDAY One users with the Insurance profile.

When to start from Contacts

Use Contacts when the campaign starts with people, such as active clients with a specific recorded attribute, label or assignee. For an ACA policy book with an exact source-policy reference, consider starting from Policies.

Contacts creates a linked Task for each person who does not already have a card in the selected Kanban. The contact remains in your database; sending to Kanban neither transfers nor deletes it. The destination check avoids another card for the same contact.

Filter by Immigration status and Contact Type

  1. Open Contacts → Filters. Check whether existing quick-search text and filters still belong in the intended selection.
  2. Find Immigration status in the field catalog. Use Search field if needed and click Add.
  3. Choose Is and Temporary Protected Status (TPS). Use the recorded contact value; you do not need a technical field code.
  4. Add Contact Type, choose Is and select Customer Active. This commercial classification differs from policy status.
  5. Under Match, keep all criteria. A person must have TPS and Customer Active. Any criterion would include people matching only one.
  6. Click Apply filter. Canceling or closing does not apply pending filter changes.

Maria Costa and Bruno Silva match both conditions. A Lead with TPS is excluded because it is not Customer Active. For leads, change type to Lead. For multiple immigration statuses, use Is any of and select the required options.

The agency can customize Contact Type options; their names remain as configured. If a field is missing, check enabled fields, your access and agency setup. Do not assume a missing value means TPS or another status.

Combined filters: Immigration status = TPS and Contact Type = Customer Active, matching all criteria.
Combined filters: Immigration status = TPS and Contact Type = Customer Active, matching all criteria.
Selected values in both criteria: TPS and Customer Active.
Selected values in both criteria: TPS and Customer Active.

Check the total and pagination. Quick search and filters combine; Manage columns changes visible columns, not matching records. Clear filters and search text as needed before building another selection.

Two matching contacts selected to create cards.
Two matching contacts selected to create cards.

Select contacts and set the destination

  1. Check filtered contacts’ names, phone numbers, email addresses and preferred languages.
  2. Select intended contacts. Select visible records selects the displayed page; if using select all results, check the full count including other pages.
  3. Click Create Kanban cards in the action bar. The limit is 500 contacts per creation; split larger groups.
  4. Choose Destination Kanban, such as Open Enrollment 2027, and Destination stage, such as Prepare the list.
  5. Use Renewal 2027 — {{contact.name}} as Task name. Insert full name adds the field; each contact’s full name replaces it.
  6. Fill required additional fields, review selection and destination, then click Create cards.

Destination-stage automations may trigger. Use a preparation stage without automatic sending when reviewing the list first. Creating a card does not itself mean the form was sent.

Open Enrollment Kanban, preparation stage and personalized title before creation.
Open Enrollment Kanban, preparation stage and personalized title before creation.

Understand duplicate prevention and check results

Before creation, the system checks whether each contact already has a non-deleted card in the same destination Kanban. It checks all stages, other assignees and completed cards. It does not compare only titles or only the selected stage.

  • No destination card: create a new linked Task in the selected stage.
  • Existing destination card: skip the contact without creating another card, moving the original or changing its title/stage.
  • Card only in another Kanban: creation in the current destination is still allowed.
  • Card deleted into the recycle bin: it does not count as an existing card for this check.

Example: Maria Costa already has an Awaiting reply card in Open Enrollment 2027; Bruno Silva has none in that board. Selecting both for Prepare the list produces 1 card created and 1 contact skipped. Maria stays in her existing process; Bruno receives the new card.

Result: one card created and one contact skipped because a card already exists in the destination Kanban.
Result: one card created and one contact skipped because a card already exists in the destination Kanban.

Confirmation shows created/skipped counts and the reason. Zero created with everyone skipped can be correct. Each contact counts once as skipped even if several linked cards exist. Existing duplicate cards are not deleted.

Use Open Kanban and find the contact’s card before choosing the next step. If an existing card is reported but invisible to you, check filters and access with the agency administrator; the check includes cards outside your view. Do not create a second contact record to bypass it.

Protection uses the link to the same contact record. Different records for the same person are not merged. Check previous requests and invitations before sending again.

Writing 2027 in a title does not configure the form year. Review year, policy context and channel in the sending workflow.

Check the context before issuing an update request

Open the cards and check the linked contact, delivery details and reference coverage. A generic card created from Contacts does not itself identify a specific policy. The form uses available contact data and, depending on context, the related or flow-selected ACA policy. Resolve multiple-coverages or source-policy uncertainty before issuing a link.

Review the record and client answers; a Task title does not guarantee that all details from the correct policy have already been selected.

Choose how to send

For rule-based invitations, move checked cards to Automatic request after configuring orchestration. To control each sending group, keep them in Prepare the list and follow bulk sending from Kanban. Do not use both paths for the same group without checking existing requests.

Keep learning

Updated October 27, 2026.