Guides
2 booking systems that work for bilingual appliance repair shops in Quebec City
Appliance repair booking systems for Quebec City shops: two setups for French and English service calls, Charter rules, OPC duties and RBQ checks.
What to take away
- Two appliance repair booking systems work in Quebec Citya Google Workspace bilingual intake form (Google Forms, Google Sheets, Google Calendar) with French-first dispatch, and a Calendly two-lane calendar with language-tagged technician routing.
- French is the default language of service under the Charter of the French Language. English is offered on request, not assumed.
- Intake must collect an RBQ licence number for any job that falls under contractor licensing, and verify it before the visit is confirmed.
- Quebec consumer law adds merchant duties around contracts, cancellation and advertising that your booking confirmations should reflect.
- Both setups fit a shop of two to ten technicians. Pick based on whether your bottleneck is the phone or the calendar.
What a bilingual booking system has to do in Quebec City
Quebec City is not Montreal. Most walk-in and phone demand arrives in French, and English calls cluster around the anglophone communities, the universities and the hospitality and relocation work tied to the city's institutions. A booking system that treats English as an afterthought loses those jobs to shops that answer in the caller's language on the first ring.
The system has three jobs. It captures the request in the language the customer used. It routes the job to a technician who can finish the conversation in that language. It keeps a written record that satisfies both privacy rules and consumer law.
Customer data sits under federal privacy law, and the Office of the Privacy Commissioner publishes its guidance in French for exactly this market. A booking form that stores names, addresses and door codes is a personal information system, and it needs a retention rule you can explain in French at the counter.
The French-language privacy guidance is the plain reference for that.
Quebec also layers its own consumer rules on top. The Office de la protection du consommateur sets out what merchants owe buyers on quotes, contracts and cancellations, and the merchant obligations section is where a repair shop should check its booking wording before printing it on an invoice.
Newer duties keep landing on merchants, and the OPC tracks them under new merchant obligations.
Finally, appliance repair in Quebec often touches licensed building work. The Régie du bâtiment du Québec runs the licence framework that covers contractors, and the RBQ licence framework explains who needs one and what it permits. If your shop subcontracts installation or gas-adjacent work, the licence question belongs in intake, not in a later phone call.
Setup one: a bilingual intake form with French-first dispatch
This setup fixes the phone. One form, two language paths, no separate English line.
The named system is Google Workspace from Google LLC: Google Forms for the bilingual intake, Google Sheets for the queue, and Google Calendar for the French-first dispatch list. A typical build for a two to ten technician shop takes 2 to 4 hours (typical range, not a vendor figure).
The form opens in French. A language toggle sits in the top right, labelled in both languages, and the choice switches the whole form, including error messages and the confirmation email. Nothing is half-translated: a form that asks for the address in French and confirms in English reads as careless.
Fields that matter for a Quebec City shop:
Bilingual intake form fields
- Full name, phone, second contact number
- Address with borough, door code, buzzer
- Appliance type, brand, model, serial
- Preferred languageFrench or English
- RBQ licence number for installation work
- Access notespets, parking, elevator, concierge
- Consent line in chosen language
Once submitted, the ticket lands in one queue but carries a language tag. Dispatch reads French tickets first, because that is the default language of service and the larger share of volume.
English tickets go to the technicians who can handle them, and if none is free, the customer gets a call back in English with a realistic window rather than a vague promise.
The RBQ step is a checkbox, not a paragraph. For jobs that need a licensed contractor, staff open the licence verification tool and confirm the number before the visit is booked. Record the check on the ticket. If a customer asks why, the answer is simple: Quebec requires it, and it protects them.
This setup suits shops where most bookings still arrive by phone or through a web form, and where the same two or three people answer everything. It pairs well with a written SOP checklist so that intake, verification and confirmation happen the same way on a busy Monday as on a quiet Thursday.
Setup two: a French and English scheduling calendar with technician routing
This setup fixes the calendar. Instead of one queue with language tags, you run two visible lanes on the same board: FR and EN. Every job is placed in a lane before it is assigned a time.
The named system is Calendly from Calendly LLC. You build two event types, one labelled FR and one labelled EN, and use round-robin routing to assign only technicians who speak that language. A typical build for those two event types and routing rules takes 1 to 2 hours (typical range, not a vendor figure).
Technicians carry a language capability in their profile. Routing rules then do the work:
Two-lane language routing
- Job arrives, placed in FR or EN lane
- French call: FR tech, then bilingual
- English call: EN or bilingual only
- No match: callback list with language
- Bilingual techs absorb overflow from both
A worked example. A Sainte-Foy customer books a dishwasher repair in English for Tuesday morning. The FR lane is full, the EN lane has one opening at 9:00 with a bilingual technician, and the job is placed there.
The confirmation goes out in English, the technician's notes are written in French for the office file, and the invoice prints in French with an English courtesy copy. Nothing about that job required a second phone call.
This is where scheduling that works earns its keep: the language lane is a constraint, and constraints only help if the calendar shows them. Shops that hide language in a technician note end up double-booking the same bilingual tech every week.
Two-lane calendars also make hiring decisions visible. If the EN lane is chronically short, you know what the next hire needs to speak. If the FR lane is short, you have a service problem in your home market, which is worse.
Charter of the French Language considerations for customer communications
Quebec's Charter of the French Language makes French the normal language of commerce and service. In practice, for a repair shop, that means French is the default in advertising, contracts, invoices, receipts and posted notices. Customers may be served in English, and a business may offer English, but English cannot be the language you lead with.
What this changes in a booking system:
Charter of the French Language considerations
- Default templates, confirmations and reminders ship in French. English versions exist and are sent when the customer chose English.
- The website and booking page are French-first, with an English version available, not the reverse.
- Invoices and work orders are French. An English copy is a courtesy, not the original.
- Staff greet callers in French. Switching to English on request is normal and expected.
- Signage, van lettering and ads follow the same rule.
The practical trap is the third-party tool. Many North American scheduling products are English-only out of the box, and their customer-facing messages are the ones that break the rule. Before you commit, test the confirmation email, the reminder text and the invoice PDF in French.
If the tool cannot produce them, that is a reason to look elsewhere, and choosing appliance repair software should weigh language output as heavily as route optimisation.
Consumer-facing wording on quotes and cancellations should match what the OPC expects of merchants, in French. That is a legal question, not a design preference.
Comparing the two setups for a small Quebec City shop
Comparing the two setups
Setup one: bilingual intake, French-first dispatch
- Best for
- Phone-heavy shops, one dispatcher, two to five techs
- Language control
- Language tag on the ticket, manual dispatch order
- Setup effort
- Low: one form, one queue, one rule
- Failure mode
- French tickets starve when the queue is busy
- Reporting
- Count of jobs by language, response time by language
- Fit with RBQ checks
- Checkbox at intake, verified before booking
Setup two: two-lane calendar with routing
- Best for
- Shops with mixed-language teams, six or more techs
- Language control
- Language lane on the calendar, automatic routing rules
- Setup effort
- Medium: technician profiles, lane rules, callback list
- Failure mode
- Lanes drift and bilingual techs get overloaded
- Reporting
- Utilisation by lane, unfilled English slots, callback backlog
- Fit with RBQ checks
- Checkbox at intake, verified before the job enters a lane
Neither setup needs a large budget. Both need discipline about the language field, because a booking system only routes on what intake actually captures.
Dispatch flows that keep both language queues moving
A morning flow that holds up in a Quebec City shop:
Morning dispatch flow
- Sort overnight web bookings by language before 7:30
- Assign French tickets first by customer window
- Match English tickets to EN or bilingual techs
- Verify and mark RBQ jobs before dispatch
- Post both language lists for technicians
During the day, the rule is simple: a technician who finishes early takes the next job in their language lane, not the next job overall. That one habit prevents the English queue from quietly ageing while French work gets cleared.
End of day, log three numbers: jobs completed per lane, callbacks owed per lane, and any ticket that sat unassigned past its window. Those three numbers tell you whether the setup is working or whether you need the other one.
A shop that tracks them for a month usually knows which model fits, and the wider workflow for owners is where that habit belongs.
If you are still running a paper book and a shared inbox, the migration order matters more than the tool. Move intake first, then the calendar, then the reporting.
Shops that buy the biggest platform first tend to abandon it, and the subscription question is worth settling on evidence, as this review of which software deserves the subscription argues.
