Received
Phone, text, email or web form, in French or English, at any hour. The line answers, asks which language, and takes the description. Every channel produces the same request record.
Maintenance triage and dispatch · Canada
Maintenance requests sorted by urgency, routed to your own staff first, and followed up until the work is confirmed. In French and in English, by your rules, alongside the property management software you already use.
OPIS answers in French or English, takes the caller’s description, and runs it through the same triage as a text. It does not hold a conversation. A tenant who needs to talk something through still reaches your team.
Phone, text, email or web form, in French or English, at any hour. The line answers, asks which language, and takes the description. Every channel produces the same request record.
Each request is classified by trade and scored for urgency on a 0 to 100 scale mapped to four priority tiers. A burst pipe and a dripping tap both read as urgent at midnight. Separating them is the work.
Your rules decide: trade, priority, building, hours. Internal staff before vendors. If a vendor declines, the next one is contacted automatically. Closed means done, not filed.
One call, about an hour, in French or in English. You leave with a written routing and escalation plan for your portfolio, yours to keep whether or not you ever work with us.
How it works
OPIS runs on your rules: your trades, your buildings, your vendors, your hours, your on call rotation. Setting it up means describing how you already work. It does not mean changing how you work, and it does not mean an integration project.
Trades, buildings, vendors, business hours, who is on call, and which request types your own staff should always take before an outside vendor is contacted.
A number and an address your tenants call, text or email, in French or English. They keep doing exactly what they already do.
Each request carries a timestamped trail of what happened and who was told. Useful for owners, and for the conversations you would rather not have from memory.
The system
We have no customer logos to show you, because we do not have customers yet. What we can show you is how it is built, which is the part that decides whether it holds at two in the morning.
Multi tenant PostgreSQL where each account is separated at the database layer, not by a filter in the application.
Every outbound call is HMAC signed per tenant with the timestamp inside the signature, so a replayed request does not act twice.
Request events are added, never overwritten. What happened, who was told, and when, in an order nobody can quietly edit.
Outbound calls carry idempotency keys, so a retry after a timeout does not dispatch the same plumber twice.
Included with every account
A dashboard for your team. The record is not something you have to ask us for. You open it.
In Quebec and bilingual Ontario
Quebec’s French language property management software lets a tenant submit a maintenance request in French. Then a person reads it and picks the contractor. OPIS makes that decision a rule rather than a person, in both languages.
Emergency wording is maintained as its own French list alongside the English one. A tenant who writes dégât d’eau, refoulement or pas de chauffage is scored on the same basis as one who writes flooding, backup or no heat. And they are answered in the language they wrote in.
Neither Quebec nor Ontario sets a numeric response deadline. Both assess afterwards, on what you can show. That makes the question not how fast you moved but whether you can demonstrate you handled the urgent thing first. OPIS produces exactly that: the urgency tier, the rule that fired, who was told, and when.
OPIS supports how you evidence your own practice. It does not make you compliant with anything, and you should be careful with any vendor who says otherwise.
Plainly
The sorting and the urgency scoring are done by software, working on how tenants in Quebec and Ontario actually write, in both languages. Anything it is not confident about, a person reads before it moves. Anything it marks urgent goes straight to your on call person, by name, and never to a vendor unless one of your rules sends it there.
What stays with your team: obtaining and comparing bids, judging whether a quote is reasonable, negotiating with vendors, verifying completed work, and anything involving rent, leasing or the tribunal.
Questions
Yes. There is a bilingual line. It answers, asks the caller to choose French or English, takes their description of the problem, and runs it through the same triage and routing as a text message. What it does not do is hold a conversation. It will not answer questions, negotiate, or talk a tenant through a fix. A tenant who needs that still reaches your team.
No. OPIS covers the intake and routing part of the work: reading the request, identifying the trade, setting urgency, sending it to the right person under your rules, and following up to confirmation. Obtaining and comparing bids, judging whether a quote is reasonable, negotiating with vendors, verifying completed work, rent collection, leasing and tribunal matters all stay with your team. Managers use OPIS so an existing administrator can carry more doors, not so the position goes away.
An answering service takes the message and passes it on. OPIS decides what happens next. It identifies the trade, sets an urgency level, applies your routing rules to send the request to your own staff before any vendor, and stays on it until someone confirms the work is done.
In both directions. Requests written in French are read and scored in French, with no translation step. Emergency wording is maintained as separate French and English sets, so dégât d’eau and refoulement carry the same weight as flooding and backup. Tenants receive their updates in the language they wrote in.
No, and it needs no integration project. Requests arrive by phone, text, email and web form, so OPIS runs next to Buildium, Yardi, AppFolio, Hopem, UpperBee, Rent Manager or a spreadsheet without touching any of them. Your existing system stays the record for leases, accounting and rent.
No. OPIS has no vendor network. Requests route to your internal staff first, then to the trades you already work with. We are paid a flat monthly fee and never take a percentage, a markup or any share of a repair invoice. Your vendor invoices you directly.
You get the Command Center with every account. The live queue, a full timeline on every request, your routing rules editable by you, your vendors and staff, and a log of every message OPIS sent on your behalf. The record is something you open, not something you request from us.
A flat monthly fee based on door count. Nothing per request and nothing per minute. We do not publish a rate card, because your routing rules, staff coverage and request volume decide the figure. It is quoted after the routing review.
Anyone who needs a live person and a real conversation on the phone, since the line takes a description rather than talking with the caller. Firms that want the contractors supplied, since we have no network. United States operators, since the Canadian and bilingual context is the reason to choose us. And anyone looking for a property management system, since OPIS does not do leasing, rent or accounting.
Whether you have your own maintenance staff or you lean on outside trades, the routing plan is built around how you already work.
Book the routing review
Tell us where to reach you and roughly how many doors you manage. We come back with times, in French or English, whichever you prefer.
No cost, no obligation, and the routing plan is yours either way. If you would rather just write, it is admin@realtytechflow.com.
For investors and partners
Plainly, because you would find out anyway. OPIS has no paying customers. The platform was built through 2025 and into 2026, went quiet, and is being relaunched around a narrower position. Here is what exists, what the bet is, and what could kill it.
Multi tenant PostgreSQL with row level security, per tenant signed webhooks, an idempotent integration log and an append only event trail. Intake adapters for phone, text, email and web form, including a bilingual voice line with language selection and speech capture in fr-CA and en-US. A deterministic rule based routing engine. Roughly 119 automation workflows.
French first Quebec software handles the request but not the decision. Triage products make the decision but do not treat French as a first class case. Both sides are real businesses, and the gap between them is narrow and specific.
The phone line takes a description rather than conversing, while the funded leaders run full conversational voice agents. An incumbent deciding Quebec is worth a quarter of engineering time. Bilingual alone is not a moat, and we do not claim it is.
Design partners more than capital. Bilingual portfolios willing to run real requests through it and say where it fails. An introduction is worth more than a term sheet right now.
Diligence questions are welcome, including the uncomfortable ones. We will send the architecture notes and answer directly on stage, traction and risk.
Or write to admin@realtytechflow.com.
Investor and partner enquiries