UnifyDesk connects WhatsApp, email, SMS and advertising providers so teams can work from one customer communication workspace without replacing the underlying services.
Public access is coming soon. Labels describe the public rollout direction, not a guarantee that a configured account can send or synchronize today. Each provider has its own authorization, setup and readiness requirements.
Messaging
WhatsApp, SMS and channel delivery providers.
PROVIDER LAYER
WhatsAppIn development
Connect a company-owned business account and number for customer conversations and provider-aware outreach. Number readiness, account validation and applicable template rules remain prerequisites.
The current managed SMS provider direction. Prepare the sender and required templates, review destination requirements and confirm provisioning before treating SMS delivery as ready.
An additional messaging provider under evaluation. This is an exploration status, with no committed public launch date or promise of production availability.
Inbox connections and managed sending infrastructure.
PROVIDER LAYER
GmailIn development
A mailbox connection for email conversations, inbox synchronization and replies. Its role is distinct from managed campaign delivery; connecting Gmail is not a promise of bulk sending.
Connect Microsoft mailbox conversations to the customer workspace. Mailbox authorization and provider permissions apply. This inbox connection is separate from campaign sending infrastructure.
The current managed email direction for campaign delivery. Sender or domain verification, provider readiness and capacity matter before sending. Email usage is a separate billing layer.
An additional campaign delivery provider choice planned for public rollout. Provider setup and real delivery validation are still required; this label does not announce a live public integration.
An additional email delivery provider choice planned for public rollout. Sender setup, provider authorization and delivery readiness must be confirmed before a company relies on this connection.
Provider-native campaign workflows through one Ad Center.
PROVIDER LAYER
Google AdsIn development
Bring connected advertising account and campaign work into the Ad Center direction. Provider account permissions and supported capabilities apply; media spend stays with Google.
Organize connected Meta advertising account and campaign work in the same workspace direction. Provider permissions remain necessary and Meta media spend is separate from platform access.
One workspace above the providers you already trust.
The integration layer keeps provider-specific capabilities visible while giving teams a connected direction for conversations, broadcasts and campaign operations. Company-authorized connections should be ready and validated before they are relied on for customer work. Managed email and SMS usage and external advertising spend remain separate from platform access.
Start with the customer workflow: inbox conversations, outbound campaigns or advertising. Then confirm the account your company controls, the permissions needed and the provider's requirements. A mailbox and a campaign sender serve different purposes.
Three checks before connecting
Confirm account ownership and an authorized company member.
Review verification, sender, template and provider limits.
Check availability, workspace entitlements and usage costs.