Useful answers. Practical next steps.

Browse the practical guides without an account, or open Help & support after signing in. A support request keeps your question and the operator’s replies together. Include the page and what happened, but never send passwords or API keys. Public contact details are listed only when confirmed.

Saved work stays in your account. Your current account baseline or administrator allocation determines the remaining capacity. If you are over a limit, you can still read and export existing work, but must reduce usage or arrange more capacity before adding that resource. One-time credit packs do not increase workspace capacity.

Administrators have a separate Launch readiness area for email diagnostics, operational alerts and scheduled SQLite snapshots. A snapshot is marked verified after an independent restore and integrity check; operators can repeat the drill. An independent watchdog can detect an unavailable service. Actual retention, off-site copies and notification delivery depend on the deployment settings.

Brand profiles, reviewed product facts, reusable media, content plans, editable storyboards, campaigns, tasks, client review and versioned delivery are available. Client records, intake, branded portals, service periods and content-performance reviews connect the first brief with the next plan. Public examples use fictional data.

Choose a product campaign, creator series or client-services example in the tour. A brand can begin with approved product context, a creator with a recurring audience question, and an agency with a client brief. From each stage you can open its practical guide or the corresponding workspace tool.

The current planner uses local templates with facts and context you supply and review. It does not call a writing model, crawl a URL or automatically verify product claims. Plans and projects retain the context you deliberately select.

Enable an intake template for the client, collect answers and supplied references, then review each item. Clients can save drafts and resubmit requested changes. A manager accepts the current completed request into one empty linked campaign; acceptance does not generate projects or videos, and retrying it does not duplicate the campaign.

No. Intake review confirms that the supplied brief is ready for planning. Claims still need a separate knowledge-base review before you select them as approved product context. Uploaded references retain their supplied rights notes and are not automatically added to the private media library.

Yes. Set a studio name, logo, welcome and accent for the client. Choose its enabled intake templates and explicitly share linked campaign reviews, delivery packages or retained performance summaries. Service-period visibility is selected separately. A campaign association alone does not publish everything in it.

They compare an agreed target with planned work, current approvals, handed-off storyboard versions and the remaining delivery target for a service period. These are different measures. Repeated handoff of the same project revision does not increase the delivered count, and current deliverables are storyboard versions rather than generated videos.

The confirmation shows the period and all five counts. If source evidence changes before you confirm, closing is refused and the active period refreshes for another review. A successful close retains its snapshot; later work does not rewrite it. You may still withdraw portal visibility and prepare the next period with the original calendar span.

Team Owners and Admins manage client relationships, intake review, sharing and service periods. Editors can prepare and submit intake requests; Viewers have read access. The application checks current permissions, so a role change or removal can withdraw access from an already open workflow.

No. Record actual publication links and manually supplied measurements, or map your data to the unified CSV template. There is no connected social account or automatic analytics collection. Comparisons and reports show the observations you supplied, rather than proving causation or predicting revenue.

Use the unified UTF-8 template, preview row errors, duplicate identities and existing-data conflicts, then fix all errors before the atomic import. A batch supports up to 100 rows and 150 KB. Compare two to six publications from the same platform, traffic type and observation window. A blank measurement means unknown; measured zero remains zero.

Write the lesson and a concrete next test, then have a manager confirm the current note and evidence. Changes require confirmation again. Use in new plan retains the confirmed conclusion and supporting evidence in a new private plan, where you adapt the brief and prepare the next drafts. It does not automatically share private context with a team.

A manager can explicitly share a retained client-safe performance summary in the client's portal. It includes selected supplied analytics, coverage and confirmed conclusions at sharing time. Internal workflow counts, private relationship notes and source libraries are excluded. Share a new summary when you want to show newer evidence.

Yes. A private portal link lets its holder use the enabled intake and selected shared work until expiry or revocation. A standalone review link also supports feedback and a decision on its frozen storyboard. You copy and send the links yourself. Labels and reviewer names are self-declared, not verified customer identities.

Client contacts, relationship notes, private source libraries and billing stay outside the portal. Create portal links for 1, 7 or 30 days, revoke them or remove individual shares. Original review and delivery expiry rules still apply. Archiving a client disables portal access; restoring it does not revive revoked or expired links.

Current approved storyboard snapshots, their approval records, separately labelled publishing copy, a manifest and selected reference files. The ZIP includes HTML, JSON and SRT. The client does not receive internal tasks or private source profiles; an uploaded MP4 is a supplied reference, not a generated result.

If a client reference is missing or its size no longer matches the stored record, the application stops the download and asks the team to restore it from a private backup. The file can be downloaded again after restoration. Reference uploads require supplied usage rights and remain subject to existing file and owner-storage limits.

No. Video, voice, music and payment provider adapters remain reserved. Production and checkout flows are simulated. Available outputs include HTML storyboards, JSON, SRT and approved-delivery ZIPs. No money is collected.

No. Service fulfilment is an operational record of agreed work, separate from platform credits, membership controls and payment collection. Closing retains a summary; preparing the next period copies a proposed schedule for your review. Neither action creates an invoice or automatically charges or renews a client.

The current workflow tools are available across workspace plans, with different team, member, client, storage and portal-link capacities. Monthly memberships provide capacity during an active confirmed period; one-time packs add credits only. Existing accounts retain previous limits. Client-service targets are separate from these capacities and from production credits. Checkout remains simulated.

Planned dates, publication links and performance measurements are manual records. No social publishing or social analytics account is connected in the current version.