A team, our own platform and API connections

People who handle your maintenance tickets.

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.

Download the presentation (PDF)

Sample ticket · building BReceived
  1. WhatsApp 08:12 · resident, flat 3B

    “Water is coming out from under the meter room door in the lobby.”

  2. AI suggestion

    Summary: water under the meter room door, building B. Suggests plumbing and high priority.

  3. Fixfy agent 08:15

    Calls the resident: water has reached the landing. Confirms the high priority.

    A person decides
  4. In your CMMS 08:19

    Ticket opened with photos and location, sent to the plumbing contractor you work with.

  5. Reply to the resident 08:21

    “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 person
Illustrative example · not a real case
Always a personSomeone on the team reads every request, decides what to do and replies.
Several channelsPhone, email, WhatsApp, chat or web form, under your name.
Own platformWith AI to classify and API connections.
Also in your toolSiGO, Reparanet or whichever maintenance tool you already use.

What we do

From request to closure, with someone behind it.

Hours, channels and commitments are agreed with you before we start.

  1. Request comes inOn the agreed channel
  2. Complete ticketWith what’s needed
  3. Sent to the contractorWith all the context
  4. Closure explainedTo whoever reported it
01

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.

02

Ticket management and follow-up

We classify and prioritise using your criteria, send the ticket to whoever you choose and follow it until it’s closed.

03

Updates to the person who reported it

We tell them how it’s going, in plain words and before they have to ask, and explain the fix when it’s closed.

04

A tidy system

Complete tickets, merged duplicates, up-to-date categories. We log recurring faults so you can decide what to check.

Own platform and API

A team and a platform to handle your requests.

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.

  • From a photo or a message to a logged request, with what’s needed to act.
  • AI classification: it suggests category and priority, and a person checks it.
  • Every case followed to closure, with what was said in the history.
  • API connections with other platforms. Before we start, we review what information the service needs to exchange and what each system allows.

Diagram · the scope of each connection depends on the platform and the service

Demo · one photo, one draft

From a photo to a draft request.

See how AI suggests a description, a category and a priority. In the service, a person checks the suggestion before anything happens.

  1. 01
    You take a photoOf a fault, in any kind of space.
  2. 02
    AI suggestsWhat it shows, category and priority, with the reason.
  3. 03
    A person checksIn the service, they confirm, complete and pass it on.

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.

Who does what on every request

Demo · SiGO app for FixfyOpen the demo
Try it with a photo
QR code that opens the demo on your phone

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)

How your photo is handled

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

What kind of spaces do you look after?

Every sector reports issues in its own way. See how we work in yours.

Common questions

What people usually ask us.

What exactly does the service cover?

Taking 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.

Do I have to change my tool?

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.

What hours do you cover?

The hours we agree on. We set them when preparing the proposal, based on the requests you get and when they come in.

Who decides how urgent a request is?

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.

What happens if a request gets stuck?

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.

How is the price worked out?

From what you want covered: channels, hours, tool, tasks and roughly how many requests. With that we prepare a proposal.

Video

How Fixfy works.

How we handle a request, from the first call to closure.

Fixfy · video1 min 28 s · with subtitles

Open the video in a new tab

Signs

When it makes sense to work with us.

If any of these sound familiar, let’s talk.

Sound familiar?
  • Requests reach someone’s mobile, and when that person is on holiday, they get lost.
  • Your technicians spend part of the morning on the phone instead of repairing.
  • Nobody knows the status of some open tickets.
  • People call back to ask how their issue is going.
  • Ticket records are incomplete: no photos, no full address, or duplicates.
  • You don’t know which faults keep coming back, because nobody has had time to count them.

Let's talk

Tell us how requests reach you today.

Which spaces you look after, which channels requests come in on, and where they go unanswered. From there, we suggest how to handle them.

What happens next
  1. 01
    A conversationYou tell us what you need covered.
  2. 02
    A written proposalTasks, hours, channels and platform.
  3. 03
    Go-liveOn the date we agree.