Study email localisation

Translates your study email templates for a second region without rewriting each one by hand, and replaces nothing until you approve.

Workflow 12 of 12Study designSeptember 30, 2026

Get the workflow

Enter your details and the prompt appears here, ready to copy.

How do I translate research invitation emails for another region?

Ask an AI tool connected to Great Question to open a study's message templates and translate each into the target language, keeping the structure, merge fields and incentive wording. Have it show each translation beside the original and replace nothing until you approve. Participant-facing copy is the last place for an unchecked draft, so a fluent speaker should read it too.

Who runs it
Whoever owns a study running in more than one language.
Where you sign off · You approve first
Yes, on every translation, before it replaces anything. Participant-facing copy is the last place you want an unchecked draft.
Schedule it · By hand
No.

How to run it in Claude, ChatGPT, Cursor or Copilot

The prompt is the same in every tool. What changes is where you connect Great Question and where you paste it.

Run it in Claude

  1. 1

    Connect Great Question to Claude

    In Claude Desktop, open Settings → Connectors → Add custom connector. Name it Great Question, paste https://greatquestion.co/api/mcp/v1, then Save and Connect and sign in with your Great Question account. Restart Claude so the tools load.

  2. 2

    Paste the prompt

    Start a new chat and paste the prompt. Claude asks before it uses each Great Question tool; allow the read tools, and read anything it proposes to write before you allow it.

Your admin has to switch the MCP on in Great Question first. The MCP guide covers every tool, the security model and a team rollout.

The tools it calls

Named so you can see exactly what the agent touches before you let it near anything.

  • list_study_messages
  • get_study_message
  • get_message_template
  • compose_study_message
  • revise_study_message

What we never automate

Four rules sit under every workflow here, and they matter more than the workflows.

  • Nothing reaches a participant without a person

    No workflow sends an invitation, an email or a reminder. The MCP can do those things. They are left out on purpose, because a scheduled job that contacts your customers is a different category of risk from one that reads a transcript.

  • Nothing launches a study without a person

    An agent can build the screener and draft the messages. Someone still presses go.

  • Nothing reaches a stakeholder unchecked

    The synthesis workflows hand you quotes with links attached so you can check them in one click. Use the click. A misattributed quote in a board deck costs more than the hour it saved.

  • Nothing sees more than the person who connected it

    Permissions follow the individual, so an agent connected by a PM reaches exactly what that PM reaches. Your admin decides whether it is available at all.

Questions

Will the merge fields still work after translation?

They should, because the prompt tells the agent to keep them exactly. Check each one in the side-by-side view; a translated merge field is the most common way this goes wrong.

Should I translate the incentive wording literally?

Keep the amount and terms identical, but let the phrasing read naturally. If the incentive itself differs by region, change it in the study, not in the translation.

Does it send the translated emails?

No. It drafts them and stops. Sending stays with a person, as with every workflow here.

Related reading

More workflows

See all 12