blankmile Workflows
Efficient work starts with
the right information.
When a fault is reported or a task needs doing on site, your team needs a clear process. blankmile Workflows guides customers, partners and employees through the right questions and steps. Details, media and feedback are collected in one place.
Trusted by service teams at industry leaders.
Build workflows.
No coding required.
Put the steps of your process together in the visual builder. Define questions, instructions and conditions, then check the flow in the preview. No programming knowledge required.
You can edit your workflows at any time, even after publishing.
Get your workflow to the customer.
Rückfragen minimieren
Send an invitation link
Send your customer a link to collect the missing details. The workflow guides them through the right questions and helps your team avoid further follow-ups.
Self-Service
Place a QR code on the machine
Attach the QR code directly to the machine. Your customer scans it and starts the relevant workflow independently on site.
Two types of workflow.
One clear process.
Information Workflows collect the details your team needs to make a decision. Execution Workflows guide people through a defined task, step by step.
Collect information
A machine reports a fault.
A customer reports a fault, describes the symptoms and adds photos or videos. The service team receives the details in one structured case.
- The customer opens the workflow using the provided link or QR code.
- They describe the fault and add photos or videos of the affected area.
- The workflow asks for the details needed for this case.
What your service team receivesA structured report with the fault description, equipment details and media. Your team can assess the case and decide on the next step.
Guide self-service tasks
A part needs replacing on site.
A technician carries out a planned part replacement. The workflow shows each next step and asks for the required feedback on the work.
- The service team provides the planned procedure.
- The technician opens the workflow on site and follows the defined steps.
- They submit the requested feedback on the completed replacement.
What your service team receivesFeedback on the work in one place. The responsible team can see what was done and whether further action is needed.
Example: collecting information
From voice message
to service ticket.
A customer is standing at their machine. On their smartphone, the workflow guides them through the details your service team needs.
The customer enters the number of the affected machine, giving the request its context.
What happened? The customer describes the situation in their own words in a voice recording.
A photo of the machine and a close-up show the affected area.
The machine number, voice recording and photos are submitted together. Your service team can assess the request.
The request data is extracted: machine number MX-240. Description: Customer reports a sensor malfunction that has been occurring since yesterday. Attachments: a transcript and two photos. The structured data is forwarded by email or to a ticketing system.
Workflows for everyday service.
From the first fault report to the service report, Workflows guides people through the right questions and steps for recurring tasks.
Capture fault reports consistently
Customers identify the affected equipment, describe the fault and add photos or videos. Your service team receives all the details in one report.
Guide part replacement
A technician follows the defined replacement steps and records what was done. The service team can review any deviations afterwards.
Guide maintenance on site
Employees or partners follow the planned checks and record their observations. The responsible team can review the feedback on the work.
Support commissioning
Technicians carry out the planned checks and adjustments on site and record their feedback. The team can see which steps have been completed.
Create service reports
Technicians use a guided process to record completed work, parts used and relevant photos. These details form the basis of a clear service report.
Identify spare-part needs
Customers or technicians record the machine, affected component and a photo. Your team has the information it needs to assess the spare-part request.
What is follow-up work costing you?
Follow-up questions, case handling and documentation take time. Find out where your service team could save.
Calculate potential savingsThe right information.
Right when you need it.
Captured information can be reused in existing CRM, ERP, ticketing or knowledge systems.
Integration and data transfer options are assessed for your specific systems. No particular integration partner is guaranteed.
Explore integrations
Microsoft
Dynamics
When the details call for a closer look together.
Workflows collects details and media through a guided process. If the situation then needs to be assessed live, the service team and customer can look at it together with Visual Support.
Workflows and Visual Support complement each other in a service case. Both also work independently.
Explore Visual Support
What information does
your team really need?
What information do your team and customers need? Together, we’ll explore how Workflows can help.
Get startedQuestions about blankmile Workflows.
Answers about digital service processes, fault reporting, service reports and using blankmile Workflows.
Are Workflows only for collecting information?
No. Workflows can also guide people through tasks such as part replacement and collect the related feedback. Your company defines the technical procedure.
Which media types can be used?
Workflows can combine text, images, video and voice when collecting information. Specific file formats and size limits need to be checked for your use case.
Can workflows be reused?
Yes. You can use a one-time workflow for a specific request or provide reusable workflows for recurring processes.
Can we use QR codes?
Yes. A reusable workflow can be made available through a reusable link or QR code.
Show moreShow less
Can the process change based on the answers?
Yes. Conditions allow the next step to depend on answers given earlier.
Are Workflows only for customers?
No. Workflows can also guide employees and partners through information capture, for example for internal service or installation reports.
What is blankmile Workflows?
blankmile Workflows is a solution for guided digital service and customer processes. Customers, partners or employees capture information and media or follow defined work steps. Service, after-sales and sales teams receive structured details and feedback to continue the process.
How do Workflows differ from forms and email?
In a free-form email, the sender decides which details to include. blankmile Workflows guides them through the required questions and steps, combining text, images, video, voice and conditions. The focus is on the guided process: alongside collecting information, it can include defined tasks and feedback on the work.
Does the service team need to be present while a workflow is completed?
No. blankmile Workflows supports asynchronous work. Recipients complete the process without the service team needing to join a call at the same time. The responsible team can then review the captured details and decide on the next steps.
Can I create digital service processes without coding?
Yes. With the blankmile workflow builder, you can create guided processes without development expertise. Define questions, media and conditions to suit your service process. Your company determines the technical content and the order of the work steps.
How can we capture fault reports in a structured way?
blankmile Workflows guides customers through the details your service team needs to assess a fault. A workflow might ask for the machine number, a description of the symptoms and photos or videos of the affected area. Technical details and media arrive together, helping the team prepare the next steps.
How does blankmile support digital service reports?
blankmile Workflows guides employees through the required details of a service or installation visit. The process can capture completed work, feedback and supporting media. A consistent structure makes the documentation easier to follow.
How do Workflows help with spare-part requests?
blankmile Workflows can collect the information needed for a spare-part request. This can include machine details, a description of the affected component and photos. Structured capture helps your team review the request and advise the customer. The established technical and ordering processes determine which parts fit and how to order them.
How can Workflows reduce follow-up questions?
blankmile Workflows asks for the required details before your service team starts working on the case. Machine details, a fault description and photos arrive together. Your team is less likely to need to request them separately. This helps avoid follow-up questions.
When should we use Workflows or Visual Support?
blankmile Workflows is suitable when information needs to be captured asynchronously or defined steps need to be carried out. blankmile Visual Support is suitable when the service team and customer need to look at a situation live together. Both products work independently and can complement each other: a structured fault report can be followed by a live session when needed.
Does blankmile Workflows replace a CRM, ERP or ticketing system?
No. blankmile Workflows complements existing systems with guided information capture and process steps. The captured details can form the basis for further work in your CRM, ERP or ticketing system.
How can Workflows improve the remote fix rate?
The remote fix rate is the proportion of service cases fully resolved without a service technician travelling to the site. blankmile Workflows can support remote resolution. Customers provide structured fault descriptions, photos and machine details. They can also follow defined steps to resolve the issue. Your team receives the information and feedback needed to assess the case remotely. Visual Support can add a live session when needed. Capturing a fault report alone does not count as a resolved case; the issue must be fully resolved without an on-site service visit.