Available in the private beta
- Invite-controlled accounts, separate workspaces, team roles, and profile recovery.
- SMTP and SendGrid email sending with connection checks and workspace rate controls.
- Customer-owned WhatsApp accounts in every Wepy workspace, with Meta setup, verified senders, approved templates, campaigns, shared Inbox, automations, and Results. Sending still requires eligible contacts, channel consent, and provider readiness.
- 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.
- Automation workflows with the triggers, conditions, schedules, and limits shown in the builder, plus run 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.
Request access and get help setting up
- Open Request access and tell us about your business, the channels you want to use and the setup help you need. Choose a beta plan that fits your team. Do not include passwords, API keys or contact lists.
- Confirm your email using the link we send. Email confirmation submits your request for review; it does not create an account or guarantee approval.
- We approve up to five businesses per day for personal setup help. Requests may be waitlisted, and there is no guaranteed approval or response time.
- If approved, open your invitation and sign in or create an account with the same email. You set your own password. A legacy invitation creates the approved free-beta workspace without payment authorization. Other invitations may require separate owner authorization and secure payment setup under the terms shown in that invitation. Requests and email verification do not authorize payments.
- Follow the setup checklist to connect providers, prepare consented contacts, create a first campaign and review a test. Personal setup help has a US$100 value. One-time setup help is included at no cost for approved beta workspaces. This is a beta offer for getting started, not ongoing campaign management.
Choose your workspace plan
Open Settings > Beta access to review Launch, Growth and Scale. Each plan includes the same supported channels, with different team-seat and active-automation limits. Owners and admins can change a legacy beta plan; members can view it. A separately authorized billing agreement belongs to the owner, and plan changes cannot silently change its agreed price. Review the options shown for your workspace.
- Legacy beta access remains ₹0. Future reference prices are not current charges, and choosing a legacy beta plan does not save a card or authorize a payment.
- Only if you separately authorize future billing: Wepy subscription fees are ₹0 during beta, which has no fixed end date. At enrollment, the workspace owner explicitly authorizes the selected plan's future monthly charges. We will email at least 30 days before the first charge with the start date and exact total. Billing then renews monthly unless canceled. Cancel before billing starts to avoid the first subscription charge. Canceling during free beta pauses new outbound sending immediately; you can still sign in, read and export data. Sending-provider fees are separate.
- Under beta-autopay-v1, monthly charges after beta per workspace are Launch ₹999 + ₹179.82 tax = ₹1,178.82; Growth ₹2,499 + ₹449.82 tax = ₹2,948.82; Scale ₹4,999 + ₹899.82 tax = ₹5,898.82. Tax is 18%. Review and authorize the exact total during enrollment. This guidance does not announce that new enrollment is available.
- Secure payment setup may involve a ₹1 authorization or bank transaction. This is not a Wepy subscription fee. Any reversal or refund depends on the payment provider and bank; Wepy does not promise an automatic refund.
- Existing legacy beta requests, invitations and workspaces keep their no-automatic-charge terms. They are not enrolled in future billing without a separate, explicit owner authorization.
- Billing review and cancellation remain available for existing agreements when new enrollment is unavailable. For an existing owner-authorized agreement, use Settings > Beta access to cancel before the displayed first-charge date and time to avoid the first subscription charge. No replacement payment method is required to cancel. During free beta, new outbound sending pauses immediately; any already-paid access lasts through its paid period. You can still sign in, read and export data. If a charge is already in progress, cancellation does not guarantee it can be stopped or refunded. Canceling future billing does not delete your workspace or stop your separate provider charges.
- Seats include the owner, other members and unexpired pending invitations. Resending or accepting an invitation does not use an extra seat.
- Only active automations count toward the automation limit. Pause unused workflows, or choose a larger plan if you need more capacity.
- A smaller plan must fit your current usage. Remove unused members or invitations and pause extra automations before switching.
- Your own sending providers may charge separately. Wepy plans do not include provider credits.
Not yet available
- Unannounced conversion of legacy beta workspaces to paid plans. Legacy customers must separately authorize recurring billing. Existing agreements and cancellation controls remain in place when new enrollment is unavailable.
- A full drag-and-drop email builder or email-safe media upload library.
- Direct APNs connections, silent or background marketing Push, critical alerts, machine-learning send-time optimization, or importing device tokens directly from another Push provider.
- 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.
- Support access to change another workspace's data, sign in as a customer, or share private system logs.
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 for new features, fixes, and changes that affect your work.