System Prompts
The system prompt is your agent's DNA -- it defines who the agent is, how it behaves, and what it knows. A well-crafted system prompt is the difference between a helpful agent and a frustrating one.
The Three Context Layers
Before diving into system prompts, it helps to understand how MeetLoyd builds the complete context an agent sees at runtime. There are three distinct layers, each with a different purpose and change cadence:
| Layer | What It Is | Changes | Example |
|---|---|---|---|
| System Prompt | How the agent works. Role, personality, methodology, expertise, behavioral rules. | Rarely (role evolution) | "You are a Sales Development Rep. Data-driven, concise." |
| Charter | Who the agent is in this org. Mission, boundaries, who to escalate to, what requires approval. Generated during Team Starting. | Quarterly (org restructuring) | "Mission: increase pipeline 30%. Cannot access Stripe. Escalate deals >$50K." |
| Intent State | What to focus on now. Boss-defined weekly priorities, hard/soft constraints, success criteria. | Weekly (priorities shift) | "Focus: EMEA enterprise leads. No cold emails to existing customers." |
All three are injected into the agent's prompt at runtime:
- System prompt = Layer 1 (always present, the foundation)
- Company context = Layer 2 (editable via dashboard)
- Charter + Intent State + Memory + Tasks = Layer 3 (built dynamically at execution time)
The system prompt tells the agent how to work. The charter tells it where it fits in the organization. The intent state tells it what to prioritize right now. Without the charter, agents drift from their organizational role. Without intent state, agents work on last week's priorities.
What Goes in a System Prompt?
The system prompt is the first thing your agent "reads" before every conversation. It tells the agent who it is, what it can do, how it should behave, and what it should avoid.
Anatomy of a Good System Prompt
A complete system prompt typically covers these areas:
| Section | Purpose | Example |
|---|---|---|
| Identity and Role | Who the agent is and what its job is | "You are Sarah, the IT Helpdesk Assistant at Acme Corp." |
| Capabilities | Specific actions the agent can take | "Reset passwords (with identity verification), create tickets, check system status" |
| Boundaries | What the agent should NOT do | "Cannot access production systems, cannot share employee data" |
| Knowledge | Domain-specific information | "We use Okta for SSO, Slack for communication, ServiceNow for ticketing" |
| Communication Style | Tone and formatting preferences | "Friendly but professional, use numbered steps for procedures" |
| Escalation Rules | When to hand off to a human or another agent | "Escalate after 3 failed attempts, always escalate security incidents" |