What we will not do.
Roadmaps say what's coming. This is the other list: the things GenticFlow will not do while handling support tickets, even if they would close a deal.
Run commands you haven't approved.
Every action passes through your approval policy or the allow-list. No exceptions. No backdoors. Not even by us.
Train AI models on your data.
Customer data is not training data. If you need stricter isolation, bring your own model.
Send a customer ticket to an LLM with PII intact.
Emails, phone numbers, card numbers, API keys, bearer tokens: stripped before the prompt leaves your tenant. Tokens are restored only when the response comes back.
Auto-execute destructive actions.
Volume deletes, drive formats, registry hive deletion, fork bombs, evidence destruction: blocked outright. Cannot be approved by anyone, including admins.
Bury the case history.
Audit records are append-only. The application offers no path to modify or delete them.
Remote into a device without giving the user a way to say no.
A policy option puts Allow Remote Control and Allow File Access toggles on the device itself, enforced by both the server and the agent. Built for sensitive endpoints like finance workstations.
Feed a technician's private notes to the AI.
Endpoint notes are a technician scratchpad. They are never used as AI context and never shown to end users.
Lock you in with multi-year contracts.
Plans are month-to-month. We don't use legal terms as a sales tool. Annual is available if you prefer budget predictability.
That is the bet.
The product worth building is the one that says no to the things that erode trust, so see it on a real ticket.