Requests and follow-up
A custom ticketing system.Every request has an owner.
With a custom ticketing system, customers and partners log their own requests in a portal. Every request gets an owner and a status, so your team can keep track of the follow-up.
Ripal
Business software
Sound familiar?
Where does a request disappear?Usually in a mailbox.
The question did come in. Nobody just knows who is picking it up.
Everything comes in by email
Questions, complaints and requests all mixed up, in the mailbox of whoever happened to reply.
Nobody owns it
Everyone has seen it, so everyone assumes someone else is picking it up.
Customers call for an update
Because they cannot see whether their request has been picked up.
No view of what keeps coming back
Nobody knows which problems turn up again every week.
Why Hubigen
Requests that belong with your work.That is why companies choose us.
What you get, and when it clicks.
What you get
- A request form with your own fields and types.
- Requests linked to a customer, project or delivery.
- A portal where whoever logged the request follows its status.
- A fixed price per phase, and after each phase you decide.
- Software that is yours, including the code and the data.
When you choose us
- You want requests to stop coming in by email.
- You want every request to have an owner.
- You want to see requests alongside your customers and projects.
- You want partners to log requests in their own portal.
- You want honest advice, even if something simpler will do.
What is inside
What is in a custom ticketing system?From request to resolved.
Customers or partners log requests themselves, with the fields you need to get started straight away.
Proof, not promises
Requests that are already being followed up.For clients and for ourselves.
Partners who log returns and trailer swaps themselves in a portal, and our own admin system in which every request becomes a task on a board.
In practice
How we did it at IBS
At IBS the mobile work order is the basis for recording and following up a technical intervention. The first version focuses on the technician flow with work registration, signature and PDF.
Get to know us
How many requests are left lying around?Start from how you work today.
Show us how questions come in today. We will tell you honestly whether a package will do or something of your own is worth it.
Questions
What clients ask us.About portals, integrations and your mailbox.
A system in which every question, complaint or request becomes its own ticket, with an owner and a status. That way your team can see who is picking up a question and what follow-up is still needed.
If you mainly handle standalone support questions, a package is often enough, and we will say so. Custom pays off when requests need to be linked to your customers, projects or deliveries, or when partners log them in their own portal.
Yes. Customers or partners log requests in their own portal, with the fields you need, and follow the status there themselves. That is how partners at Ripal report their returns and trailer swaps, instead of emailing.
Yes. An email to a fixed address can automatically become a ticket, so people who prefer email can keep using it.
That depends on who logs requests and which systems we connect to. We work per phase at a fixed price, so after each phase you decide whether we carry on.
Contact
Work together?Tell us what you want to build.
Curious what we can do for you?Leave a short message about your question or project.
