The real cost of changing the software that runs your shop was never the monthly bill. It is the three months afterward, when everybody in the building is a little slower, the counter person asks how do I do X again about ten times a day, and you turn into the help desk without anybody voting on it.
The old fix for that was training days, a PDF manual nobody opens after the first week, and a support ticket answered tomorrow (or next week). Tomorrow is not when issue is happening. It happens with a customer standing at the counter and somebody behind him.
So I built an extremely capable AI support assistant right into 1sixty8 Manifold. It’s called Ask Manifold. It sits behind the help icon in the top bar, on every screen. It does two things: it answers how-to questions about anything the software can do, and it can look up your shop’s own live data. Same window, same conversation. It is included, not an add-on and not a paid module.
Some of what that looks like on an ordinary Tuesday:
- A new hire ringing up a first sale types “how do I take a deposit on an estimate?” and gets the detailed steps plus a link to the article. No manager interrupted.
- A tech in the bay, looking at a work order, asks how to add a second tech to this job. It knows which work order he is on and answers for that job.
- You at six in the evening: “What did we bring in this week?” or “Which customers still owe us money?” It pulls live numbers off your own invoices, with no report to configure first.
- Mid-sale: “Do we have any 10-inch subs in stock?” It searches the catalog and comes back with stock levels instead of telling somebody to go check the inventory page.
- A week after a data import: “Why does this imported invoice show as open?” It points at the import articles instead of a support email address.
Every how-to answer cites the knowledge base article it came from, so anybody who wants the full walkthrough clicks straight through. When a feature changes the article changes, so it doesn’t drift the way a printed training binder does. It knows which screen and which record you are on, so the answer is about this invoice and not a generic FAQ. It knows which modules your shop has turned on, so a new user never gets told to click a menu that isn’t on their screen. And it suggests a follow-up question after each answer, which is usually the one they were about to ask anyway.
That is the part I think shortens a switch more than anything else I could have built. Supporting the staff becomes one sentence: ask it. Questions get answered at the moment somebody needs the answer, which in my experience is the only time any of it sticks. There is also a side effect I like more than I expected: owners and store managers can read the team’s chat logs under Settings. Whatever your people keep asking is your training list for the week, written by them, without anybody having to admit anything out loud.
What it does not do: it does not change data. It looks things up and explains, and your staff still do the work in the real screens. It only sees your shop’s data, scoped to the logged-in user’s store. And it can be wrong, which is why every answer carries a thumbs up or thumbs down, and those ratings come back to me and turn into better articles.
I wanted to change the software running my own shop more times than I can count and never did it once, and the reasons I kept talking myself out of it had more to do with the months after the switch than with the software itself. That is the stretch I was trying to shorten here. If you run a shop and want to see how it behaves on your own screens, send me a note.