Do you support inspections in other languages?

Every customer-facing string — step instructions, buttons, consent text, error messages — can be provided per language on a template, and the recipient's language is selected when the inspection is sent.

This matters more than it sounds: completion rates drop sharply when the prompts are not in the customer's first language.

Invitation and reminder emails and SMS follow the same language selection, so the entire journey is consistent.

Reports can be generated with localised section headings while your team continues to work in the workspace's own language.

Live support and inspection sessions are agent-led, so the spoken language is whatever your agent speaks; the on-screen customer UI still follows the localised template.

Virtual Inspection Pro supports localisation of customer-facing prompts, emails, and SMS per template or per recipient, so a Spanish-speaking customer can experience the whole customer-facing flow in Spanish. For a multi language inspection programme, decide how your team will collect language preferences before invitations go out. Ask customers directly rather than inferring their preferred language from a name, address, or browser setting.

Use a localized inspection template when a recurring workflow needs a consistent language version, such as Spanish instructions for residential property inspections. Use recipient-level localisation when customers following the same workflow need different languages. Before launch, have your team check that the invitation, reminders, and inspection instructions use the intended language consistently. Keep a process for correcting a mistaken preference, and tell customers how to request language assistance without having to complete the inspection first.

A useful translation tells the customer exactly what to do, not merely what each English word means. Have a qualified bilingual reviewer check technical terms, safety warnings, and instructions about photographs or measurements. For inspectors and property teams, distinguish between photographing an electrical panel's exterior and removing its cover. Localised wording should never turn a safe observation request into an instruction to handle hazardous equipment.

Maintain equivalent requirements across language versions: the same item, requested view, and stopping conditions. A Spanish inspection flow should not omit a warning or add an evidence requirement absent from the original. Test the wording on a phone with representative users, including people unfamiliar with inspection terminology. W3C's mobile accessibility guidance is relevant to this review: translation alone does not address accessibility barriers on mobile devices. Check readability and comprehension alongside language accuracy, and record approved wording in your team's documentation.

Consider a property team arranging a move-out inspection for a resident who prefers Spanish. Staff confirm the preference during intake and prepare Spanish customer-facing prompts, email, and SMS. Before sending the real invitation, a bilingual reviewer follows a test journey on a phone. The reviewer checks whether each instruction makes sense without an English explanation and whether the resident can understand what evidence is being requested.

Suppose an instruction asks for a photograph of damage beneath a sink. The reviewer should confirm that the Spanish wording identifies the location clearly and does not suggest dismantling plumbing. If the resident later submits an unclear image, staff should clarify the request in the resident's preferred language rather than immediately treating it as non-compliance. This acceptance check is an operational recommendation, not a claim that the product automatically translates customer submissions or performs translation quality assurance.

Localised customer communications do not establish that reports, internal screens, customer-written responses, or live conversations are translated. Confirm any needs beyond prompts, emails, and SMS before deployment. Government agencies, insurers, and lenders should identify who will review unfamiliar-language submissions and resolve ambiguous technical terms. Use an appropriately qualified bilingual reviewer or interpreter when misunderstanding could affect a decision.

Language support also does not make every inspection suitable for remote completion. ICC's remote virtual inspection guidance provides general context for planning these workflows; the responsible authority still determines what is acceptable. Arrange human review when evidence conflicts or instructions remain unclear. Consider an in-person visit when safe access, image quality, connectivity, or the required physical examination prevents a reliable remote assessment, even after language assistance.