Request intake
We take requests by phone, email, WhatsApp, chat or web form, during the hours we agree on, and open a ticket with what’s needed to act.
A team, our own platform and API connections
A team of people takes the maintenance requests for your spaces, logs them and follows them through to closure, with our own platform and API connections to other platforms. They answer under your name, on the channels and during the hours we agree on, and whoever reported it knows how it’s going without having to ask.
“Water is coming out from under the meter room door in the lobby.”
Summary: water under the meter room door, building B. Suggests plumbing and high priority.
Calls the resident: water has reached the landing. Confirms the high priority.
A person decidesTicket opened with photos and location, sent to the plumbing contractor you work with.
“Thanks for letting us know. The plumber has been notified. We’ll message you as soon as we have a time.”
Written and sent by a personWhat we do
Hours, channels and commitments are agreed with you before we start.
We take requests by phone, email, WhatsApp, chat or web form, during the hours we agree on, and open a ticket with what’s needed to act.
We classify and prioritise using your criteria, send the ticket to whoever you choose and follow it until it’s closed.
We tell them how it’s going, in plain words and before they have to ask, and explain the fix when it’s closed.
Complete tickets, merged duplicates, up-to-date categories. We log recurring faults so you can decide what to check.
Own platform and API
As well as the team that handles requests, we have our own platform to support handling and follow-up. Our team can also work in your tool, and we integrate with other platforms through APIs.
Diagram · the scope of each connection depends on the platform and the service
Demo · one photo, one draft
See how AI suggests a description, a category and a priority. In the service, a person checks the suggestion before anything happens.
A SiGO demo (our technology provider), adapted for Fixfy and in Spanish. It isn’t the Fixfy platform or an API integration, and it doesn’t order any repair.
Best on your phoneScan the code with your phone camera to open the demo and take the photo there.
Clicking opens the SiGO demo in a new tab. The photo is processed by AI to prepare the draft and isn’t stored. Use an image without people, number plates or other personal data. Privacy (in Spanish)
When you take the photo, it’s sent to the SiGO demo, our technology provider, and analysed by Anthropic’s AI. The demo doesn’t create a request or send it to any maintenance system: the photo is only used to prepare the draft, and neither the photo nor the draft is stored. Don’t upload photos showing people, number plates or other personal data. More in the privacy policy (in Spanish).
Example drawing · the real app opens in a new tab
Your case
Every sector reports issues in its own way. See how we work in yours.
Residents report; we answer on behalf of your firm and follow up with the contractor.
Read moreEach shop reports its own issues; we organise them and follow each ticket through to closure.
Read moreRequests from staff, handled without your maintenance team having to pick up the phone.
Read moreRequests from users and staff, handled during the service hours we agree.
Read moreWe manage the jobs and the appointments so your technicians can focus on repairs.
Read moreWe also handle their maintenance requests: who can report, through which channels and who each ticket goes to, agreed with you.
Read moreTaking requests, logging them in your tool, passing them to the contractor, following them up and keeping whoever reported them informed. The exact scope, channels and hours are agreed with you before we start.
No. We can work in the one you already use, such as SiGO, Reparanet or another. We review access with you and, where needed, the options for an API connection. If you don’t have one, the service can be managed on the Fixfy platform.
The hours we agree on. We set them when preparing the proposal, based on the requests you get and when they come in.
A person on the team, using your criteria. AI helps to summarise, classify, spot repeat cases and draft a reply; the decision and the reply are down to a person.
We log it, alert whoever we agreed on and tell the person who reported it what’s pending. Who gets each delay alert is agreed before we start.
From what you want covered: channels, hours, tool, tasks and roughly how many requests. With that we prepare a proposal.
Video
How we handle a request, from the first call to closure.
Signs
If any of these sound familiar, let’s talk.
Let's talk
Which spaces you look after, which channels requests come in on, and where they go unanswered. From there, we suggest how to handle them.