Questions,
answered plainly.
Twelve answers, grouped the way the questions actually arrive. If yours is not here, ask it on the call.
The product
What is InSynk?
A print workflow tracker built by WEBBED. Each job keeps one shared record from creation to delivery. Photos, voice notes, assignments, hiccups, and reports all sit on that one record.
Who is InSynk built for?
Four access levels. Access A, called Owner in the app, creates jobs, tracks them, sees Reports, exports the monthly PDF, and holds full outsourcing control. Access B, called Manager, does the same with view-only outsourcing. Access C, called Supervisor, assigns, approves, and resolves blockers. Access D, called Operator, accepts tasks, completes them, and can raise a Hiccup.
How does job tracking work?
Each job gets a JobID in the format [INITIALS]-[SERIAL]-[TYPE]. S means Sample, O means Order, R means ReOrder. Access D taps Accept, then Complete, and raises a Hiccup if something blocks the job. Stage history records who moved what, and when. The QR link at /job/:id opens for Access A, B, and C only.
What happens when a job is finished?
The job sits at 100% and its history stays on the record. Access A exports a monthly PDF by hand and shares it, and that export is logged for your records. Nothing is filed away on its own.
Your setup
Which devices are supported?
Android, iOS, macOS, Windows, and Web. Linux is not supported. You can read last known data while offline, but creating a job, uploading photos, and syncing all need internet.
Which languages are supported?
English, Tamil, and Hindi. The choice is saved per person and access level, so a Tamil speaker on Access C and an English speaker on Access A can each keep their own. More languages can be added on request.
What does Access D see?
A person on Access D sees a task list. They tap Accept, then Complete, and can raise a Hiccup. There is no Start button and no timer. If prior work on the job is unfinished, the task shows a locked notice until it clears.
The demo
How long is the demo?
Thirty minutes. We walk through your own use case rather than a fixed script, and you will see the screens your role would actually use.
Will you ask me to commit to anything?
No. There is no pressure on the call. If you want a quote afterwards, we reply within one business day.
Can I bring a teammate?
Yes, and it usually helps. Bring a teammate on another access level if they will use it too. Seeing their screen answers more questions than ours would.
What if I am just exploring?
That is fine. A lot of people watch a walkthrough first and decide months later. We will show the flow, answer your questions, and leave it there.
Do you support our setup?
In most cases, yes. We check your access levels, whether anyone needs Tamil, and whether your team is on Android, iOS, or Web in the first ten minutes. If something will not fit, we tell you on the call rather than after.