Category: Uncategorized
-
Building Reliable AI Systems: Why Software Still Needs to Stay in Control
One thing we’ve learned from building AI into real products: the smarter the model gets, the more important the software around it becomes. We ran into this while building ServiceBrief AI at WonderIT. Imagine a technician leaves a voice note: “AC is running again, but the compressor is pulling high amps. Customer may need a…
-
Guardrails aren’t just for frontier labs
Anthropic’s CEO just told the world to slow down. This weekend, Dario Amodei published an essay calling for AI companies to deliberately pace how fast they push model capabilities forward — arguing that safety, oversight, and alignment work need to catch up before the industry pushes further. OpenAI’s Sam Altman and even Elon Musk publicly…
-
Shipping a real multi-tenant SaaS
A convincing AI demo can live in one database row and a .env file. A product cannot. ServiceBrief AI is multi-tenant from the data model up: organizations, users, plans, knowledge, inboxes, and jobs. This post is the unglamorous work that makes the AI features safe to sell. Isolation is a query habit, not a middleware…
-
Capturing jobs when the signal drops
The worst place to require a perfect connection is the place the work happens: a basement mechanical room, a steel building, a rural driveway. If capture only works on office Wi-Fi, you did not build a field product. ServiceBrief AI is a web app with PWA support, not a pair of native stores. This post…
-
A website lead form field teams can actually embed
Most “contact us” forms on service websites email the office and die. The interesting version is a form that looks like the company, asks for the right fields, and lands in the same operations product as calls and voice notes. ServiceBrief AI ships a public embed for that. This post is what we had to…
-
An operations inbox for field-service email
The shop email is where quote requests, “are you coming today,” technician photos, vendor PDFs, and spam coexist. Forwarding that inbox to a human is a job. Forwarding it to an AI that opens a work order per newsletter is a different problem. ServiceBrief AI’s inbox is review-first. Mail is captured and classified. A manager…
-
After-hours phone intake without auto-creating jobs
The call that matters arrives when nobody can pick up. The failure mode is not “no recording.” It is a Monday board full of junk jobs a bot opened from hang-ups, spam, and “is this the pizza place.” For ServiceBrief AI we wanted missed-call coverage that still respects the office. Capture the call. Do not…
-
Quote drafts that stay honest
A quote is a promise. If software writes one, the numbers have to come from the company’s book or from a person who typed them. “The model thought $420 sounded right” is not a commercial process. ServiceBrief AI treats quote generation as matching and drafting, not as creative writing. This post is the rule and…
-
Company knowledge that cannot leak to the customer
Retrieval-augmented generation is often sold as “chat with your PDFs.” Field service cannot use that slogan. Some of the PDF is a customer-safe explanation. Some of it is an internal lockout procedure, a wholesale cost, or a troubleshooting tree you would never print on a fridge. In ServiceBrief AI, company documents are first-class, but they…
-
From voice note to structured service report
A technician voice note is a terrible document and a perfect input. It has the diagnosis, the parts, the “we should come back Tuesday,” and the thing the customer was actually worried about. It also has coughs, radio, half sentences, and no headings. When we built ServiceBrief AI, the pipeline from that note to a…