Vuti

AI social media employee

How it worksStudioTemplatesPricingPlatformsFor ClaudeDocs
Sign inStart free
OverviewStartCreatePlan & publishEngageWorkspaceUse casesResources
Overview

Get started

QuickstartConnect channels

Create

Nia assistantComposeCreative StudioInspirationCatalog

Plan and publish

Plan a calendarReview & approvePublishingAutomations

Engage and improve

TodayInboxAnalytics

Workspace and control

Brand setupMemoryAssetsPlans & credits

Use cases

Choose a workflowFor foundersFor creatorsFor teamsFor agencies

Integrations and resources

Connected appsPlatform supportFeature availabilityTroubleshootingGlossaryFAQChangelog
Use case · Agency

Run a repeatable client workflow without mixing brand context

Give every client a distinct workspace, make source and approval ownership visible, and reuse the operating rhythm rather than the client’s private context.

Manage workspaces

8 min · Last verified 11 August 2026

Step 1
Create a boundary per client
Use a separate workspace for each client brand so voice, memories, assets, members, and channels remain scoped.
Review workspaces
Step 2
Build an approval-ready brand kit
Record approved offers, claims, phrases to avoid, audience context, voice examples, and the destination accounts.

Agree with the client on which facts are approved for routine use and which claims require case-by-case verification.

Open the Catalog
Step 3
Run the same campaign intake
Capture the objective, source material, deliverables, dates, reviewer, and final approver before generation starts.
Capture campaign sources
Step 4
Share the review surface
Invite ongoing collaborators or use a temporary public preview for limited external feedback.

Resolve comments in Vuti, then record the final approval in the review workflow. Disable public previews after the decision.

Prepare client review
Step 5
Report from delivered work
Separate creation status from publishing status, then use analytics and delivery history for the client readout.
Open analytics

What to standardize across clients

  • Campaign intake questions and naming conventions.
  • Review deadlines, comment resolution, and final approval responsibility.
  • Publishing-health checks and failure escalation.
  • Report structure and the questions each report should answer.

What must stay client-specific

  • Brand voice, audience, offers, approved claims, account credentials, source assets, performance data, and private feedback.
Do not use public previews for confidential campaigns

Public preview links are convenient for external feedback, but anyone with the active link may be able to open it. Disable the link after review and invite a workspace member when stronger access control is required.

Continue learning

Manage client workspaces
Configure brand context, members, and workspace ownership.
Read guide
Build evidence-led reporting
Compare performance and publishing reliability without overclaiming.
Read guide
PreviousFor teamsNextConnected apps
View MarkdownOpen in Vuti

Last verified Aug 11, 2026

Vuti © 2026. Product docs

HomePricingCreative StudioTemplatesBusinessPlatformsDocsPrivacyTermsSupport