Gale Account Context (Gale Suite, Premium Feature)

Account Context allows administrators to provide Gale with organization-specific information, making its responses more accurate, relevant, and aligned with operational priorities. By adding Account Context, Gale can tailor recommendations, use your preferred terminology, and prioritize the risks that matter most to your business.

🔒 This is a premium feature. To learn more or request access, contact your Tomorrow.io Account Manager or email sales@tomorrow.io. 

Note: Only account administrators can add or modify Account Context.

When to Use Account Context

Use Account Context when you want Gale to:

• Reference your operational priorities (e.g., safety, continuity, cost efficiency)
• Align responses with your industry or domain focus
• Reflect your preferred tone, terminology, and languages
• Reduce generic outputs and generate actionable recommendations

How to Configure Account Context

You can configure Account Context from two entry points:

Option 1: From Account Settings

1. Navigate to Account Settings > Knowledge Base.
2. In the Gale Account Context section, enter text describing your organization’s priorities and guidelines.
3. Use the categories below as a template for clarity and consistency.
4. Click Save when finished. Updates apply to all Gale users in your account.

Option 2: From the Gale Interface

1. Open Gale within the platform.
2. Click the gear icon (⚙️) in the upper corner of the chat window.
3. In the Gale Account Context section, enter text describing your organization’s priorities and guidelines.
4. Use the categories below as a template for clarity and consistency.
5. Click Save when finished. Updates apply to all Gale users in your account.

Note: File uploads are not supported. For complex configurations or multiple-language setups, contact support@tomorrow.io.

Template for Admins

When setting up Account Context, provide details in each of the following categories:

Operational Instructions

What Gale should prioritize during weather events.

• Example: “Ensure crew safety and avoid delays by monitoring thunderstorms along routes.”

Industry/Use Case Focus

The primary industry or business domain your organization operates in.

• Example: “Airline operations,” “Sports & Entertainment,” “Logistics & Delivery,” “Construction & Infrastructure.”

Operational History / Priorities

Recent challenges, recurring disruptions, or specific goals Gale should account for.

• Example: “We experienced major delays due to snow last winter; avoiding schedule disruption is our top priority.”

Preferred Language(s)

Specify which language(s) Gale should use in responses and reports.

• Example: “English only,” “Spanish for staff notifications,” “French for reports.”

Terminology & Style

Provide any specialized language or tone preferences.

• Example: “Say ‘all clear’ instead of ‘no risk detected.’”

Examples by Industry/Use Case

Aviation

• Operational Instruction: “Prioritize flight safety and minimize diversions by monitoring thunderstorms, turbulence, and volcanic ash.”
• Priority: “On-time performance is critical; communicate weather risks early.”
• Language: “English for dispatch, Spanish for crew briefings.”

Sports & Entertainment

• Operational Instruction: “Ensure fan and staff safety; minimize game delays from lightning and heavy rain.”
• Priority: “Smooth stadium operations and timely communication with security staff.”
• Language: “English, with simplified outputs for public announcements.”

Logistics & Delivery

• Operational Instruction: “Maintain safe and on-time deliveries by tracking snow, flooding, and high winds.”
• Priority: “Avoid service delays in high-demand regions.”
• Language: “English for managers, local language for drivers (e.g., French in Quebec).”

Construction & Infrastructure

• Operational Instruction: “Protect worker safety by monitoring extreme heat, lightning, and high winds.”
• Priority: “Avoid downtime and equipment damage.”
• Language: “English for reports, Portuguese for onsite teams in Brazil.”

Energy & Utilities

• Operational Instruction: “Monitor storms, floods, and ice buildup to protect assets and prevent outages.”
• Priority: “Minimize downtime and ensure grid reliability.”
• Language: “English for HQ, Spanish for field teams.”

Best Practices

• Review and update Account Context quarterly or whenever operational priorities change.
• Keep instructions concise and action-oriented.
• Avoid including sensitive or confidential data.
• Coordinate with your Account Team for multi-region or multi-language configurations.

Need Help?

For assistance setting up or maintaining Gale Account Context, contact your Tomorrow.io Account Manager or reach out to support@tomorrow.io.