How It Works
From payment to activation.
The Digital Twin lifecycle stays attached to the tenant that purchased it: payment, onboarding, consent, knowledge ingestion, testing, approval, activation, Revenue OS handoff, and reporting.
Lifecycle
- 01
Business
Company details, services, operating hours, and owner context.
- 02
Personality
Tone, vocabulary, values, phrases, and prohibited language.
- 03
Knowledge
FAQs, pricing, SOPs, policies, source materials, and offers.
- 04
Writing Clone
Approved examples, generated profile, and approve/edit/regenerate review.
- 05
Voice
Explicit authorization, approved samples, and revocation controls.
- 06
Video
Likeness authorization, source assets, and provenance checks.
- 07
Sales
ICP, objections, promotions, pricing boundaries, and escalation rules.
- 08
Customer Service
FAQs, cancellations, complaints, emergencies, and routing.
- 09
Test Lab
Run scenarios, inspect sources, confidence, approvals, and risk flags.
- 10
Activate
Checklist for consent, training, approvals, and autonomy limits.
Command Center
Operational tabs
Operating Modes
Level 0 — Off
No actions. Training and configuration only.
Level 1 — Draft Only
Generates outputs but cannot send or publish.
Level 2 — Approval Required
Prepares actions and waits for tenant approval.
Level 3 — Approved Automation
Executes only approved workflows within configured boundaries.
Activation only happens when the twin is safe.
Consent must be complete, required profiles approved, safety rules configured, escalation contacts ready, and public-facing actions limited to approved autonomy levels. No cross-tenant access. No unrestricted autonomy.