Business supplies and services: Customer portal for localisation providers
A customer portal for localisation providers where product teams view language reviews, check screenshots and answer string questions, organised per release and per language.
What customers of localisation providers want to see.
A product team working with a localisation provider receives translator questions, per language review reports and screenshots showing problems during every release. They arrive by email at the product manager, who forwards them to a developer or a colleague in the market. Answers come back in different threads, and a decision about a term in one language never reaches the translator of another. Localisation providers lose time merging answers and cannot see which questions are holding up the release. A portal needs to gather those questions, reviews and decisions per release and language.
Customer portal for localisation providers
Example- 1
Set up access per role
DoneFor each client you decide who sees what.
- 2
Show questions and reviews
In progressTranslator questions appear next to the string they concern, with the screenshot attached.
- 3
Feed decisions back
NextAn answer or a decision on a term is recorded with a name and date and goes straight to the translators involved.
From invitation to approval.
Set up access per role
For each client you decide who sees what. The product manager sees every language and the schedule, a developer answers questions on context and variables, and an in market reviewer sees only their own language. Each role gets just what it needs, and it stays clear who may decide on terminology.
Show questions and reviews
Translator questions appear next to the string they concern, with the screenshot attached. Review reports per language list reported issues with category and severity. Screen testing screenshots sit with the language, so the client can spot overlong text or clipped buttons before the release goes live.
Feed decisions back
An answer or a decision on a term is recorded with a name and date and goes straight to the translators involved. If a decision applies to several languages, every translator sees it. Open questions blocking the release sit at the top, so the product manager knows where their team needs to respond first.
Less email, the same records.
Product teams use an issue tracker for their own development work and sometimes a translation platform holding the strings. The portal replaces neither but is the place for collaboration with the provider: questions, reviews, screenshots and decisions. A question that is really a bug, such as a string never made translatable, can be passed on by the client to their own tracker. You own the reviews and reports; the client owns decisions about source text and terminology.
Involve client reviewers or not
Many clients have colleagues in the market who want to check the translation. Bringing them into the portal gives quick feedback but also more opinions on style. A clear role with the ability to comment, and one decision maker per language, keeps it workable. Without that agreement, discussions arise that delay the release.
Batch questions or ask directly
Translators who ask every question immediately get quick answers but swamp the product team. Batching per day or per language is calmer but can leave a translator waiting. The portal lets the project manager batch, while flagging questions that block work as urgent so they reach the right person at once.
Decide per language or centrally
Some terms must be treated the same in every language, such as product names that are never translated. Others are a choice per language. The portal lets a decision be recorded centrally for all languages or per language, so a product name is not translated in one language and left alone in another.
What customers find in the portal.
The portal opens with access per role, questions on strings with screenshots, review reports per language, screenshots from the screen check and recorded decisions. Before clients log in, we replay an ordinary release where a few context questions need answering, and a release where an in country reviewer wants to change a term already used in other languages. Passing items to the client's tracker and an overview of decisions per product can be switched on later.
View pricingSupport and updatesGood to know.
Explore pricing and optionsDoes the developer need an account to answer questions?
That is the most convenient, because they then see only the questions about context and variables. If a client prefers fewer accounts, the product manager can forward questions through a link that lets the developer answer just that one question.
How do we stop in market reviewers rewriting everything?
By agreeing upfront what they look for, such as terminology, tone and errors, and what is not a reason for change, such as personal style preference. The portal asks for a category with every comment, so the project manager can see which comments are real errors and which are preferences.
Can we look back at earlier releases in the portal?
Yes. Questions, reviews, screenshots and decisions are kept per release. If a question later arises about a choice in an earlier version, you find the release and the decision. Terminology decisions carry forward into later releases.
Can the client request a review themselves?
Yes. If a product team has doubts about an existing translation, it can request a review for a language or part of the product. It reaches the project manager as a request, who schedules it and lets the client know through the portal when the review is ready.
What often connects to this.
- Digital job cards for localisation providersDigital job cards for localisation providers: a string package with version reference that records translation, review and screen testing per language, so every delivery traces back to a release.
- Website for localisation providersA website for localisation providers that explains how software, apps and help content are translated and tested per release, so a product team knows what to supply and when.
- Enquiry form for localisation providersAn enquiry form for localisation providers that gathers source strings, screen context and release details, so the language team knows where every string appears before translation starts.
One place for your customers.
Start with a short intake. Then we schedule a call to show the software with your services, team and way of working.
WhatsAppinfo@vorlyo.com Customer portal for localisation providers: language reviews, screenshots and string questions per release and language, with product team responses recorded.
- Set up access per role
- Show questions and reviews
- Feed decisions back