The machine stops.
The story starts.
A visit, a replacement part, a customer promise and ₹450 of travel. See how the team keeps the details as the work moves forward.
Actual app captures · Sunrise Foods demo scenario · Desktop views
The problem has a shared home.
Kavita’s packing machine stops during sealing. The Service Visit Karma records the customer, equipment, finding and next step: the drive belt needs replacing. Ravi is the Karta, with colleagues helping.
An action. Its details. Someone responsible.
“The replacement belt is arranged.”
Ravi records the inspection. Suresh confirms the part. Their messages and a machine photo stay beside the task, which links back to the Service Visit Karma.
The next colleague can read what happened.
₹450, with its reason.
The travel expense names the service visit and customer. This entry shows approval and the history of a category correction. Finance has the context behind the amount.
The work explains the expense.
The promise survives the call.
Priya records that Kavita needs the machine before the next production shift. Dated follow-ups keep the next conversations in view. A useful conversation does not have to become another task.
The customer history stays with the business.
Several steps. A place for each.
A separate Project example organises repair tasks into Site Visit, Parts & Repair, and Customer & Money. Each task has a place on the board. Projects group Tasks; Karmas are not added to Projects.
See the larger effort without confusing the structures.
Know what still needs doing.
Site Visit is complete. Parts & Repair and Customer & Money each show one of three tasks complete. The repair is still in progress in this capture. The team can see the next steps instead of reconstructing the story from calls.
The work moves on. The knowledge stays.
Explore Tasks & Projects
Now let’s follow one piece of your work.
A service visit, a sales follow-up or an approval: tell us where the handover gets difficult.