Set the foundation.
Review your use case, account, number and onboarding requirements.
WhatsApp Business API
Put WhatsApp to work across customer updates, support and enquiry intake. We connect the official Business Platform to the tools and people behind your business.
Explore the conversation ↓A considered message, a natural reply and a clear handoff. Explore three ways the platform can support your business.
A shared inbox and connected tools give people a useful place to step in. Automation supports the handoff.
Context attached.Ready for the team.
Account setup, useful message design and the right integration. The scope follows your business and your tools.
Plan the account, business number and integration route around your existing setup. We support onboarding and the required configuration; eligibility and reviews remain with Meta.
Prepare useful templates, organise their categories and support the review process. Build reply flows around the customer service window and your business requirements.
Give your team a place to handle conversations, assign ownership and carry context into the next response. Inbox features depend on the solution selected.
Connect supported CRM and operational tools. Map relevant events, contact context and follow-up tasks, with clear access and ownership.
Use supported reply buttons, lists and media to make the next step easier. Plan the conversation and when it should hand over to a person.
Agree consent handling, access, retention and escalation. Build around WhatsApp policies, the selected tools and your organisation’s requirements.
Design the journey around the people you serve and the work your team needs to do.
Order confirmations, shipment updates and a straightforward route to product support.
Review your use case, account, number and onboarding requirements.
Prepare messages, integrations and the handoff your team needs.
Validate the flow, check access and agree ownership before activation.
A transactional email API is a cloud-based service that allows applications to send individual, triggered emails programmatically — such as a purchase receipt when an order is placed, a reset link when a password is forgotten, or an alert when a threshold is crossed. Unlike bulk marketing email, transactional email is one-to-one, time-sensitive and expected by the recipient, which means inbox placement rates are typically high when the sending infrastructure is set up correctly.
Send via REST API for custom apps or SMTP relay for existing systems with no code changes.
SPF, DKIM and DMARC configuration ensures your emails are authenticated and trusted.
Track delivery, opens, clicks, bounces and spam reports for every send.
Build reusable HTML email templates with variable substitution for personalisation.
Automatic suppression of hard bounces and spam complaints to protect sender reputation.
Dedicated sending IP for high-volume senders who need maximum inbox placement control.
Authenticate your sending domain with SPF, DKIM and DMARC — we walk you through it.
Add the REST API or SMTP settings to your app — takes under 30 minutes.
Use the dashboard to track delivery rates and act on any reputation signals.
The Business Platform provides APIs for integrations and scaled messaging workflows. A shared inbox, automation and CRM connections are built or provided through the selected solution.
Replies to a user message can be sent without a template within the 24-hour customer service window. Outside that window, the Platform requires approved message templates. Recipient permission and other policy requirements still apply.
No. Business verification and verification badges are separate processes. Any badge or account eligibility is controlled by Meta and is not guaranteed by this service.
We review supported APIs, account features and available access. The integration scope is agreed around the tools your team uses.
Pricing depends on the implementation, selected provider or software, usage and applicable Meta charges. We scope these for your setup; no fixed platform price is claimed in this preview.
No. The message workspace, inbox and enquiry form are local previews. Live sending requires a configured account, the appropriate permissions and an agreed implementation.