Skip to content

Site search

Type to search pages, articles and docs

Security & human control

The line between autonomous and human-approved is written down — not left to chance.

Narrapulse runs your channels within a brand voice and escalation policy you sign off. Routine, pre-approved replies go out on their own; anything carrying legal, regulatory, or reputational weight waits for a named person before a word is published.

Controls

What holds the operation in place.

These are the boundaries and controls the service runs under — described plainly, without claiming certifications we do not hold.

Access scoped per customer

Channel credentials and customer data are held under FTLAB's shared security controls, with access scoped to each customer. Your channels are operated on your behalf and are not pooled with another brand's.

An immutable record

Every published item, every autonomous reply, and every escalation is logged immutably. You can evidence exactly what the system did on your behalf — what was sent autonomously and what a human approved.

Versioned, attributable policy

Brand voice, content calendar, escalation thresholds, and the enumerated autonomous-reply categories all live in the Policy Console. Policy changes are versioned and attributable to the human who approved them.

A firm line at public communication

The service draws a firm line at public communication carrying legal, regulatory, or reputational weight. It routes those matters to human judgement rather than acting on them.

How the boundary works.

Narrapulse is an AI-born service: AI colleagues do the operating work — drafting and sequencing content calendars, generating and scheduling posts across connected channel APIs, monitoring mentions and comments continuously, and preparing draft responses. Accountable humans govern, approve, and hold responsibility for all public brand communication and crisis handling. The boundary between the two is explicit and enumerated, not discretionary.

What runs autonomously

AI colleagues act against a machine-readable policy that a human has signed off in the Policy Console — brand voice, calendar, escalation thresholds, and the reply categories permitted to go out on their own.

Only routine, pre-approved reply categories are dispatched autonomously. Every other action is queued for human approval before it is published.

The system builds a per-brand voice and response model over time, which reduces the share of items needing human review while keeping the audit trail complete.

What waits for a person

Sensitive topics, complaints, and reputational risks must reach a named human before any public statement is made.

Humans set and sign off the brand voice, approve the content calendar, and define which reply categories may be sent autonomously; everything else is escalated.

The system never expands its own autonomous scope. Widening what it may send requires an approved policy change, recorded against the person who approved it.

What buyers ask before they hand over a channel.

Want to walk through the controls in detail?

Reach us at hello@narrapulse.com and a person will answer — the same principle this whole page describes.