📌 This article is for users of elvex 2.0. Find out which version you're using.
Context is at the heart of what makes elvex powerful. It's what allows elvex to feel less like a tool and more like a knowledgeable colleague who already understands your world.
Why Context Is Powerful
Context is the guidance that transforms elvex from a capable new hire into a seasoned colleague who just knows your team, your tools, your priorities, the way things work around here. You set it once, and it carries into every conversation automatically.
A new hire needs hand-holding. A seasoned colleague picks up a vague request and runs with it, because they already understand the context behind it. The difference isn't intelligence, it's institutional knowledge. Context is how you give elvex that knowledge.
When context is set well, elvex can:
Respond to vague requests with precision ("email my team" actually emails the right people)
Skip generic answers in favor of ones grounded in your company's specific tools and processes
Route questions to the right resources without you having to know where things live
Act like a team member, not just a search engine
Context flows into elvex at three levels, each one layering on top of the last.
Company Context
Company context is set by administrators and flows into every user's conversations across the entire organization. It's the shared organizational knowledge layer: what the company does, its products, its terminology, its norms — and it's a powerful lever for shaping how elvex behaves for your entire team.
Admins can use company context not just to inform elvex, but to nudge or direct user experiences: steering people toward the right resources, enforcing consistent behaviors, and ensuring that organizational standards are applied without anyone having to remember to ask.
Examples of what to put in company context
What to add | Why it helps |
Company mission and product descriptions | Every conversation starts from an accurate understanding of what you do |
Key terminology and internal jargon | "CRO" means something specific at your company — define it once |
Brand voice guidelines | Drafts across the org reflect a consistent tone |
Process standards and rules | "Always check X datasource before answering Y questions" applies everywhere |
Tool and integration conventions | "We use Salesforce for all CRM activity" — no need to repeat it |
Company context example
We store all internal IT documentation in the IT Knowledge Base datasource, which is publicly accessible to all employees. Whenever a user asks an IT-related question — software access, device setup, VPN, policies — check this datasource first and answer from it before offering any general guidance. If the answer isn't there, say so clearly and direct the user to submit a ticket via the IT portal.
What this unlocks:
Every employee asking an IT question gets answers grounded in your actual policies — not generic internet advice
No individual team or Space has to remember to configure this — it applies automatically, everywhere
The IT team controls the source of truth; the company context ensures it's always consulted first
Personal Context (My Space)
Personal context lives in My Space — your private, curated workspace in elvex.
Every conversation you have automatically includes your personal context. You never have to re-explain yourself.
Examples of what to put in your personal context
What to add | Why it helps |
Your team roster with email addresses | "Email my team" works without you having to specify who that is |
Slack channels to monitor for team activity | elvex can check the right channels when you ask what your team is up to |
Your role and key responsibilities | Responses are framed around what actually matters to you |
Tools you use daily (Slack, Notion, Salesforce, etc.) | elvex knows where to look and which integrations to use |
Your communication style preferences | "Write a follow-up email" comes out in your voice, not a generic AI voice |
Regular workflows or recurring tasks | "Make me a QBR" can trigger a specific agent built for that purpose |
Key stakeholders and their roles | Context for who's involved when you reference a person by name |
Time zone and working hours | Scheduling and calendar tasks are accurate without clarification |
Current projects you're working on | elvex can connect the dots when you reference project names |
Personal context example
My name is Allison. I lead Customer Success at elvex. My team includes:
Jordan Park — [email protected]
Sam Rivera — [email protected]
Devon Chen — [email protected]
Morgan Lee — [email protected]
My team's primary Slack channels are #cs-team (internal updates) and #customer-health (account signals and escalations). Check both when I ask about team activity.
For my communication style there are voice and tone examples in the CS Writing Style datasource; reference it whenever I ask you to draft anything.
When I say "make me a QBR," use the QBR Generator agent. It's built for this and knows how to pull the right data.
What this unlocks:
"Draft a team update email" → addressed to all four teammates, written in your voice based on the style datasource
"What's my team been working on?" → elvex checks #cs-team and #customer-health for recent activity
"Make me a QBR for Acme" → hands off directly to the QBR Generator agent, no further explanation needed
"Create a follow-up in Salesforce" → elvex knows which integration to use
Space Context (Shared Spaces)
Spaces are shared workspaces for teams or projects. When you or your team chats within a Space, the Space's context, including all its pinned resources, flows into every conversation automatically.
Space context is the shared foundation for everyone in that Space. It's where you put information the whole team needs elvex to know: the purpose of the Space, what's in it, and any instructions for how it should be used.
What to put in a Space's context
What to add | Why it helps |
The team's or project's purpose | Every conversation starts from the right frame of reference |
What each pinned datasource is for | "When someone asks about X, use this datasource" removes ambiguity |
What each pinned agent is for | Helps elvex route to the right specialist automatically |
Preferred tone or communication style | Useful for content and marketing Spaces |
Escalation paths or decision-making rules | "If unsure, ask the user before taking action" |
Common terms or internal jargon | Acronyms, product names, team nicknames — defined once, understood always |
What should NOT happen | "Do not share pricing information" or "do not summarize without citing a source" |
Space context example: a product launch project
This Space is for the Q3 Product Launch. All relevant assets live in three datasources pinned here:
Launch Brief — the source of truth for messaging, positioning, and target audience. Always reference this first.
Competitive Research — analysis of how competitors have positioned similar features; use this when drafting differentiation language.
Draft Assets — in-progress copy, FAQs, and announcement drafts. Check here before creating anything new to avoid duplicate work.
The goal of this Space is to keep launch content consistent and grounded in the brief. When summarizing or drafting, always cite which datasource you drew from.
What this unlocks:
Any team member who chats in this Space immediately has access to all three datasources — no manual attachment needed
"Draft the press release intro" → written against the brief's positioning, checked against competitive research
"Is there already a FAQ draft?" → elvex checks Draft Assets before creating anything new
New team members added to the Space are instantly oriented without a separate onboarding doc
Space context example: a Sales team hub
This is the Sales team's shared workspace. The Competitive Intelligence datasource contains battlecards and competitor analysis. The Pipeline datasource reflects our current Salesforce data. The Battlecard Agent is the best tool for live deal prep — use it when someone needs help positioning against a specific competitor. Our ICP is mid-market and enterprise companies with 250+ employees, HQ in North America or Western Europe, Director-level contact or above.
What this unlocks:
"Help me prep for my Acme call" → routes to the Battlecard Agent with the right context
"What do we know about Competitor X?" → pulls from your actual intelligence, not Wikipedia
Every rep who chats in this Space gets answers that reflect your team's real ICP and positioning
Getting Started
You don't need to write a perfect context document on day one. Start small:
For personal context: Write 3–5 sentences about your role and your team. Add email addresses and the Slack channels where your team is most active.
For a shared Space: Describe the Space's purpose in one sentence. Add one line about each pinned resource — what it is and when to use it.
For company context (admins): Start with the one or two behaviors you most want to be consistent across the organization — a datasource everyone should check, a tool convention, a tone guideline.
You can always refine it. The more you use elvex, the more you'll notice moments where context would have made the answer better — and that's exactly when to update it.
Tip: You can set up personal context by chatting with elvex directly. Say "Interview me to set up my personal context" and elvex will walk you through it conversationally.