AI Tooling and Context

Copilot's usefulness depends on giving the model the right bounded context and the right tools.

Runtime Context

Every Copilot run should include:

• Organization id.
• Current user id.
• Message id.
• Current date, time, timezone, month, quarter, and year.
• Current page context.
• Current entity context when available.
• Active conversation thread when available.

Time context is required so prompts like "tomorrow", "this month", and "day after tomorrow" resolve correctly.

Current User Context

The current user context should include:

• User name and email.
• Organization role.
• Permission role when available.
• Job role and level when available.
• Teams.
• Skills matrix values.
• Assigned tasks.
• Owned projects.
• Pending approvals assigned to the user.

Use this for prompts such as:

• "What should I work on next?"
• "Show my hours this month."
• "Assign the best person based on skills."

Read Tools

Read tools should expose concise domain intelligence, not raw database dumps.

Common read tool outputs:

• Project summaries.
• Task triage.
• Account briefs.
• Invoice summaries.
• Expense summaries.
• Approval summaries.
• Time totals and grouped hours.
• Team member skills.
• Resource capacity.
• Semantic workspace memory.

For time questions asking for totals, hours, or breakdowns, Copilot should use aggregate hour tools instead of listing raw time entries.

Context Quality Rules

Tools should:

• Return bounded results.
• Include identifiers and readable labels.
• Include status and important dates.
• Include enough evidence for concise answers.
• Avoid exposing fields the user cannot access.
• Prefer exact structured matches over semantic matches.

Navigation Context

Navigation actions should use a generic action registry where possible. If a user asks to open a specific project, invoice, task, account, contact, or credit note, resolve the entity and return one direct action to that record.

Avoid showing many buttons when the user requested one specific record.

Missing Data

When required context is missing:

• Say what is missing.
• Ask for the smallest missing piece.
• Offer a navigation action when appropriate.
• Do not invent values.

Examples:

• Missing recipient for invoice reminder.
• Missing project for task creation.
• Missing assignee.
• Missing approval request.

Related Docs

• Global Search and Command Bar
• AI Memory and Embeddings
• AI Proposals and Execution
• Troubleshooting