> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/partner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.360dialog.com/partner/get-started/alphas-and-betas.md). # Alphas and Betas Early-access programs 360dialog runs with Meta: which ones are open to partners today, their status, how to join, and answers to the questions partners ask most. Alphas and Betas give partners early access to selected WhatsApp Business Platform features before they reach general availability (GA). You test them with real clients, we collect the feedback and pass it to Meta's product teams. Scope, eligibility and specifications can change during a program. Enable a pre-release feature for a client only when you have a fallback. ### Program stages * **Alpha**: limited functionality, small test group, specifications still moving. * **Beta**: broader access and more stable. Enrollment is still controlled, usually by Meta through allowlists, sometimes by 360dialog as well. * **GA**: generally available. The feature leaves this page and lives in the regular documentation. ## Programs open to partners | Program | What it enables | Status | How to join | | --------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [WhatsApp Login](https://docs.360dialog.com/partner/get-started/alphas-and-betas/whatsapp-login) | Onboard businesses that use the WhatsApp Business App to the Cloud API without a Facebook account. They authenticate with the app on their phone. | **Open Beta since October 2026**. On for every partner. Not enabled for EU-based clients, no timeline. No GA date from Meta. | Integrated Onboarding: nothing to do, it is already on. Self-hosted Embedded Signup: run it on your own Meta app and config, asking your partner manager or 360dialog support to have your Tech Provider Business Portfolio ID allowlisted by Meta. | | [Max price for marketing messages](https://docs.360dialog.com/docs/resources/marketing-messages/max-price-for-marketing-messages) | Cap what a client pays per delivered marketing message, per template, on the Marketing Messages API. Meta charges that amount or less. Templates without a max price keep the rate card. | **Open Beta since 1 October 2026** on Meta's side. GA tentatively Q2 2027, when max price becomes the standard way to pay for marketing traffic in eligible countries. Supported on the 360dialog Messaging API, EEA and UK recipients excluded. | Nothing to request. Set `optimization_spec` on a marketing template through the Messaging API or WhatsApp Manager and send through the marketing messages endpoint. Full guide in the client docs. | | [Self-service PLBV via Partner API](https://docs.360dialog.com/partner/get-started/alphas-and-betas/self-service-plbv) | Submit and track Partner-Led Business Verification cases for your clients through the Partner API instead of a support chat. | **General availability, early access**. Live in production for every eligible partner, field names and statuses can still be refined. PLBV submissions are paused and resume during October 2026 with updated eligibility criteria. | Available on the Growth and Premium Partner Plans, no allowlist. Share expected volumes with your 360dialog contact before integrating. | {% hint style="info" %} Enrollment forms for closed programs stop accepting responses once Meta or 360dialog close the program. If a form you received earlier is closed, the program has either moved to GA (see below) or stopped onboarding new participants. {% endhint %} ## Programs that reached general availability These started as Alphas or Betas with 360dialog partners and are now open to everyone. Use the regular documentation. | Program | Where to find it now | | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Direct Send API (Utility messages without templates) | [Direct Send](https://docs.360dialog.com/docs/messaging/direct-send). GA for the Utility category. The Authentication category is still access-restricted by Meta, ask your partner manager if a client needs it. | | Voice messages (native voice notes with `voice: true`) | [Voice Message Beta Program](https://docs.360dialog.com/partner/messaging/media-messages/voice-message-beta-program). Available to all Cloud API numbers, no allowlisting. | | Calling API (voice calls on WhatsApp) | [Calling](https://docs.360dialog.com/docs/messaging/calling) | | Marketing Messages API (formerly MM Lite) | [Marketing Messages](https://docs.360dialog.com/partner/messaging/marketing-messages) | ## How participation works Programs are opened at partner level. Your clients take part through you, and you remain their point of contact. We validate every feature internally before inviting partners. In return for early access we expect: 1. Real business scenarios on real numbers, enabled client by client. 2. Issues reported with reproduction steps, timestamps and request or webhook IDs. 3. Feedback on what worked and what did not. Both reach Meta. You get onboarding guidance, the program documentation on this site, and a direct line to the 360dialog product team for the duration of the program. Each program documents its own endpoints and payloads. When a feature needs a dedicated endpoint, it is added to the Partner API or the Messaging API and described on the program page. ## FAQ **How do I know whether a feature is still in beta?**\ This page is the index. Each program page carries a status banner at the top, and a feature moves to the GA table above once Meta announces general availability. **How do I request access to a program?**\ Write to your partner manager or to [support](mailto:support@360dialog.com) with your partner ID, the clients or volumes you have in mind and the use case. Some programs depend on Meta allowlists, so access can take a few days and is not guaranteed. **Meta contacted my client about an alpha or beta, or told them to contact their BSP. What now?**\ Check this page first: if the program is listed above, the program page says what to do, and for max price there is nothing to enroll in. If it is not listed, forward Meta's message to us. 360dialog takes part in a subset of Meta's programs, and some features Meta promotes, such as passkey authentication or payments in new countries, are not available through 360dialog yet. We confirm whether we are in the program and what the next step is. **Can my clients join a program directly with 360dialog?**\ No. Programs are run with partners. Your clients use the feature through your integration or through 360dialog's Integrated Onboarding under your partner account. **Does testing cost extra?**\ There is no program fee. Standard Meta messaging and conversation charges apply, together with your usual 360dialog plan. **Does a beta affect my production setup?**\ Pre-release features run in production on real numbers, there is no separate environment. Enable them gradually, keep the standard flow as fallback and check the program page for known issues before rolling out to a client. **Can I share the program pages with my clients?**\ Yes. The pages on this site are public. Keep the beta status visible in your own communication, especially the limitations listed on each program page. **When does a beta end?**\ Meta decides GA dates and rarely shares them in advance. We update this page and the partner newsletter when a program changes status or opens to more partners. ## Feedback and issues Use the channel agreed during onboarding (Slack Connect, email or support chat). Include the affected partner and client IDs, the WABA or phone number, timestamps and the request or webhook payload. Clear reports go to Meta faster. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.360dialog.com/partner/get-started/alphas-and-betas.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.