Changes it can make to your account
Read-only by design: it runs no actions and reads none of your data. The only write it can do is open a ticket, and only if you confirm.
Pluxi can only read Pluxion's documentation and talk to you. It makes no changes, reads none of your data, and the one thing it writes — a support ticket — needs your explicit yes.
The assistant doesn't improvise: it answers from a knowledge base written and reviewed by the team that builds the product.
When it's not a question but a failure, Pluxi prepares the ticket for you and waits for your confirmation.
No small print: these are the rules it answers by, identical on Starter, Pro and Business.
The assistant is on every page of the panel, so it has to hold up. These are the nets underneath it.
Read-only by design: it runs no actions and reads none of your data. The only write it can do is open a ticket, and only if you confirm.
It loads the help for the module you're working in, so you don't have to explain the context before asking.
In the main modules it suggests typical questions for that screen, and a general set everywhere else. One click sends them for you.
When the product changes, the team edits the knowledge base and the assistant picks it up with no deploy in between.
A separate assistant designs the integration with you: which services to use, which events fire webhooks and with what minimum permissions.
The token is created when an admin or owner confirms the proposal, it's shown once, and the integration prompt is assembled without any AI involved.
There's nothing to set up: the button is there from day one, on every page of the panel.
A fixed corner button, without leaving the screen you were working on or losing what you had in progress.
It loads the global docs plus those of the module you're in and gives you the exact step, with links when needed.
It asks one short question — since when, who it affects, whether it blocks you — and drafts a ticket with the right priority.
Only if you say yes. It reaches support classified and with the context written, and you get the reference right away.
The assistant has no tiers and no extras: it's complete on Starter, Pro and Business, and it burns none of your plan's quota.
| Feature | Starter | Pro | Business |
|---|---|---|---|
| The assistant | |||
| Available on every page of the panel | ✓ | ✓ | ✓ |
| Answers from Pluxion's knowledge base | ✓ | ✓ | ✓ |
| Automatic context for the module you're in | ✓ | ✓ | ✓ |
| Interface in Spanish and English | ✓ | ✓ | ✓ |
| Messages per minuteTechnical per-user limit, not a monthly quota | 15 | 15 | 15 |
| Consumption of your AI quotaAsking Pluxi deducts nothing from your plan | 0 | 0 | 0 |
| Escalation to support | |||
| Ticket opened from the chat with your confirmation | ✓ | ✓ | ✓ |
| Priority estimated by the AI | ✓ | ✓ | ✓ |
| Category based on the module you were in | ✓ | ✓ | ✓ |
| Conversation transcript inside the ticket | ✓ | ✓ | ✓ |
| Ticket reference and access to Support | ✓ | ✓ | ✓ |
| Integration wizard | |||
| Chat that designs your CRM integration | ✓ | ✓ | ✓ |
| Proposal with least privilege by role | ✓ | ✓ | ✓ |
| Your organization's real context in the proposal | ✓ | ✓ | ✓ |
| Access token creationAnyone can design it; only an admin or owner confirms it | ✓ | ✓ | ✓ |
| Prompt ready to paste into your AI | ✓ | ✓ | ✓ |
| The assistant's scope | |||
| Runs changes on your account | — | — | — |
| Reads your organization's data | — | — | — |
| The model sees your tokens or secrets | — | — | — |
| Knowledge base reviewed by Pluxion | ✓ | ✓ | ✓ |
| Available to owner, admin and memberMail-only accounts don't have it yet | ✓ | ✓ | ✓ |
Under 'The assistant's scope', a dash is not a gap: those are deliberate limits. Pluxi guides, you decide.
What we're building. Not available yet — we list it so you know where it's heading.
Every service talks to the others and lives in the same plan.
Pluxion's five core services, today paid separately — in a single plan.
7-day trial · No charge today · Free migration