Skip to main content
Use Send Summary on a company-linked meeting page to compose a follow-up email. You can write it yourself or request an AI draft when AI is available. Audience: MSP staff with meeting write access. Company recipients can understand a meeting summary and ask their MSP for corrections. A visible Send Summary button does not grant permission to generate or send.

​
Open the composer

  1. Open the meeting’s full workspace from Calendar > List View or My Meetings using … > Open Meeting Page.
  2. Check the meeting title and company, then select Send Summary.
  3. Review To, Subject, and Email Content. Opening this standalone page does not generate an AI draft or send an email.
The standalone composer requires a company-linked meeting. If it does not open, check the meeting’s company and your access with an MSP administrator.
The unsent email is not a saved draft. Subject, recipients and editor content remain in the open page only. Cancel, leaving, or reloading can discard them. Save & exit in wrap-up does not save an unsent email. Keep a separate copy if you need to return later.

​
Set recipients and subject

To starts with the meeting participants’ email addresses. Review every address; this is not a client-only recipient list. Assigned staff and company contacts are suggestions, not automatic CC recipients.
  • Type a name or address and choose a suggestion, or enter a complete email address. A valid typed address can also become a recipient when the field loses focus.
  • Use arrow keys to select a suggestion and Enter or Tab to add it. Check that the address appears as a recipient chip before sending.
  • Select CC to reveal the CC field. Remove a chip with its × control. Backspace in an empty recipient field removes its last chip.
  • Hover a named chip to check its email address. Check To and CC for duplicates and unintended recipients.
  • Edit Subject, which initially reads Meeting Summary: [meeting title].
Changing email recipients does not change the meeting’s invitation list. At least one To recipient is required; up to 50 To and 50 CC addresses are accepted. The subject is limited to 500 characters.

​
Write or generate the content

You can type directly in Email Content and use its formatting toolbar. AI is optional. When available, Generate with AI requests a new draft. Choose Length (Brief, Standard or Detailed) and Tone (Friendly, Neutral or Executive) first. The defaults are Standard and Friendly.
Once the editor contains text, the button becomes Regenerate. Regeneration replaces the editor content when it succeeds, including your manual edits. Changing length, tone or recipients does not automatically rewrite an existing draft. Review the greeting again after changing To recipients. The wrap-up’s Summary step can request its initial AI draft automatically when opened. This differs from the standalone composer. Moving backward and forward within that same open wrap-up keeps the mounted email editor; leaving or reloading the page does not preserve it.

​
Understand Based on

After generation, Based on reports which source categories were available: Meeting notes, Agenda, Action items, and Transcript. It describes the draft’s inputs, not independently verified facts or every field in the source records. The draft uses saved public meeting notes, agenda titles/notes with additional budget context, action-item details and available transcript text. Private Notes is not the public meeting-notes source. Do not assume that hidden presentation items are excluded: the summary’s agenda inputs are separate from slide visibility. Long transcripts can be shortened for drafting; Transcript (shortened) identifies that case. Generated transcript notes can be used when transcript text is absent. A missing-source message means little material was available for the draft, not that the meeting had no discussion. Review dates, amounts, recipients, wording and commitments against the actual meeting. Remove internal discussion or details that should not be emailed. Generation does not apply new meeting notes, create action items, or send the draft.

​
Optionally add a public PSA ticket note

When a default PSA is configured, the composer can show Add as note to [provider] ticket. The provider label follows your configured PSA; this workflow supports ConnectWise, Autotask, Halo and Syncro through the ticket-note integration.
  1. Turn on the ticket-note option.
  2. Enter a ticket number or summary in Search Ticket.
  3. Choose the intended ticket and verify its number, title and company.
Ticket-note access is separate from meeting write access. The email can send even if you lack permission to add its ticket note. Searching and selecting do not post a note. The note is attempted after the email is sent. It is a public ticket note, not an internal note; use content suitable for the ticket’s client audience. Provider formatting and notification behavior can differ. Search uses the default PSA, meeting company and your ticket visibility. If no result appears, check those settings and synchronization. An empty result can also reflect a search failure; it does not prove that the ticket does not exist. Turn the option off if you intend to send without a ticket note.

​
Send and check the outcome

Review the final To/CC chips, subject, body and optional selected ticket, then choose Send Email. There is no additional review screen after that button. Wait for the result. The email is sent from your MSPortal account using the tenant’s configured sending identity. Your profile name used in an AI sign-off does not mean the message is sent from your personal mailbox. The composer does not offer delegated Microsoft 365 sending. Sending may mark an existing, non-dismissed wrap-up completed. That update is separate from email delivery. Sending does not mark the meeting itself Completed.

​
Understand QBR follow-up

For eligible company meetings, automatic QBR logging can run after sending when enabled in Calendar settings. It can create/update a company log entry and add new commitments as meeting action items. A configured QBR PSA sync can also update the provider’s company record independently of the optional ticket note. Automatic logging skips technical visits, service calls and internal meetings, and preserves manually edited entries. Email success does not prove that QBR generation, action-item creation or PSA synchronization succeeded. Review the QBR log and meeting action items separately. Wrap-up may open QBR Log after sending; the standalone composer returns to the meeting workspace. A pending QBR indicator does not guarantee an entry will be created.

​
Frequently asked questions

The standalone page does neither. Generate with AI drafts content; Send Email sends it. The wrap-up Summary step can automatically request its initial AI draft.
No. The email editor, recipients and subject are page state. Cancel, leaving or reloading can discard them. Wrap-up Save & exit does not persist the unsent email.
Yes. Write and format Email Content yourself. Sending still requires meeting write access and valid recipients, subject and content.
No. A successful regeneration replaces the editor content. Keep a copy first if you need those edits.
Not automatically. Review and edit the existing greeting, or deliberately regenerate using the new To list.
No. To is prefilled from meeting participant email addresses, which can include staff or other guests. Review each address.
No. It changes the outgoing email’s recipients, not the meeting invitation list.
No. It reports source categories supplied for drafting. Check the resulting facts, dates, amounts and commitments yourself.
Not necessarily. Summary agenda inputs are separate from slide visibility. Review the draft before emailing it.
The transcript exceeded the portion used for drafting. Review the original transcript and add any important missing discussion.
No. This composer sends through the MSPortal account using the tenant’s configured sending identity. An AI sign-off can still use your profile name.
No. The public ticket note is attempted after Send Email succeeds. Searching and selecting alone do not post it.
The integration path supports ConnectWise, Autotask, Halo and Syncro. The composer uses your configured default PSA and your visible tickets.
Do not resend just to retry the note. The email was already sent; verify the ticket and resolve the note separately.
No. It confirms acceptance by the sending service, not delivery to every mailbox or reading by recipients.
No. Meeting status is separate. An existing wrap-up can be marked completed, and eligible QBR follow-up runs separately when enabled.
Do not rely on it as sent-email history. The composer starts with an empty body and default recipients/subject. Keep the actual sent email for reference.