Available in the private beta
- Invite-controlled accounts, workspace isolation, team roles, and profile recovery.
- SMTP and SendGrid email sending with connection checks and workspace rate controls.
- Contacts, Lists, Tags, Segments, custom fields, CSV jobs, forms, hygiene, suppression, and recipient-controlled email topics.
- Saved Email campaigns, source-code and live preview editing, scheduling, templates, and reusable blocks.
- Bounded automation workflows, schedules, supported triggers, conditions, and execution history.
- Campaign, automation, delivery, and provider-supported engagement results.
- Unified Push for Web and native Mobile apps: customer-owned VAPID or Firebase credentials, explicit consent, signed identity binding, app-scoped topics, controlled tests, templates, campaigns, automations, delivery policies, experiments, recommended timing, conversion attribution, and privacy-safe results.
- Verified sign-in email changes and protected personal account deletion with last-owner checks.
Not yet available
- Self-service paid plans and payment collection. Private-beta access is currently free and Razorpay work is on hold pending approval.
- A full drag-and-drop email builder or email-safe media upload library.
- General WhatsApp availability. Account, template, campaign, inbox, automation, and results workflows are staged only for specifically enabled workspaces until controlled Meta provider testing is complete.
- Direct APNs credentials, silent/background marketing Push, critical-alert entitlement claims, opaque machine-learning timing, and blind raw-token imports from another Push vendor.
- Automatic duplicate-contact merging. Wepy keeps duplicate review and consent-safe merge decisions explicit.
- A public roadmap, community forum, guaranteed support response-time SLA, or public status page.
- Cross-workspace support mutations, customer impersonation, or raw log access in the support console.
No fake capability
These limits are deliberate. Wepy will show unavailable states honestly rather than display demo data or imply unsupported provider coverage.
What beta participants should expect
- Use controlled, permissioned audiences and test important sends with addresses your team owns.
- Report product issues with the page, action, approximate time, and a redacted screenshot.
- Do not include credentials, recipient data, message content, provider payloads, or unsubscribe links in support messages.
- Review this guide and the Changelog when Wepy publishes a customer-visible beta release.