Chat from the front counter to the back bench

Every shop has the same conversation fifty times a day. A customer at the counter asks whether their bike is done. The person at the counter does not know, so they walk to the back, or yell, or send a text to a mechanic whose hands are covered in brake fluid. The mechanic answers from memory. Half the time the answer is right.

Chat puts that conversation somewhere it can be found later. A channel for the front counter, a channel for the bench, a channel for ordering. When the counter asks about a Tarmac with a creaking bottom bracket, the question and the answer sit in a thread under that one bike. Tomorrow, when the rider calls again, whoever picks up can read what was said instead of asking the same mechanic the same question.

It is the Chat module of erp.io, the same suite that runs Service. You sign in once and it is in the rail beside everything else. There is nothing extra to install; it runs in the browser on the counter computer and the laptop on the bench.

The habit that makes Chat worth having in a shop is simple: every bike that needs a conversation gets a thread, and the first line of the thread is the ticket number and the bike. "4471, Trek Rail 9.8, rider says motor cuts out on climbs." Everything after that, the diagnostic notes, the photo of the corroded connector, the message to ordering, the reply that the part ships Thursday, lives under that line.

Today that ticket number can be the Service job number, since work orders are live in Service as numbered jobs, or whatever tag you already hang on the bike. The link between Service jobs and Chat is on the roadmap: the Service plan has mentions in work order notes notifying people through Chat, so a mechanic can @ the service manager from the job itself. Until that is built, the thread per ticket is a convention you run by hand, and it works.

The same pattern covers the other conversations a shop has every day. A channel for the van if you run mobile repair. A channel for warranty claims, with one thread per claim, so the photos and the rep's replies are in one place when the frame comes back. A channel for ordering, where the bench posts what it needs and the person placing orders marks each one done.

Chat is for people talking to people inside your shop. It is not where the record of the repair lives. The checklist a mechanic fills in, with its photos, signature and PDF, belongs in Service, where it is live today. So do the job, its visits, the time clocked against it and the invoice, which are live in Service too. Parts will join them once inventory is built.

Chat is also not how you talk to riders. Customer texts, the "your bike is ready" message and two-way messaging with the rider are on the Service roadmap and are planned to run through the CRM's telephony. Keeping the two apart matters: a mechanic's frank note about a customer's drivetrain should never end up in a text to that customer.

What Chat gives you right now is a written memory for the shop. The service manager on a Saturday can read what Thursday's mechanic found. A new hire can scroll the ordering channel and learn which distributor is fast. That is useful before any of the Service roadmap arrives, and it will be more useful after.