Customize the Altify Terminology within MaxAI

Configure MaxAI (via MCP Servers) to recognize and respond using your organization's own names for Altify concepts.

The following are explored in this topic:

• What terminology customization solves
• How it works: two separate steps
• Step 1: create the glossary record (Salesforce UI)
• Step 2: add the glossary to your AI client
• Worked example: renaming Relationship Map to Stakeholder Map
• Troubleshooting

What terminology customization solves

Out of the box, Altify MCP tools use Altify's own names for its concepts — Relationship Map, Insight Map, Key Player, and so on. However, many organizations use different names for the same concepts:

• “Relationship Map” becomes “Stakeholder Map” or “Org Chart”
• “Key Player” becomes “Champion”
• “Insight Map” becomes “Edge”

Without customization, the agent still works correctly, but it speaks and listens in Altify's language rather than yours — replies use Altify's terms regardless of how your organization refers to them, and a request phrased in your organization's own terms may not be understood.

Terminology customization lets you (as an administrator) configure a glossary that maps Altify's terms to your organization's preferred terms, so both the agent's replies and its understanding of your requests use your organization's own language.

How it works: two separate steps

Terminology customization is a two-part configuration, and both parts are needed for full effect:

• Step 1 (Salesforce, admin-configured) controls what the agent says. It affects output only — once set up, the agent's replies consistently use your organization's preferred terms instead of Altify's own labels.
• Step 2 (your AI client, configured separately) controls what the agent understands. It affects input only — without it, a request phrased in your organization's terms (e.g. “Show me the Stakeholder Map”) may not be recognized as a request for the Relationship Map tool.

Step 1: create the glossary record (Salesforce UI)

This step uses the same Altify Customization object (ALTF__Customization__c) as when you Customize the Altify Methodology within MaxAI, but as a distinct, single-purpose record:

Field	What you put in it
Customization Name (standard Name field)	Enter the following (no braces, no package prefix): terminology_glossary
Content (long text)	Your glossary: one line per Altify term (and any known variants) mapped to your organization's preferred term. See the worked example below for the expected format.
Is Active (checkbox)	Checked to activate; unchecked to disable without deleting.

To create the record, do the following:

1. In your Salesforce org, open the App Launcher and select Altify Customizations.
2. Click New.
3. Set Customization Name to terminology_glossary (bare, no braces or package prefix).
4. Paste your glossary into Content, following the format in the worked example below.
5. Select the Is Active check box.
6. Click Save.

There is only one terminology_glossary record per org. Run any smart MCP tool (e.g. ask for an account overview) to confirm the new terms appear in the reply.

Step 2: add the glossary to your AI client

Because the AI client (Claude, ChatGPT or Copilot) — not the Altify MCP servers — decides which tool to call in response to a user's words, Altify cannot configure this side on your behalf. To have the agent correctly route requests phrased in your organization's terms, add the same glossary to your AI client's own custom or project instructions.

1. Open your AI client's custom instructions, project instructions, or system prompt settings (this varies by client).
2. Paste the same glossary block used in Step 1 (or a copy tailored for input-routing — see the worked example).
3. Save, and test by asking a question using your organization's term (e.g. “Show me the Stakeholder Map for Acme Corp”) to confirm it routes to the correct tool.

Worked example: renaming Relationship Map to Stakeholder Map

This section shows the shape a glossary should take, using a small, realistic example rather than a full glossary.

Scenario: your organization calls the Relationship Map the “Stakeholder Map,” and Key Players “Champions.” You want the agent to use these terms in its replies, and to understand requests that use them.

Step 1 content (paste into Content field on the terminology_glossary Altify Customization record):

Customer terminology — this organization uses its own preferred names for
concepts in its Altify account and opportunity plans. When you present the
information below, refer to each concept by the organization's preferred
term on the right instead of the Altify label on the left:
- "Relationship Map" / "Political Map" / "Relationships" → "Stakeholder Map"
- "Key Player" / "Key Players" → "Champion" / "Champions"
Apply the preferred term consistently, including inside headings and
labels; do not also show the Altify label in parentheses or as a gloss.

Step 2 content (paste into your AI client's custom instructions):

When I use the term "Stakeholder Map," treat it as the Altify Relationship
Map and use the corresponding tool. When I use "Champion" or "Champions,"
treat this as the Altify Key Player concept.

With both steps in place: asking “Show me the Stakeholder Map for Acme Corp” correctly calls the Relationship Map tool, and the agent's reply refers to “Stakeholder Map” and “Champions” throughout rather than Altify's own labels.

Troubleshooting

• The Customization Name field must be a bare value. Use terminology_glossary, not {{terminology_glossary}}. A record with braces or a package prefix in the Customization Name field silently fails to match — Altify's default terms slip through and no warning is emitted.
• One Altify Customization record for terminology glossary only. If multiple active records share the name terminology_glossary, behavior is undefined. Disable old records (Is Active = false) rather than leaving duplicates.
• Agent speaks the right terms but doesn't understand them as input: this means Step 1 is done but Step 2 is missing (or was only configured for one user's AI client, not the whole team's).
• Ordinary English words that double as Altify labels (e.g. “Contacts,” “Solutions,” “Assessment”) can occasionally slip through in a reply, echoed from a tool's underlying data values rather than the agent's own wording. This is a known soft limitation — distinctive, multi-word terms (like “Stakeholder Map”) convert reliably; single common words are more prone to leaking through.
• Terminology customization only affects smart (prose) MCP tools. Plain read tools return data as-is; terminology there surfaces as field labels, which this glossary does not rewrite.
• Test before rolling out broadly. Activate the glossary, complete both steps, run an affected tool once, and confirm the reply and routing both work as expected.