schedule-meeting

name	schedule-meeting
description	Prepare a conflict-free meeting; confirm before creating.
metadata	{"short-description":"Prepare meetings with verified participants"}

Schedule Meeting

Outcome

A conflict-aware meeting proposal with correct participants, timezone handling, purpose, and agenda.

CRM-neutral operating contract

• Discover available CRM, communication, calendar, knowledge, and file capabilities before choosing a retrieval plan. If no live CRM is available, use user-supplied exports when that still satisfies the request; never imply a live write is possible.
• Map records by meaning, not vendor labels: organization, person, lead, opportunity, activity, product, service record, user or team, and knowledge item. Inspect schemas and custom fields, preserve native IDs, stages, currencies, timezones, and fiscal periods.
• Keep observed facts, derived conclusions, and missing information distinct. Anchor consequential claims to record IDs, fields, timestamps, or named sources, and state access or freshness limits.
• Start read-only. Before creating, updating, assigning, sending, or scheduling, show the exact proposed action and obtain confirmation unless the current request already authorized that exact mutation.
• Obey connected-system permissions, resolve ambiguous records or people instead of guessing, check for duplicates before creation, and report partial failures without repeated retries.

Workflow

1. Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
2. Retrieve the minimum authorized evidence needed from the following inputs: Meeting objective, participants, duration, date constraints, timezones, working hours, availability, location or conferencing needs, CRM context, and organizer preferences.
3. Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
4. Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
5. Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.

Analysis rules

1. Resolve every participant identity and email address; ask when duplicate or ambiguous candidates remain.
2. Check timezones, working hours, conflicts, buffers, and required attendees before suggesting slots.
3. Use the customer objective and current CRM context to draft a specific title and agenda.
4. Do not expose one participant's private calendar details to another; describe availability only as needed.

Required output

• Resolved participants
• Two or three viable slots
• Timezone presentation
• Proposed title and agenda
• Invitation details requiring confirmation

Actions and boundaries

Create or send the calendar event only after the user confirms the slot, participants, and invitation content.