Core Docs - Core Concepts - Setting Your Organization Context

Rock Version: v20.0
Last Modified: 2026-07-15 1:52 PM

Your organization context is a short description of who your organization is so every agent knows. Write it once and all your agents benefit.

Think of it as a quick onboarding for a new staff member: your name, your campuses, what you call things in Rock, how your organization works. If you leave this field blank, Rock fills in a default using your organization name, address and phone number. That's a starting point, but your own context makes agents noticeably more useful.

Keep it Short
This prompt is added to EVERY request you make through Chat Agents, that means you want to keep it short, and well written. Just start with the basics (Organization Name, Location, etc) then adjust from there.

Where to set it

Navigate to Admin Tools > Settings > AI Agents, then select Settings. The organization context field is there.

A good example

Rock Solid Church is a Christian church based in Phoenix, Arizona, located at 3120 W Cholla St Phoenix, AZ 85029. Our main office number is (555) 555-0100 and our website is rocksolidchurchdemo.com.
How we use Rock: We use Groups to manage both small groups and serving teams. "Small Groups" are small groups of Group Type "Small Group" (Group Type ID 25). "Serving Teams" are groups of Group Type "Serving Team" (Group Type ID 23). When staff mention "a group," they likely mean a Small Group unless they specify otherwise.
Campus: Main Campus (MAIN).
Weekend services: Saturdays at 4:30 PM; Saturdays at 6:00 PM; Sundays at 9:00 AM; Sundays at 10:30 AM; Sundays at 12:00 PM.
We follow up with every first-time guest, usually within their first week. A "first-time guest" is anyone whose first visit was within the last 90 days with no prior record in Rock. We use the term "the directory" to refer to the People section.

Short, factual, specific. No behavior instructions. Just the facts about who you are.

Using Lava

The organization context field supports Lava, processed once when the context is assembled. The best use is pulling values Rock already stores rather than duplicating them as plain text you'll have to remember to update.

For example, if your organization stores your giving page URL as a Global Attribute, you can pull it directly:

Our online giving page is {{ 'Global' | Attribute:'GivingUrl' }}.

When that attribute is updated in Rock, your organization context reflects it automatically. No need to edit this field every time something changes. Keep Lava to simple merge fields; complex logic here causes more confusion than it prevents.

What to include (and what to skip)

Include: your name, location and campuses; terminology that differs from Rock's defaults ("We call small groups 'Life Groups.' In Rock, these are Groups of Group Type 'Life Group.'"); how you use specific Rock features; shorthand your staff uses that the agent would otherwise misread.

Skip: behavioral instructions (those belong in each agent's Instructions field); information the agent can look up itself; anything sensitive you wouldn't put in a staff handbook. More is not better. A long context can interfere with how the agent processes requests.

Troubleshooting