IRM365

View saved version →

---
name: daily-briefing
description: Build a morning briefing from IRM365. Use when the user asks what's on today, what they should work on, for a daily or morning summary, or what they missed.
---

# Daily briefing

1. Call `get_workspace_context` for the person and their timezone.
2. Call `list_followups` with `window: "overdue"`, then with `window: "today"`. Page through results while `has_more` is true, up to 100 follow-ups each.
3. Call `search_leads` with `priority: "hot"` and pick out leads whose `last_contacted_at` is more than three days ago, or empty.
4. If opportunities are shared, call `search_opportunities` with `closing_before` set to seven days from today.

Write the briefing in this order, using short lists:

- **Overdue**: follow-up, lead reference and name, how late it is. Oldest first.
- **Today**: follow-ups in time order, with the time in the user's timezone.
- **Hot leads going cold**: each with the days since last contact.
- **Closing this week**: opportunity, stage, expected value in AED, close date.

End with the three actions that matter most today, one line each. Leave out an empty section rather than writing "none". Never invent phone numbers, emails or notes; the connection does not share the phone and email fields.

View saved version →

---
name: get-started
description: Introduce the IRM365 connection. Use when the user has just connected IRM365, asks what IRM365 can do here, or asks which company or data the connection can see.
---

# Get started with IRM365

1. Call `get_workspace_context` first. It returns the company, the signed-in person, their timezone and the data areas this connection may read.
2. Tell the user, in two or three sentences:
   - which company and person the connection acts for;
   - which areas are shared (leads and follow-ups, opportunities, activity notes);
   - that the connection is read-only and does not share the phone and email fields (free-text notes may still contain whatever people typed).
3. Offer three things they can ask next, picked from the shared areas. For example:
   - "What follow-ups do I have today?"
   - "Show my hot leads that haven't been contacted this week."
   - "Which opportunities should close this month?"

Use the timezone from `get_workspace_context` for every date you mention. If an area the user asks about isn't shared, say so and tell them their company admin or the IRM365 consent screen controls it. Don't guess at data you couldn't read.

View saved version →

---
name: pipeline-review
description: Review the IRM365 sales pipeline. Use when the user asks about their pipeline, forecast, deals or opportunities closing soon, stalled deals, or expected revenue.
---

# Pipeline review

## Decide the scope first

- **Open deals only.** The open stages are `discovery`, `viewing`, `proposal`, `negotiation` and `commitment`. Won, lost and cancelled deals are closed. Never count them in pipeline totals.
- **Period.** If the user named one ("this month", "this quarter"), work out its last day in the user's timezone (from `get_workspace_context`) and pass it as `closing_before`. If they named none, review all open deals and say so.

## Fetch

1. Call `search_opportunities` once for each open stage, using `status`, plus `closing_before` when there is a period.
2. Page through each call while `has_more` is true, up to 200 opportunities in total.
3. If you stop with `has_more` still true, the totals are **partial**. Say so plainly at the top of the answer, with how many deals were read. Never present partial totals as the pipeline.
4. For a deal that looks stalled, call `get_opportunity` for its detail. Stalled means its close date has passed, or it has no next follow-up.

## Report

- **Totals by stage:** for each open stage, the count and expected value in AED, plus a probability-weighted total (expected value × win probability).
- **Closing soon:** deals due in the next 30 days, or within the period, soonest first, with owner and probability.
- **At risk:** deals past their close date and deals without a next follow-up, each with one suggested next step.

Show amounts as AED with thousands separators. Say that the figures cover only the opportunities this person can see in IRM365, which may not be the whole company. Don't round probabilities into certainty, and don't forecast beyond what the data shows.

View saved version →

---
name: team-followups
description: Check a team's follow-up discipline in IRM365. Use when a manager asks who in their team is behind, who has overdue follow-ups, how their agents are doing, or for a team activity summary.
---

# Team follow-ups

## Decide the period first

Use the period the user named. Otherwise use the **last 7 days**, ending now, in the user's timezone (from `get_workspace_context`). State the period in the answer.

## Fetch

1. Call `list_my_team`. If it returns an error because the person has no employee record, or the team is only themselves, explain that a team view needs a reporting line in IRM365, and offer their own follow-ups instead.
2. Call `list_followups` with `window: "overdue"` and page through every result.
3. Call `list_activities` with `status: "completed"`. Results come newest first. Keep paging while `has_more` is true **and** the last row's `completed_at` is still inside the period, up to 400 rows. Count only rows whose `completed_at` falls inside the period.

## Report

Group by team member, using `performed_by` and the lead owner:

| Team member | Overdue follow-ups | Oldest overdue | Completed in the period |
|---|---|---|---|

Under the table, name the two or three people with the most overdue work and their oldest items, by lead reference.

**Evidence rule:** say someone completed nothing in the period only if you read every completed activity back to the start of the period. If you stopped at the row limit first, say the counts are incomplete and how far back they reach, and don't call anyone inactive.

Keep it factual and neutral. This is for coaching, so describe the numbers and don't judge the person. If activity notes aren't shared, judge by counts and outcomes only, and don't claim what was said on a call.