Public House offers comprehensive translation and multilingual communication services to ensure that housing programs are accessible and inclusive for all Applicants.
Applicants can select or update their preferred language at any time during screening, application, or survey steps, ensuring consistent communication throughout their housing journey.
All system content — including Field labels, notifications, messages, and help text — is automatically displayed in the applicant’s selected language. Original data remains unaltered in Salesforce, preserving data integrity and consistency across records.
About Translations
Public House uses the Google Translate API to provide real-time, multilingual support. This is the only scalable method for translating a platform of this size, including:
These tools allow programs to offer broad language access without needing to manually translate every component.
Using translations is optional and not a paid feature. While Google Translate is a powerful tool:
- Accuracy may vary with housing-specific language or complex phrasing.
- Clients can adjust their default-language text to help improve translated output.
For many organizations, translations provide a strong foundation for accessibility, with the option to tailor key content for even greater clarity.
How Translation Works
- Applicants choose a preferred language during screening or application.
- Public House uses translation APIs to dynamically translate content while preserving original data in Salesforce.
- That selection is saved to the Field: PHA__Preferred_Language__c
- Updated with screening form submissions, or during the application process.
All translated pages and communications include the following disclaimer:
Translated from English to {Language} by Google Translate. Please ask for help if anything is unclear.
Supported Languages
To manage system performance and API limits, Public House supports up to 10 active languages per system. Current supported languages include:
- English
- Spanish
- French
- Amharic
- Arabic
- Chinese (Simplified)
- Tagalog
- Haiti Creole
- Korean
- Portuguese
- Russian
- Vietnamese
What’s Translated
Applicant-facing content translated through the platform includes:
- Screening Forms, Applications, Recertifications, and Annual Surveys
- Program-specific descriptions, messages, modals, warnings and help text
- All 24 standard Public House email with customized content and SMS templates
- Staff comments in Document Corrections emails
- Property descriptions
- Screening submission ineligible messages
- Picklist options, validation messages, modals, and attestation statements
What’s Not Translated
Not translated:
- Applicant names and addresses
- Free-form responses (stored in original input language)
- Help requests submitted from the applications are not translated. Any responses to these emails are also not translated.
Common free-form fields include:
- Special needs or accommodation descriptions
- Significant income changes
- Assets sold or transferred
Preventing Translation
To exclude specific terms from translation, wrap them in <notranslate> tags.
<notranslate>Proper Name</notranslate>
Supported in:
- Question or help text
- Descriptions
- Custom emails
- Confirmation and attestation statements
- Required document explanations
- “I don’t have it” responses
Note: No Translate tags are not supported for picklist options.