Give an agent a key, not your password
Most software added a chat box that can talk about your data. AlphaFlux was built the other way round: every capability is an interface first, so an agent can do the work and not just describe it.
The receptionist answers before a person has to
A call comes in at 9pm on a Friday. Nobody is in the office. The phone is still answered, the caller is still helped, and the job is on the board before Monday.
The receptionist answers first, with a fifteen second timer. If it handles the call, a human is never rung and the caller never knows the office was closed. If it cannot, the call rolls to the person on duty, or to voicemail with an automatic text back, according to the rule you set for that number and that hour.
What it can do is bounded on purpose. It can identify the caller, work out which office serves their address, check whether the service they are describing is one you offer, book an appointment against real capacity, take the details and leave a complete record. It cannot invent a price, promise an exact arrival time, or book a job that would oversell a technician's day.
Its script is versioned inside the platform rather than hidden in a vendor's dashboard, so changing how your phone is answered is an edit you make, not a support ticket you file.
-
Hour aware
Different behaviour inside and outside business hours, with a rule per number.
-
Territory aware
It resolves the address to the correct office and respects the areas you do and do not serve.
-
Capacity aware
A booking is checked against real capacity before it is confirmed, so an agent cannot oversell a day.
-
Escalation that works
Emergencies are routed to a person immediately, and a solicitor gets a scripted answer rather than a technician's time.
What an agent can do on day one
Concrete work, not demonstrations. Each of these runs against the same records your staff use.
How the access actually works
An agent is a credential with a job, not a person with a password. Everything about the design follows from that.
-
A scoped key
Read and write access is granted per module. An agent that books jobs does not need, and does not get, the billing module.
-
Inherits its owner, and nothing more
A key carries exactly the permissions and the companies of the account that created it. It cannot reach past its owner.
-
Revocable without a reset
Disable a key and the agent stops working. No password changes, no disruption for the humans on the system.
-
Everything is an endpoint
The agent connects over the same documented interface your other software would, so nothing it does is special or unreviewable.
-
Attributed, always
Records carry whether a person, an agent or an import made a change. Sales, notes, tickets and jobs all record it.
-
Autopilot, if you want it
A per company switch lets agents keep configuration tidy and heal small problems on their own, under the same attributions and the same audit trail.
Why attribution is the part that matters
Once an agent handles a meaningful share of the work, the first question an owner asks is not whether it is fast. It is which of these did a machine do, and can I see the difference.
AlphaFlux records the actor on every action, and it distinguishes an agent from a person from an import. Revenue an agent booked is separable from revenue a person booked. A note written by the receptionist reads as agent authored. A ticket the assistant raised says so on its face.
That is also what makes the numbers trustworthy later. When commission is calculated, when a customer complains, when a regulator asks who touched a record, the answer is already in the data rather than reconstructed from memory.
The difference between an agent you trust with real work and one you do not is whether the platform can say no in a structured way.
Guardrails, stated plainly
-
No raw database access
An agent works through the same validated operations your software uses. There is no path from a model to an arbitrary query.
-
No credentials in a prompt
Agents receive what they need to answer and act. Payment tokens, carrier credentials and full customer records are not put in front of a model.
-
Confirmation where it matters
Proposals are separated from actions. A merge, a price change or a bulk send asks a person to confirm before anything is written.
-
A trail you can read
Every action lands in the audit log with actor, role, company, action and time, readable by the owner and filterable by an agent.
Questions people ask before signing up
Do I have to use AI at all?
No. Every module works fully with people driving it. Agents are an additional way to operate the same records, and they can be switched off entirely without changing how anything else behaves.
What stops an agent from doing something expensive?
Three things. The key only carries the permissions it was issued. The platform refuses operations that break a rule regardless of who asked, such as a booking that would exceed a day's capacity. And the operations that carry real consequence, like merging accounts or issuing a bulk send, are presented as a proposal that a person confirms.
Which AI providers can it use?
AlphaFlux is provider agnostic. It can run against a hosted model of your choosing or against a model running on your own hardware, which is the arrangement that keeps customer data inside your building.
How do I connect an agent?
Issue a scoped key in the console, then hand the key to the agent. For agent clients that support tool protocols, the platform presents itself as a set of callable tools, so the agent discovers the available operations rather than being told about them. Developers can read the developer page for the exact interfaces.
Can an agent email my customers?
Yes, through the email marketing module, under the same suppression list and consent rules a person is held to. A customer who has unsubscribed is excluded from an agent's send exactly as they are from a person's.
Start on the free plan
Twenty customers, one location, every core module, free permanently. Move up when the work outgrows it.