Blog Inside Sneeze It · Inside the Hub · Part 5
Our team updates client records by talking to a Slack bot, and every change keeps a name
One" lives in our company Slack. It answers questions, takes notes, changes facts and files requests in plain words, and every change it makes is recorded in the Hub under the name of the person who asked.
Most of what an agency knows about a client is said out loud before it is ever written down. A strategist hears on a call that a location changed its website. A coach learns the owner prefers texts to email. Someone notices an offer ended early. In most agencies that knowledge lands in a chat thread and stays there, because opening the client record, finding the right field and typing it in is a second job nobody has time for in the moment.
We decided the record should come to where the team already talks. So the Hub, the one record every Sneeze It tool reads from, has a teammate in our company Slack. It is called One. You mention @one in a channel or send it a message, in plain words, and it does the thing in the Hub.
Seven things from one message
One does seven things, and only seven. It can show help, list what is still open, refresh the numbers, open a ticket, set a fact, answer a question, and take a note. Anything said to it about a client that is not one of the other six becomes a note on that client in the Hub.
It finds the client the way people actually refer to them: a full name, the name without the brand, a distinctive first word, initials, or an alias. Questions ("how did last month's offer do?") are answered from the Hub's numbers and live ad reads, never only from a stored snapshot. "Refresh" reads Meta, the join data and the call center now.
Source: the Hub's Slack command router and build history, September 29, 2026
Rules decide what you meant. AI only answers.
This is the decision we care most about. When a message arrives, a fixed set of plain rules decides which of the seven actions it is. No AI model is asked to interpret the request. The same words always do the same thing, which means a teammate never has to wonder whether "set the website" will be read as a question this time.
AI is used for exactly one of the seven: answering a question. Then it works with read-only tools over the Hub's data and live ad reads. It can look; it cannot change. Every change to the record comes from a rule the person triggered on purpose.
The same words always do the same thing. AI answers questions; it never decides what you meant.
- 1SlackA teammate mentions @one or sends it a message
- 2CheckThe Hub confirms it came from Slack and from a Sneeze It account
- 3RulesPlain rules pick one of seven actions
- 4HubThe note, fact or ticket lands on the client's record
- 5HistoryThe change is recorded under the person's own name
One is internal only. It works for Sneeze It staff, recognized by their company account, and it refuses to work in any channel shared with another company. A client can never read an answer meant for our team.
Every change still has a name and a time
Changing a fact looks like this, using a sample client:
@one set Sample Fitness Riverside website to samplefitness.com
One: Done. Website changed from (blank) to samplefitness.com. Recorded in the Hub.
Before it saves, One checks that the value looks real for the field. A ZIP code has to look like a ZIP code. Then the change is made as the person who typed it, not as "the bot," and it goes into the same history every Hub page keeps: the old value, the new value, who, and when. Someone opening that client's page next week sees exactly what changed and who changed it, whether the change came from Slack or a click on the page.
Knowledge in a chat thread
The website changed, and it was mentioned in a channel. Nobody updated the record. The next person looks it up, finds the old one, and asks again.
Knowledge on the record
"@one set ... website to ..." The fact changes in the Hub, under the name of the person who said it, with the old value kept. Every tool that reads the Hub sees the new one.
A request, one question at a time
"ticket" plus a client opens a request without leaving the conversation. One walks through the same questions the Hub's request form asks, one at a time, with skip, back, cancel and send. When it is sent, it is filed to the Hub and to the team's Jira desk, the same way a ticket opened on the location page would be. The forms themselves, and the 99 old requests that shaped them, are in We read 99 old requests and rebuilt every form.
One also works the other way around. Other Sneeze It tools can post a question to the right teammate through One, and any reply in that thread closes the question and becomes a note on the client. When a client's success coach changes, One announces it in the coaches' channel and messages each person it affects.
Listening, carefully, in one channel
The newest piece is the most limited on purpose. In one internal channel only, One listens. When a teammate says something about exactly one client, a small AI model restates it plainly and sends it to our shared Brain as a candidate lesson, so the knowledge reaches the other tools instead of scrolling away. It never replies in the channel, it skips anything about money, and it has a daily cap. It is switched on for that one channel and nowhere else for now.
All of this rests on the same principle as the rest of the Hub: one record, read by every tool, with every change traceable. That is the subject of One record, every tool.
