Core Docs - Core Concepts - Setting Your Organization Context

Rock Version: v20.0
Last Modified: 2026-04-30 3:49 PM

Your organization context is a short description of who you are that every agent gets automatically. 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.

Where to set it

Navigate to Admin Tools > Setting > 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 rocksolidchurch.com.

Campus: Main Campus (MAIN). Weekend services: Saturday at 4:30 PM and 6:00 PM; Sunday at 9:00 AM, 10:30 AM and 12:00 PM. Average weekend attendance is 108.

How we use Rock: We use Groups to manage both small groups and serving teams. "Connect Groups" are small groups of Group Type "Connect Group." "Serving Teams" are groups of Group Type "Serving Team." When staff mention "a group," they likely mean a Connect Group unless they specify otherwise.

Our Connection Request workflow is used for all first-time guest follow-up. 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. "Giving" refers to Financial Transactions.

Fiscal year: January through December.

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.

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 org 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

The agent doesn't know our terminology. Add the mapping: "We call our small groups 'Life Groups.' In Rock, these are Groups of Group Type 'Life Group.'" One line is usually enough.

The agent gets confused about what "groups" means. Rock uses Groups for many things. Be specific about which Group Types your staff mean in everyday conversation.

The agent seems to ignore part of my context. Trim it. Remove anything the agent can look up itself and anything that duplicates what's in an agent's Instructions field.

The agent is behaving oddly after I updated the context. Start a new conversation. New context takes effect in new conversations, not existing ones.