Replify now gives multi-brand, multi-location, and regional teams more precise control over who sends, where content publishes, how engagement is handled, and which analytics profile is being reviewed. These updates cover the 12 supported channels only; no advertising management or additional networks were added.
Multiple profiles on every supported channel
You can connect more than one WhatsApp number, Instagram account, Messenger identity, X profile, LinkedIn identity, TikTok profile, YouTube channel, Google Business location, Pinterest account, Reddit account, Telegram identity, or Snapchat Public Profile in the same workspace.
Set a primary profile to simplify new work. The primary selection is a default, not a global override. Existing conversations retain the channel account that owns them, and publishing, templates, broadcasts, automations, commerce messages, and WhatsApp Flows use an explicitly selected or safely pinned sender. If an older conversation is ambiguous in a workspace with several senders, Replify stops and asks for repair rather than sending from the wrong identity.
A connection manager built for real operations
The Channels page now presents each connected profile as an independent account. Authorized managers can add, reconnect, rename through the network, make primary, manage, disconnect, or release eligible resources without affecting unrelated profiles. Capacity, pending setup, verification, suspension, billing attention, and release states are shown with actions appropriate to the exact account.
For WhatsApp, dedicated business tools cover business profile fields, connected and provisioned numbers, calling settings and history, eligible groups, blocked users, and provider account events. Billable and irreversible actions require explicit confirmation.
A richer engagement workspace
Open a social interaction from the shared inbox to inspect the original content, source, connected profile, rating, media, status, sentiment, lead score, tags, and history. Depending on the network and the individual item, an authorized teammate can:
- reply publicly, privately, or to a Google review;
- request a human-approved AI draft;
- hide or unhide, like or unlike, or delete an eligible interaction;
- remove a Google review reply;
- assign or unassign, archive or reopen, and mark whether a reply is needed;
- review both local action history and the network response.
Item-level eligibility matters. Replify intersects the profile permission with the actual interaction flags and explains why an action is unavailable.
Publishing lifecycle controls
The publishing workspace now supports editing and rescheduling scheduled drafts, cancelling future posts, safely retrying failed targets, and unpublishing eligible published targets. Supported external posts can be synchronized into Replify on demand.
Published text can be edited for supported X, LinkedIn, YouTube description, Google Business, Pinterest description, Reddit self-post body, and Telegram targets. Instagram, TikTok, and Snapchat do not support unpublishing through this workflow. External on-demand post sync is unavailable for Telegram and Snapchat.
The composer also includes current network-specific controls such as Instagram collaborator, feed, audio, tag, first-comment, and AI-media settings; LinkedIn native resharing and documents; YouTube visibility, audience, playlist, and synthetic-media fields; Pinterest board sections and AI disclosure; Reddit subreddit and flair controls; Telegram formatting and delivery controls; Snapchat content type; and TikTok privacy and commercial-content settings.
Advanced analytics
The analytics workspace now adds daily performance, best time to post, content lifespan, publishing frequency, follower growth, post timelines, Instagram account and audience insights, YouTube channel and audience insights, LinkedIn organization analytics, and TikTok account insights. Availability follows each connected profile's permission, account type, add-on state, and network range limits.
WhatsApp templates, Flows, and business operations
Multiple-number safety now extends to templates, broadcasts, automations, commerce messages, and WhatsApp Flows. Templates can collect dynamic URL parameters, copy codes, and recipient-specific header media. Standard Flows can be sent from the exact bound number, with responses and version history visible. A legacy remote Flow with no safe account binding is blocked until an authorized user selects the owning profile and synchronizes it.
What did not change
Replify still supports exactly 12 organic channels. Threads, Discord, Bluesky, Facebook Page publishing, and advertising APIs are not included. Network permissions continue to determine which actions and metrics are available, so reconnect a profile when Replify asks for a newer permission and review the channel guide before changing a production workflow.
Start at Channels, then use the analytics guide and the article for the exact channel you operate.
Still need help?
Tell us what you were trying to do, the channel involved, and what you expected to happen.