# Keep Policy Data Current (/docs/guides/keep-your-members/keep-policy-data-current)



Your campaigns are only as good as the data behind them. Welcome calls key
off enrollment dates, check-ins key off effective dates, and save calls fire
when a policy's status changes. If careCycle doesn't hear about a new policy
or a cancellation, those campaigns don't either. So keeping your book current
is basically keeping your retention running.

The way to do that is to connect the system where you write your business, so
new enrollments flow into careCycle on their own, and to have a plan for
getting status changes like cancellations in quickly.

Connect an integration [#connect-an-integration]

Set it up once and new business flows in on its own:

* **Spark**: sends new policies sold and updates to the policies it knows
  about, as Active or Pending.
* **ConnectureDRX**: sends new enrollments as Pending when your agents submit
  Medicare applications in PlanCompare.
* **HealthSherpa**: submitted enrollments flow into careCycle as customers
  and policies automatically. See [Connect
  HealthSherpa](/docs/guides/getting-set-up/connect-healthsherpa).

See [Connect Your CRM](/docs/guides/getting-set-up/connect-your-crm) for
Spark and ConnectureDRX setup.

Spark and ConnectureDRX don't send cancellations. To catch those, have your
developer send status changes through the API, or import a list of
cancellations when you get one, so automations like Win-Backs still fire.

Build with the API [#build-with-the-api]

If you've got a developer, or a system we don't connect to natively, the sync
endpoints for
[Medicare](/docs/api-reference/sync/sync-medicare-customers-and-policies) and
[ACA](/docs/api-reference/sync/sync-aca-customers-and-policies) push customers
and policies straight in. See [API Keys](/docs/guides/developers/api-keys) to
get started.

When a sync changes a policy's status (say, from Active to Future Cancel),
that counts as a status change, so automations like
[Win-Backs](/docs/guides/template-library/medicare/win-backs) pick it up.

Which one should you use? [#which-one-should-you-use]

| Approach          | Best for                                                      |
| ----------------- | ------------------------------------------------------------- |
| **Spark**         | Ongoing sync of new and updated policies (Active or Pending). |
| **ConnectureDRX** | New Medicare enrollments as they're submitted.                |
| **HealthSherpa**  | Pulling in enrollments you submit through HealthSherpa.       |
| **API sync**      | Custom systems your developer can connect directly.           |

Not sure which fits? Your careCycle representative can help you pick.

<Callout title="What about imports?">
  [Importing a file](/docs/guides/getting-set-up/import-your-book-of-business)
  is how you bring your book in the first time, and it's handy for a one-off
  bulk update. It isn't a way to stay current, though: anything that changes
  after the upload won't reach careCycle until you import again.
</Callout>

<Cards>
  <Card title="Connect Your CRM" href="/docs/guides/getting-set-up/connect-your-crm">
    Set up an integration for continuous sync.
  </Card>

  <Card title="Connect HealthSherpa" href="/docs/guides/getting-set-up/connect-healthsherpa">
    Bring in HealthSherpa enrollments automatically.
  </Card>

  <Card title="Book of Business Field Reference" href="/docs/guides/reference/book-of-business-fields">
    Every field careCycle stores, and how records are matched.
  </Card>
</Cards>