Use cases
Automate customer support
A struggling support process has one telltale symptom: nobody can say where a case stands without asking around. InProcess gives you a claim-handling flow where every step has an owner, a deadline and a trace — without deploying a heavyweight ticketing suite.
What goes wrong today
- Claims arrive through several channels and no single view brings them together.
- Qualification depends on who picks up the case, so handling varies.
- Technician visits are arranged by phone, leaving no usable record.
- Nobody knows whether the customer considers the problem solved.
The process you get
- 1
The customer reports the problem
A public form collects the description, photos and references. The case enters the flow directly, with no re-entry.
- 2
Support qualifies it
Support categorises the case, sets an urgency level and decides what follows: direct resolution or a field visit.
- 3
A technician intervenes
They get the task on mobile or by SMS, with the case context, and submit their report and photos from the field.
- 4
The customer confirms resolution
The customer confirms the problem is fixed. Without that confirmation, the case does not close.
What changes
- Every claim has an identified status and owner at all times.
- Qualification follows the same rules whoever handles the case.
- Field reports are structured and attached to the right case.
- Closure is declared by the customer, not assumed internally.
Other common processes
- Automate quote approval
- Automate leave requests
- Automate worksite tracking
- Automate employee onboarding
- Automate purchase requests
You could have this process live today
Describe it in a few sentences, AI builds it, you approve before it goes live.