Skip to content
  • There are no suggestions because the search field is empty.

How to Require Learners to Use Specific Terminology

Learn how to configure a Roleplay environment so learners are scored on using your organization's preferred terminology — for example, saying "learner" instead of "user."

Roleplay has no dedicated "required words" field, but you can require specific terminology by combining two parts of the environment you already author: a Learner Goal and the Description. Together they make the requirement visible to the learner and scored against the session transcript.

Set It Up

  1. Add a Learner Goal that names the skill — kept generic. In your environment's Learner Goals, add a goal such as:

    The learner uses the correct terminology.

    Learner Goals are scored on every session (Met / Partially Met / Not Met) against the transcript, so this is what makes the requirement count. Keep the goal to a single line and do not list the specific words here.
  2. Define the actual terms in the Description. The Description is shown to the learner. Spell out the terminology so they know the expectation before they start, and so scoring has a concrete standard to check against:

    Refer to the people you support as "learners," never "users."

The goal gets scored, the learner sees the rule up front, and the specifics live in the learner-facing instructions instead of cluttering the goal.

Reinforce It in the Conversation (Optional)

For added realism, add a behavioral trigger to the AI Character → AI Instructions (these are hidden from the learner):

If the learner says "users," gently correct them — "We call them learners here" — then continue.

This makes the habit feel natural during practice. It does not affect the score on its own — the Learner Goal above is what's scored.

Two Things to Watch

    • To enforce terminology across every environment, use Performance Metrics, not the steps above. Performance Metrics are scored on every session account-wide, so a custom metric such as "Uses approved terminology" would apply everywhere. Because terminology is usually specific to one scenario, treat this as a deliberate account-level decision rather than a default.
    • Don't try to enforce learner wording through the AI Character's background knowledge. That content defines what the character knows and says — not what the learner is required to say. Use a Learner Goal and the Description instead.

    Need help? Submit a ticket to Customer Solutions for help configuring environment goals and scoring.