Agency questions,
answered.
What the current launch scope covers,
and what it deliberately does not.
Quick context
A few things to know before you bring this into an agency workflow.
- Narraplex is currently positioned around agencies.
- Launch scope is: approved scripts and handoff, not full production review.
- Client approval is: approve or request changes at the variant level.
- Outputs are drafts with human review, not auto-published posts.
FAQ
Is this just another AI copywriter?
No. The core value is the workflow between brief, variants, internal review, client approval, version lock, and future learning from those decisions.
How do approvals work today?
The workflow is: clients approve or request changes on a whole variant snapshot.If the script changes, it becomes a new version and goes back for review.
Can clients keep using WhatsApp or email?
Yes. The client can still respond in those channels. Your team can log the decision or feedback back into Narraplex so the approval trail stays intact.
Do client workspaces learn from each other?
No. Learning is tenant-local by design. Client-specific references, approvals, and feedback stay inside that workspace.
How do you reduce hallucination risk?
Drafting, critique, and review checks stay separated so the same pass does not author and validate everything end to end. Human reviewers still remain responsible for final sign-off.
Do you replace Asana, Monday, or Notion?
No. Narraplex owns the high-signal review and approval moment. Status can still sync outward to the project-management tools your team already uses.
Is full production already in scope?
Not in the public launch scope. Lane A is script-only delivery. Full production support and post-production review loops are planned for a later phase.
Can we request a DPA before the pilot?
Yes. A DPA is available for agency and enterprise pilots, along with supporting trust materials like retention, subprocessor, and security summaries.