The conversation and the record, in the same place
A company does not need another chat app. It needs the conversation about a customer to sit on the customer, where the next person to open the account will actually find it.
Working together without a second tool
The work is in the field and the decisions are in the office. Both should leave a trail on the account.
-
Channels and direct messages
Public channels, private channels, one to one messages and group conversations, with reactions, edits and search.
-
A note on the account
Anything worth remembering goes on the customer, not in a private message, so the next person sees it.
-
Mentions that notify
Mention a colleague on a note or a message and they are told. Mention an account and it becomes a link.
-
Unread that is honest
Unread counts per channel and per conversation, so nothing is missed without a notification firing for every message.
-
Search across everything
Find a message, a note, a job or a document by what was said in it, not only by where it lives.
-
Shifts and availability
Who is on today, who is off, and who has the right skills, so the schedule is built from reality.
Roles, departments and what each person can reach
Permissions are explicit per capability rather than implied by a job title, and a role can be scoped to a part of the company.
An audit trail, not a log file
Every change records who acted, under what role, for which company, doing what, and when.
The owner sees every entry across the installation. A company user sees their own company's entries. Nothing about that is optional, and nothing bypasses it, including actions taken by an agent or by a scheduled job.
That is what makes a bad afternoon recoverable. When a schedule was changed and the customer is annoyed, the answer is not a guess. It is a filtered list with a name on it.
It is also what makes automation safe to adopt. An owner can see exactly what an agent has been doing, in the same view as what their staff have been doing, and can turn it off with evidence rather than on a hunch.
-
Attributed actions
Person, agent or import, recorded on the action itself rather than inferred.
-
Overrides flagged
A capacity override, a forced booking or a manual adjustment is recorded with the person who made it.
-
Filterable
Filter by person, role, company, action or date range, and read it as a list rather than scrolling a raw file.
-
Readable by an agent
The audit log is an endpoint, so an agent can summarise it, spot a pattern, or alert on an unusual change.
Why the chat polls instead of streaming
Team chat in AlphaFlux updates by asking the server for anything new rather than by holding a constant connection open. That is a deliberate choice, and it is worth explaining because it affects what the product feels like.
A persistent connection per user is a thing to run, secure and monitor, and on a platform where the AI and the database are already competing for a finite machine, that cost buys less than it appears to. Polling with a proper cursor is simple, survives a dropped connection without a state machine, and works behind the corporate networks and field connections that a real service business operates on.
The honest trade is that typing indicators and presence, the little signals that make a chat product feel alive, are not part of it. That is the correct trade for a system whose job is to hold the record straight rather than to be the place people hang out.
If a decision about a customer lives in a private message, it did not get made.
Team and collaboration by plan
| Free | Starter | Growth | Scale and above | |
|---|---|---|---|---|
| Users | 1 | 3 | 10 | 25 and above |
| Account timeline and notes | Yes | Yes | Yes | Yes |
| Mentions and notifications | Yes | Yes | Yes | Yes |
| Team chat | Not included | Yes | Yes | Yes |
| Departments | Not included | Not included | Yes | Yes |
| Custom roles | Not included | Not included | Yes | Yes |
| Audit log access | Basic | Yes | Yes | Yes |
| Single sign on | Not included | Not included | Not included | Enterprise |
Questions people ask before signing up
Do I still need a separate chat app?
For conversations about customers, probably not. AlphaFlux chat keeps the discussion on the account where it belongs. Companies that also want a general purpose chat tool for lunch plans are welcome to keep one, but the customer conversation is better on the customer.
Can I stop one office seeing another office's customers?
Yes. A role scoped to a department restricts access at the query level, so a dispatcher in one district cannot see, search or change another district's records. It is enforced on the server rather than hidden in the interface.
Can a technician see pricing?
That is a permission, not a fixed rule. A company can give technicians the job detail without the money, or the money without the customer's payment history, according to how it wants to run.
What happens to a chat message if someone leaves?
It stays on the record. Messages are attributed to the person, and deactivating an account removes access without deleting the history, because a conversation about a customer is part of that customer's file.
Does the audit log slow the platform down?
No. Entries are written alongside the change they describe rather than in a separate pass, and the log is designed to be read in filtered slices rather than scanned in full.
Start on the free plan
Twenty customers, one location, every core module, free permanently. Move up when the work outgrows it.