Features
The product gets stronger when the workflow stays connected.
These are the customer-facing surfaces that shape the day-to-day experience now: campaigns, trend engines, guidance, readiness, publishing, promotion, notifications, analytics, and collaboration.
Build around campaigns, not isolated posts.
Campaigns are the center of the planning workflow. They make it easier to turn a launch, theme, or announcement into a structured sequence you can revise, schedule, publish, and analyze.
Create one campaign and expand it into multiple posts.
Keep drafts, schedule decisions, and later analysis attached to the same initiative.
Avoid copy-paste planning across disconnected tools.
Customer-safe summary
What this means in practice
Campaigns are the center of the planning workflow. They make it easier to turn a launch, theme, or announcement into a structured sequence you can revise, schedule, publish, and analyze.
Why it matters
It keeps the workflow inside one product surface instead of forcing teams to stitch together separate planning, drafting, scheduling, and reporting tools.
Four trend engines keep planning grounded.
VI Engine separates trend work into clearer engines so your team can see what matters now, what timing fits, what is translating across channels, and what fallback context still keeps the workflow moving.
Native trend discovery engine (Core): Surfaces what is gaining traction now so campaigns and drafts start closer to the moment you are publishing into.
Timing and format engine (Core): Helps decide when something should go out and which format gives that idea the best chance to land well.
Cross-network insight engine (Core): Turns account and channel patterns into practical guidance so your team can see what is translating across platforms.
Resilient fallback engine (Resilience layer): Keeps research and planning useful when live signals are thin, delayed, or unavailable, so the workflow does not stall.
Customer-safe summary
What this means in practice
VI Engine separates trend work into clearer engines so your team can see what matters now, what timing fits, what is translating across channels, and what fallback context still keeps the workflow moving.
Why it matters
It keeps the workflow inside one product surface instead of forcing teams to stitch together separate planning, drafting, scheduling, and reporting tools.
Manual control and agent help can live in the same system.
Some work starts with a quick draft in Composer. Some starts as a conversation with the agent. Both paths share the same workspace context, trend engines, campaign memory, and publishing destinations.
Use Composer when you already know the shape of the post.
Use the agent when you want research, sequencing, and next-step help.
Carry voice, campaign, and platform context across both surfaces.
Pro and Team include model selection — choose hosted providers or local-compatible AI for teams that need content to stay on their own infrastructure.
Customer-safe summary
What this means in practice
Some work starts with a quick draft in Composer. Some starts as a conversation with the agent. Both paths share the same workspace context, trend engines, campaign memory, and publishing destinations.
Why it matters
It keeps the workflow inside one product surface instead of forcing teams to stitch together separate planning, drafting, scheduling, and reporting tools.
Know what is ready before you press publish.
Readiness is a visible product surface. Instead of discovering connection, capability, or quota problems after the fact, the workspace warns you earlier and frames the next practical step.
See connection and capability cues before avoidable failures happen.
Keep publish warnings tied to the channel reality you are working with.
Use readiness checks as product guidance, not hidden operational trivia.
Customer-safe summary
What this means in practice
Readiness is a visible product surface. Instead of discovering connection, capability, or quota problems after the fact, the workspace warns you earlier and frames the next practical step.
Why it matters
It keeps the workflow inside one product surface instead of forcing teams to stitch together separate planning, drafting, scheduling, and reporting tools.
Recommendations should tell you why they exist.
VI Engine is designed to surface next-best actions and recommendations in plain language, so guidance feels grounded in your workflow instead of like a black box making claims from nowhere.
See why a recommendation is being surfaced before you act on it.
Keep next-best-action guidance attached to campaigns, publishing, and promotion.
Make suggestions easier to trust because they stay tied to real signals.
Customer-safe summary
What this means in practice
VI Engine is designed to surface next-best actions and recommendations in plain language, so guidance feels grounded in your workflow instead of like a black box making claims from nowhere.
Why it matters
It keeps the workflow inside one product surface instead of forcing teams to stitch together separate planning, drafting, scheduling, and reporting tools.
Keep the thread between one campaign and the next.
Campaign memory means the system keeps useful context attached to the work. Your team does not have to rebuild the same learnings every time a campaign evolves, expands, or needs a follow-up push.
Carry learnings forward instead of starting from zero every round.
Keep memory attached to the workspace and campaign it belongs to.
Use continuity to make the next draft, schedule, or promotion decision faster.
Customer-safe summary
What this means in practice
Campaign memory means the system keeps useful context attached to the work. Your team does not have to rebuild the same learnings every time a campaign evolves, expands, or needs a follow-up push.
Why it matters
It keeps the workflow inside one product surface instead of forcing teams to stitch together separate planning, drafting, scheduling, and reporting tools.
Move from organic work into paid amplification without losing context.
Publishing and promotion belong in the same workflow. When something starts landing well, VI Engine helps you move from a scheduled post into a promotion decision without redoing the work in a separate system.
Publish now or schedule ahead from the same workspace.
Promote strong posts when the signal says they deserve a bigger push.
Keep organic and paid decisions attached to the same campaign story.
Customer-safe summary
What this means in practice
Publishing and promotion belong in the same workflow. When something starts landing well, VI Engine helps you move from a scheduled post into a promotion decision without redoing the work in a separate system.
Why it matters
It keeps the workflow inside one product surface instead of forcing teams to stitch together separate planning, drafting, scheduling, and reporting tools.
Keep teams aligned without chasing status updates.
Notifications help the right people see publishing, quota, promotion, and collaboration events sooner. The point is less chasing, fewer surprises, and a cleaner operating rhythm.
Use the in-app notification center to track what changed and what needs attention.
Set email preferences so important updates reach you outside the workspace too.
Give shared teams better visibility without turning every event into noise.
Customer-safe summary
What this means in practice
Notifications help the right people see publishing, quota, promotion, and collaboration events sooner. The point is less chasing, fewer surprises, and a cleaner operating rhythm.
Why it matters
It keeps the workflow inside one product surface instead of forcing teams to stitch together separate planning, drafting, scheduling, and reporting tools.
Keep creative work and performance learning in the same loop.
Image generation, vision analysis, and analytics become more valuable when they stay close to the campaign and publishing flow that produced them.
Generate images inside the same workflow used for drafts and campaigns.
Use vision analysis when you want visual context to shape the next round of content.
Read advanced analytics on Pro and Team to refine the next campaign, not just summarize the last one.
Customer-safe summary
What this means in practice
Image generation, vision analysis, and analytics become more valuable when they stay close to the campaign and publishing flow that produced them.
Why it matters
It keeps the workflow inside one product surface instead of forcing teams to stitch together separate planning, drafting, scheduling, and reporting tools.
Add seats and roles only when collaboration becomes real.
The Team tier adds shared workspace membership with customer-facing roles team_admin and member, keeping the solo experience lean while still giving growing teams a clear upgrade path.
3 seats on Team.
15 connected accounts on Team.
Shared campaigns, shared reporting, shared publishing visibility.
Customer-safe summary
What this means in practice
The Team tier adds shared workspace membership with customer-facing roles team_admin and member, keeping the solo experience lean while still giving growing teams a clear upgrade path.
Why it matters
It keeps the workflow inside one product surface instead of forcing teams to stitch together separate planning, drafting, scheduling, and reporting tools.
Channel status
Live channels stay distinct from roadmap channels.
Facebook Pages
Publish photo, video, link, and status posts to Pages you manage through the shared composer and scheduling workflow.
Instagram professional accounts
Connect professional Instagram accounts for platform-aware drafting, scheduling, and publishing across feed posts, reels, carousels, and stories.
LinkedIn personal profiles
Publish directly to personal profiles from the same workspace used for your other live channels.
X / Twitter
Retained as a roadmap channel, but not marketed as live until end-to-end publishing is production-ready.
Threads
Still gated from the public product surface and not available for customer publishing today.
Reddit and YouTube
Planned as future channel expansions after the current live publishing paths stay stable for customers.