What we are working toward

This roadmap communicates direction, not a delivery guarantee. Priorities can change as provider APIs, customer needs, and product constraints evolve.

Safer migration and sync previews

Shipped: migration preflight, per-contact failure records and retry of failed contacts. Next: expected-versus-actual reconciliation and provider capacity warnings.

Reusable field-mapping templates

Define a project-level contact schema once, reuse mappings across providers, validate destination field types, and retain per-rule overrides.

Consent evidence and optional double opt-in

Store stronger consent evidence, support optional confirmation workflows, and make consent history available in exports and activity.

Provider health and deliverability alerts

Surface connection health, API failures, rate limits, retry volume, destination growth, and recommended actions before problems become silent data gaps.

Data privacy and retention tools

Shipped: contact export, permanent erasure with provider requests, and configurable retention. Next: anonymization and a dedicated privacy-request history view.

Request or discuss a capability

Contact us with the workflow and provider involved. Specific delivery dates should only be published after the work is committed.