What can Outflow access?
Before a customer connection, we agree the accounts and permissions and document the information needed, allowed actions, storage, recipients, retention and removal path. If the least-privilege route is not feasible, we explain the gap before asking you to approve access.
What stays with my team?
The written scope sets which routine actions may run and which require review. Pricing, service eligibility, contracts, sensitive requests and unusual decisions stay with your team. Any live trial begins with a named human reviewer and explicit review allowance. The current sample has no connected accounts or external actions.
Where does our information go?
Before a deployment, we document where information is stored, which services receive it, how long it is kept and how access can be removed. The setup depends on the selected systems and requirements; this has not yet been verified for a customer account.
Does the service use AI?
Where AI is proposed, we explain its role, model provider and the data it receives before enabling it. We agree approval rules and an exception owner for work that needs judgment. The featured sample uses no external model service.
Can we stop it or take over?
A customer deployment must pass pause, in-flight action reconciliation and access-revocation checks before launch. The current local prototype can pause sample work but has no connected account to revoke. Handover, retention and deletion steps are agreed in the proposal and verified for the systems in scope.
What does the current demo use?
The featured demo uses a fictional new inquiry and an isolated sample queue. No business inbox, web form, calendar, CRM or customer record is connected. It does not send a message, schedule an appointment, quote a price or decide service eligibility; each state is manually demonstrated. No customer data or external model service is used. Time saved, revenue and customer outcomes are unmeasured. Live connections, access, retention, deletion, controls and acceptance criteria must be specified and verified for each customer deployment.