Questions wey people dey ask often

Pick one high-volume workflow and launch it in a single channel. Prove wey answers dey accurate and escalations reach di right people, then expand to more channels and packs.

General-purpose copilots dey tied to one vendor's model. Threada dey a work platform: every request becomes a tracked WorkItem with policy controls, governed execution, and outcome analytics — across any LLM.

No. Threada works alongside your current tools. It captures and structures requests, then executes approved actions in di systems you already run.

AI handles understanding and structuring. Policy controls, review queues, and approvals handle di exceptions. People stay in di loop for anything high-risk.

Containment, time-to-resolution, escalation quality, approval cycle time, and action success — outcomes on di record, no interaction counts.

Run evaluation gates wey test extraction, routing, grounding, and action behaviour. Roll out gradually with canary traffic, shadow mode, and one-click rollback.

A WorkItem dey di central unit of work in Threada — a typed, lifecycle-managed object wey captures intake, decisioning, execution, and outcome for every request.

Traditional message-only automation tools manage requests one message at a time. Threada manages work: intake, policy, approvals, actions, plus outcome measurement, with audit trails plus governance controls.

Yes. Most teams begin with a single workflow scoped to one channel or workspace plus expand incrementally as confidence builds.

Websites, uploaded documents, API connectors, and feed-based sources. Each dey registered as a managed knowledge asset with its own freshness and retention policy.

You set sync cadence plus stale thresholds per source. Threada alerts on freshness drift plus failed syncs so evidence stays current.

Yes. Citation requirements fit be applied per workflow and intent. Low-evidence responses dey routed review or escalation automatically.

Yes. Decision steps and approval requirements dey configuration-driven.

Yes. Channel-specific policy overlays fit override baseline workflow behaviour.

Yes. Kill switches fit disable execution per channel, workflow, or integration scope.

Yes. Telemetry dimensions include both channel plus workflow identifiers for cross-sectional analysis.

Yes. Execution telemetry includes integration plus action dimensions with success, retry, plus failure states.

Yes. Policy version dey available as a first-class reporting dimension for quality and outcome analysis.

Request wey complete without manual handoff because policy and evidence support safe automated path.

Any managed document or synced source record wey Threada keeps fresh for retrieval and evidence.

Yes. Any time. Changes go take effect for next billing cycle.

You go get warnings as you approach. There's a 7-day grace period to upgrade.

Save 20% when billing na annual.

No. We index am for retrieval only.

99.9% target with auto-scaling plus failover.

No. Threada enforces policy within AI work automation — it integrates with your existing GRC plus identity tools rather than replacing them.

Policy overlays dey versioned and scoped by tenant, channel, pack, and workflow. Every execution records di policy version wey bin dey active.

Yes. Lifecycle, policy, and action events dey exportable for external audits, SIEM integration, and regulatory reporting.

99.9% monthly availability with explicit RTO (4h) plus RPO (24h) objectives plus documented incident runbooks.

Stripe subscriptions + usage counters; grace period automation (D-3/D-1 notices) plus controlled disablement post grace.

Yes. Export feeds (GCS and BigQuery) and on-demand downloads dey available for compliance reviews.

No. Threada dey designed to orchestrate around existing systems through integrations and actions wey get governance.

Yes. Approval requirements fit be applied by workflow, channel, risk class, and action type.

Use EvalSuite gates for extraction, routing, grounding, and action behaviour before broad rollout.

Yes. Web fit be your first channel while you keep di same workflow primitives for future channels.

Yes. Integration execution dey asynchronous and supports retries with auditable error classes.

Use correlation IDs, WorkItem history, decision events, plus execution logs to reconstruct end-to-end flow.