Available foundation
Contact Management
Built around structured contact records, status-aware data, and organization-scoped access.
Platform foundations
Tools for responsible email, with the right safeguards in view
PiztleFlow is being built in layers: first, permission-aware audience and campaign foundations; then, carefully introduced delivery infrastructure. Feature status is stated plainly so teams can understand what is available, in development, or planned.
PiztleFlow features
Audience foundations
Organize recipient data with permission, data hygiene, and clear ownership in mind.
Available foundation
Mailing Lists
Organize legitimate audiences into lists without losing the connection to contact eligibility.
Available foundation
CSV Imports with Consent Confirmation
Designed to require an explicit confirmation of permission before a controlled import is executed.
Available foundation
Recipient Eligibility Checks
Campaign preparation is built to account for consent and suppressed-recipient states before an audience is used.
PiztleFlow features
Campaign preparation
Prepare communications deliberately before provider delivery capabilities are introduced.
Available foundation
Email Templates
Reusable content foundations help teams prepare consistent campaign messages and subject lines.
Available foundation
Campaign Management
Built around drafting, audience selection, and reviewable campaign preparation—not unbounded sending.
In development
Sending Job Preparation
In development: durable preparation and recipient snapshots for accountable sending workflows. This site does not represent live provider sending.
In development
Scheduling Architecture
The platform architecture is being designed to support clear, reviewable scheduling when delivery capabilities are introduced.
PiztleFlow features
Recipient protection
Keep recipient preference and negative-delivery signals central to every future sending workflow.
Available foundation
Suppression Management
Built around preserving manual, unsubscribe, bounce, and complaint suppression states without silently reactivating a contact.
In development
Unsubscribe Handling
Recipient-state safeguards are in place; recipient-facing unsubscribe flows are being developed alongside delivery capabilities.
In development
Bounce Handling
The contact model is designed to support provider-derived bounce handling. Provider event ingestion is not yet available.
In development
Complaint Handling
The contact model is designed to keep complaint states out of eligible audiences when provider feedback workflows are introduced.
PiztleFlow features
Delivery roadmap
Delivery infrastructure will be introduced cautiously, with provider rules and sender reputation in view.
Planned
Email Authentication Support
Planned domain workflows for SPF, DKIM, and DMARC are intended to help customers establish authenticated sending identities.
Roadmap
Deliverability Monitoring Roadmap
Planned reputation and deliverability awareness tools will support responsible operational decisions. PiztleFlow does not guarantee inbox placement.
Transparency is a product principle
We will not describe a roadmap item as a live capability, or represent responsible delivery practices as a guarantee of inbox placement. Read the rules that guide platform use before getting started.