ASL Messaging — Source library
Public documentation snapshot: 2026-09-08
Team chat inside the software your staff already use
Direct and group messaging built into your ASL product — no extra chat app, no outside vendor.
Team chat inside the software your staff already use
Built for: An office or practice administrator whose staff currently coordinate work in personal text threads · A small team already using an ASL product who need to ask each other a quick question without leaving it · An organization owner who wants work conversations to belong to the business, not to whoever owns the phone · An admin who needs a direct line to ASL when something in the product is wrong
ASL Messaging exists because of this.
Your staff already message each other about work all day. They just do it somewhere you cannot see. A scheduling change goes out in a group text. A question about a customer gets answered in a personal messaging app on someone's own phone. A note about a payment gets typed into whatever thread happened to be open. It works, right up until it doesn't. The damage shows up later. Somebody leaves and the entire history of how a job was handled walks out with their phone number. A question comes up months afterward and nobody can produce the conversation. Details about a customer, a resident, or a client are sitting in a consumer app that your organization does not control and cannot ask for a copy of. And the people doing the work are switching between the tool you paid for and a chat app in their pocket, retyping the same information in both. The usual fixes are worse than the problem. Buying a workplace chat product means another subscription, another set of logins to hand out and take away, another company holding your staff's conversations, and another place people have to remember to check. Asking your software vendor to build chat into the product means waiting, and then finding out they built a thin version that leaks between customers or lets anyone type any name they like. Most small organizations end up doing nothing, and the group text stays.
ASL Messaging exists because of this.
Your staff's work conversations do not go to an outside chat company — they stay on systems ASL runs.
ASL Messaging exists because of this.
Once your staff list is published, names come from it, so a user cannot label themselves as somebody else to get an answer.
ASL Messaging exists because of this.
The isolation between organizations is proven by a check that deliberately re-runs the old, leaky behavior and confirms it really did leak — so a passing result means something.
ASL Messaging exists because of this.
Adding messaging to a product in daily use required no change to how a single person signs in.
ASL Messaging exists because of this.
Escalation to ASL is restricted to organization administrators, on our side, so a frustrated employee cannot route around their own manager.
ASL Messaging exists because of this.
A departing employee is deactivated rather than erased, so pickers stay clean without destroying the record of what was said.
ASL Messaging exists because of this.
Deliberately narrow: written conversation done carefully, rather than a long feature list done thinly.
How ASL Messaging works, start to finish.
ASL Messaging puts direct and group conversations inside the ASL products your organization already signed into. When it is switched on, a chat panel appears in the product — the same window where your staff already do the work. There is nothing to install, no new address to memorize, and no second password. If someone can open the product, they can message a colleague in it, and if they cannot, they cannot. Starting a conversation works the way people expect. You open the picker, search your colleagues by name, and click one. That list is your organization's actual staff list, published by the product itself, so it is always the people who really work there. A group conversation is named and its members are chosen when you create it, up to two hundred people. Messages arrive the moment they are sent, conversations with something new in them are marked so you can see what you missed while you were away, and if the connection drops the panel reconnects on its own without anyone having to refresh. The part that matters most is the part you never see. Every conversation belongs to one organization inside one product, and there is no path between organizations — not through the conversation list, not through history, and not through the live delivery of new messages. That last one was found and closed deliberately: two different products can hand out the same internal number for two different people, and the automated checks now include a case that proves the old behavior really would have crossed the line, so the fix cannot quietly stop working. Once your product publishes its staff list, display names are taken from that list rather than from whoever opened the conversation, which means nobody can label themselves as your finance manager to get an answer they should not get. People leave. When your product publishes an updated staff list, anyone no longer on it stops appearing in pickers immediately, but the conversations they were part of keep their full history. The organization keeps the record; the departed employee stops being a live contact. Nobody has to go hunting through threads to clean up, and nothing gets destroyed to make the list tidy. There is also a way out of the building. An organization administrator can open a direct line to ASL from inside the product and describe what is wrong, in writing, in a conversation that a named person at ASL claims and answers. Regular staff deliberately cannot do this — their issue goes to their own administrator first, in an ordinary internal conversation, and only the administrator escalates. That is enforced on our side, not just hidden in the interface, so it holds even for someone who knows their way around a browser.
Everything in the current release.
Each of these is built and working today. Nothing on this list is a roadmap item.
Chat where the work already is
Messaging appears as a panel inside the ASL product your team already uses. There is no separate app to download, no new address, and no second login to hand out. If someone has access to the product, they have messaging; when their access ends, so does it.
Direct messages and group conversations
One-to-one messages for a quick question, named group conversations for a shift, a job, or a department. Opening a direct message with the same person twice reopens the existing thread instead of starting a fresh empty one, so a conversation stays in one place. A group's members are chosen when it is created, up to 200 people.
A searchable colleague picker
Click new conversation, type part of a name, pick the person. The list is drawn from your organization's real staff list rather than from whoever has messaged you before, so a new hire is reachable on day one without anyone forwarding them a code or an internal number. It needs your product to publish that list first.
Messages arrive as they are sent
Nothing is on a refresh timer. A message typed on one screen shows up on the other while the sender is still looking at it. If the network hiccups, the panel quietly reconnects on its own, waiting at most 15 seconds between attempts, so a dropped signal in a basement or a parking lot does not mean a lost conversation.
Unread conversations stand out
Come back after a few hours and the conversations with something new in them are marked so you can see at a glance what you missed. Opening a conversation clears its marker for you and only you, so one person reading a thread does not hide it from everyone else on the team.
Your organization is walled off
Every conversation belongs to one organization inside one product. There is no path from one organization's conversations to another's — not in the conversation list, not in the history, and not in live delivery. Two organizations that happen to use the same internal numbering for their people still cannot reach each other.
Nobody can wear someone else's name
Once your product publishes its staff list, the name shown on a conversation is taken from that list, not from whoever opened it, and people who are not on the list cannot be added at all. That closes the obvious trick: opening a conversation while labelling yourself as the owner or the billing contact to get an answer you should not get.
Departures handled without losing history
When your product publishes an updated staff list, anyone no longer on it stops appearing in pickers straight away. The conversations they took part in keep every message. The organization keeps its record and the former employee stops being a live contact — nothing has to be deleted to achieve that.
A direct line to ASL, from inside the product
An organization administrator can open a written conversation with ASL without leaving the product, switching to email, or looking up a phone number. It is a real back-and-forth conversation, not a form that vanishes into an inbox, and the whole exchange stays readable afterward.
Escalation stays two-tier on purpose
A regular employee cannot page ASL directly. Their issue goes to their own administrator first, through an ordinary internal conversation, and the administrator escalates only if they cannot resolve it. This is enforced on our side rather than just hidden from the screen, so it holds even for someone who knows how to inspect a web page.
Support requests get a name attached
When an administrator opens a request, a specific person at ASL claims it and their name appears on the conversation, so you know who is actually handling it rather than talking to an anonymous queue. Clicking the button twice reopens the existing request instead of creating duplicates. Either side can close it when it is done.
A record you can check for tampering
Organization setup, staff-list publications, conversation creation and closure, and support requests and claims are written to a running record that is linked together so that altering or removing an earlier entry can be detected. It deliberately does not keep a second copy of every message body — it is an integrity record of what happened structurally, not a shadow archive of conversations.
It looks like the product it lives in
Colors, spacing, corner radius, and typeface are set by the product hosting it, so messaging looks like part of the tool rather than a foreign box dropped into the page. Nobody has to maintain a separate copy of the chat panel to make it match.
Turning it on does not disturb how people sign in
Adding messaging to a product does not change anyone's username, password, roles, or session. Existing accounts keep working exactly as they did the day before, and nobody has to be re-invited or re-enrolled. That is why it can be added to a product already in daily use without a scheduled cutover.
Numbers we can stand behind.
Every figure below comes from the product's own release record or test suite, not from a marketing estimate.
Numbers we can stand behind.
One shared service every ASL product connects to, so a fix or a hardening lands for every product at once instead of being reimplemented per app.
Surfaces and status.
Status as of 2026-09-02. Running in production and responding when checked independently on 2026-09-02: the service's health check returned a healthy response over an encrypted connection, and the chat panel it serves to host products downloaded successfully at 24,167 bytes — byte-for-byte identical to the current source in the repository, which confirms the newest code is what is actually running. Live since 2026-07-30, which the repository's own written record documents as verified against the real running service rather than a local mock: a real administrator signed into a real production organization, opened the chat panel, and a message was confirmed persisted and delivered by reading it back as the other party. The second party in that test was created for the test, not a second employee. Four ASL products have been onboarded (Repo Runner, Municipal Utilities, Therapy, Command Center). Version 0.1.0. The most recent change, 2026-08-07, hardened isolation on the live-delivery path and was verified against the running service at the time. All 17 automated checks pass, re-run on 2026-09-02.
Worth more together.
Products on this platform share one sign-in, one support queue, and one engineering standard. These pair naturally with ASL Messaging.
ASL Meet
Messaging is written conversation only. When a thread needs a voice or a face, Meet handles the call side of the same team.
ASL Files
Messages are text — you cannot attach a document. Files covers sending a document or photo to someone securely.
Repo Runner
Already carries messaging as its built-in team chat, and is the one product where the direct line to ASL is switched on.
ASL Municipal Utilities
Onboarded to the same messaging service, so office staff can coordinate on a bill or a service order inside the tool they already work in.
ASL Therapy
Onboarded to the same messaging service for staff-to-staff coordination inside a practice, separate from anything client-facing.
ASL Command Center
Where ASL staff pick up and answer the support conversations an organization administrator opens from inside their product.
Recent progress.
This product ships often. The most recent verified changes, newest first.
Recent progress.
2026-08-07 live message delivery was tightened so it checks the organization as well as the person. Two different products can hand out the same internal number for two different people, and production already had several organizations spread across three products, so this was a naming coincidence away from a real crossing. The fix came with a check that deliberately re-runs the old behavior on the same data and confirms it genuinely did leak, so the check cannot silently stop proving anything. It was verified against the running service afterward, and the automated suite went from 11 covered cases to 17. Before that,.
Recent progress.
2026-08-05 added the organization staff list, the searchable colleague picker, and the change that takes a person's display name from that list rather than from whoever opened the conversation — closing an impersonation route and giving people a way to start a conversation without already knowing someone's internal number. Nothing has changed since.
Recent progress.
2026-09-02 the service was confirmed running, and the chat panel it serves was confirmed identical to the current source, so the newest code is what is live.
Recent progress.
Pricing for ASL Messaging is quoted after a short conversation about your situation, because the right scope differs from one team to the next. There is no charge for that conversation.
We already use a group text and it works. Why change?
It works until someone leaves. The history of how jobs were handled lives on a personal phone you do not control, and you cannot get a copy of it. Messaging keeps the conversation with the business: when someone departs they stop appearing in pickers, but every message they took part in stays where your organization can still read it.
Is this another subscription and another login for every employee?
There is no separate login. Messaging appears inside the ASL product your staff already sign into, so anyone with access to the product has it and anyone whose access ends loses it at the same moment. There is no separate user list to keep in step, and nothing for you to install. Pricing is not published — talk to us about your situation.
What happens to our messages if we stop paying or leave?
Your conversations are your organization's record, not something held hostage. If you stop, tell us and we will get you your history — we do not have an interest in making an exit painful. Because messaging is part of the product you are already using rather than a separate contract, an exit is the same conversation as leaving that product, not a second negotiation.
Can another company using the same system see our conversations?
No. Every conversation belongs to one organization inside one product, with no route between them in the conversation list, in the history, or in live delivery. That last route was specifically hardened on 2026-08-07 after we found that two products could assign the same internal number to two different people. The check that covers it deliberately re-runs the old behavior and confirms it really would have crossed the line, so a passing result actually proves something.
Could someone pretend to be our office manager to get information?
Not once your product has published your staff list. From that point the name shown on a conversation is taken from the list rather than from whoever opened it, and people who are not on the list cannot be added at all — which closes the obvious trick of opening a thread while labelling yourself as the person with the authority. Publishing that list is the step that turns this on for your organization, and it is also what fills the colleague picker, so it is the same setup either way.
Do we have to migrate our accounts or change how people log in?
No. Adding messaging does not touch usernames, passwords, roles, or sessions. That was a deliberate design decision — it means it can be switched on for a product already in daily use without a cutover weekend, and existing accounts keep working exactly as they did the day before.
How long does it take to add to a product?
For an ASL product already onboarded — Repo Runner, Municipal Utilities, Therapy, Command Center — team chat is already there or is a switch. For a product not yet onboarded it is a short setup on our side plus publishing your staff list, with no database change and no schema for you to adopt. It has been done four times, and each time it took one working session.
Is this actually ready, or is it early?
It has been live since 2026-07-30 and four ASL products have been onboarded to it. The original go-live was verified against the real running service rather than a mock: a real administrator signed into a real production organization sent a message through the actual panel, and we confirmed it was genuinely stored and delivered by reading it back as the other party — though that second party was created for the test rather than being a second employee. It is deliberately narrow: written conversation only, no attachments and no calls, because we would rather do that part properly than ship a wide feature list thinly.
Can our staff message ASL directly whenever they want?
Only an organization administrator can. A regular employee's issue goes to their own administrator first, in an ordinary internal conversation, and the administrator escalates to us if they cannot resolve it. That limit is enforced on our side, not just hidden from the screen, so it holds even for someone who knows how to inspect a web page.
Where do our messages actually live, and who can read them?
On systems ASL runs, not with an outside chat company — your staff's work conversations are never handed to a third-party messaging vendor. They are protected in transit. They are not end-to-end encrypted, which means someone with administrative access to the underlying system could read them, the same as with most business chat products. If you need conversations nobody but the participants can read, this is not that product and we will say so.
Can I send a photo of a damaged meter or a signed form?
Not through messaging — it is text only today, and we would rather tell you that plainly than let you find out mid-shift. Use ASL Files to send a document or photo securely, and reference it in the conversation. Attachments are a known gap, not an oversight.
Can I add somebody to a group conversation later?
Not to an existing one. A group's members are set when it is created, so adding a person means starting a new conversation with the group you want. It is a real limitation rather than a hidden one, and it is on the list — for now the practical answer is to name groups for the shift or the job rather than trying to keep one thread alive as people rotate through.
What should I know before I rely on it?
We would rather you hear this from us than discover it later. As of 2026-09-02:
What should I know before I rely on it?
Text only. You cannot attach a file, a photo, or a document to a message — send those through ASL Files instead. Messages are sized for conversation, not for pasting in a long document.
What should I know before I rely on it?
No voice or video. If a conversation needs talking, you move to a call.
What should I know before I rely on it?
There are no typing indicators, so you will not see that someone is mid-reply.
What should I know before I rely on it?
The sender is not shown a 'seen' marker. Unread marking works for the person receiving — you can see what you missed — but the ready-made panel does not tell you when the other person read your message.
What should I know before I rely on it?
A group conversation's members are fixed when it is created. There is no way to add somebody to an existing group afterward; you start a new conversation with the people you want.
What should I know before I rely on it?
A message cannot be edited or unsent once it is sent.
What should I know before I rely on it?
You are notified inside the product. If nobody has the product open, there is no push alert to a phone or an email digest — messages are waiting when you next open it.
What should I know before I rely on it?
There is no search across message history yet. You scroll a conversation to find something.
What should I know before I rely on it?
Conversations stay within one organization. You cannot message someone at another company, and there is no cross-organization directory. The single deliberate exception is an administrator opening a line to ASL.
What should I know before I rely on it?
Conversations are protected in transit and kept on systems ASL runs rather than an outside chat company's. They are not end-to-end encrypted, so someone with administrative access to the underlying system could read them — the same as most business chat products.
Team chat inside the software your staff already use
Prefer email? contact@autosecurelogin.com