Bilingual maintenance triage and dispatch · Canada
In French and in English, by your rules, alongside the property management software you already use. Built and run in Gatineau, Québec, for Canadian property management teams.
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.
One request, end to end
What OPIS does
Maintenance coordination does not fail in the middle of a Tuesday. It fails at the edges: after hours, during vacations, and the week the person who knows every building is away.
Text message, email, web form or a phone call, in French or English, at any hour. The line answers, asks which language, and takes the description. Every channel produces the same request record, so a call at midnight is handled the same way as a form typed at noon.
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 when a tenant writes them at midnight. Separating them is the work.
Rules match on trade, priority, city and building, in the order you set. Internal staff are considered before external vendors. OPIS has no contractor network, so the trades it sends work to are the ones you already use.
If a vendor declines, the next one on your list is contacted automatically, and you are told only if nobody is left. When the work is reported complete, the tenant is asked to confirm it. Closed means done, not filed.
This one identifies the trade, sets the urgency, sends it to your plumber under your rules, and stays on it until the job is confirmed.
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.
French in, French back. English in, English back. Nobody on your team has to be bilingual on a Saturday night for a French speaking tenant to get a straight answer about what happens next.
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.
Included
A dashboard for your team, included with every account. The record is not something you have to ask us for. You open it.
Every open request in one list, with its trade, its urgency tier and its status. Open, in progress, completed. What your coordinator keeps in their head, on a screen anyone on the team can look at.
Open any request and read the full history. What the tenant wrote, how it was classified, which rule routed it, which vendor was contacted, who was notified, and when each of those happened. This is the record that matters when an owner or a tribunal asks what you did.
Add a trade, change a vendor, reorder a rule, or set which requests your internal staff take first. You do not file a ticket with us to change how your own dispatch works.
Your trades and your internal maintenance staff, each with the categories they cover, whether they take emergencies, and whether they work in French.
Every outbound message OPIS sent on your behalf, with its result. If a text did not arrive, you can see that yourself rather than wonder.
Keys for your account, rotatable by you at any time. Standard practice for anything touching tenant information, and rarely offered at this size.
Access is per person on your team, and each account only ever sees its own data. That isolation is enforced at the database layer rather than by a filter in the application.
Covering nights and weekends with people means a rota of four or five. OPIS takes the intake and routing part, so the person you already have can carry more doors instead of more evenings.
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.
How engagements start
One call, about an hour, in French or in English.
We go through how maintenance requests actually reach you today. Which channels, which languages, who sorts them, what your own staff cover, which vendor handles which trade, what counts as an emergency at eleven at night, and who gets called when the first person does not answer.
You get back a written routing and escalation plan for your portfolio. Your trade categories. Your urgency levels, with the French and English wording that triggers each one. Your staff first routing order. Your after hours chain with named fallbacks. And the list of what should be logged on every request.
It is yours to keep and to use, with or without us. There is no cost and no obligation. If it makes sense to go further, that plan is what we quote from.
Built for Canadian property management teams of roughly 150 to 1,500 doors, where maintenance requests currently reach somebody’s personal phone. Pricing is a flat monthly fee based on door count. Nothing per request, nothing per minute, and never a share of a repair invoice.
We do not publish a rate card. Your routing rules, your staff coverage and your request volume decide what this costs. We would rather quote you accurately after an hour of your time than inaccurately before it.
It is priced against what an after hours answering service and a coordinator’s time cost you, not against what you pay for your property management software.
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 or 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.
Book the routing review
Tell us where to reach you and roughly how many doors you manage. We will 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. It is working software, not a prototype.
That the durable position is the intersection rather than either axis. 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. The answer is depth in the dispatch loop and being local, which is a real answer and not an unlimited one.
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