Why we built FixLoop

A leaking sink should not take a chain of calls just to arrange a visit. Residents want to know who is coming and when. Property managers are chasing providers, comparing quotes and arranging access across many repairs.

We built FixLoop to reduce that back-and-forth, keep residents informed and leave owners in control of spending.

From a leak to a repair plan

Our demo starts with “my kitchen sink is leaking” on WhatsApp. FixLoop identifies an urgent plumbing job, offers a safety step and requests quotes. The manager records the replies; the resident compares them, chooses a provider and gives a visit window in their own words.

After the work is marked complete, the resident taps “It's fixed” or “Not fixed.” Closing a work order should depend on the person living with the problem, too.

How we built it

AWS End User Messaging carries WhatsApp conversations and SMS provider requests. Amazon SES sends approvals and summaries. WhatsApp lists and buttons make quotes and bookings easy to act on; a private upload link collects repair photos.

Amazon Nova on Bedrock AgentCore handles triage, questions and visit windows. Amazon Location finds nearby providers. Workflow code checks spending limits and approvals; managers can take over. Lambda, SQS, DynamoDB and S3 hold the workflow, audit trail and photos.

What we learned

“Which one is cheap and fast?” needs an answer, not an automatic booking. A greeting is not a visit time. These distinctions matter when arranging work inside someone's home.

Demo scope and next steps

The video uses demo repair data. Quotes and completion are recorded by the operator, rather than a real contractor visit. Provider-marketplace and property-management integrations are next.

WhatsApp free-form updates stay within the resident's 24-hour messaging window, with SMS fallback outside it. Proactive WhatsApp templates are next.

Built With

Share this project:

Updates

Submission history