Skip to main content

Generate ticket, submission, and email summaries

Condense long conversations and submissions into useful context you can review and refresh.

Written by Geoff Mina

Assistant summaries help you understand a long record before you act. In supported tickets, form submissions, and email conversations, the summary focuses on useful context rather than forcing you to reread every message or answer.

Generate a summary

  1. Open the ticket, submission, or email conversation you want to understand.

  2. Open its summary area. In a ticket, select the Summary tab; in a submission or email conversation, use the available Assistant summary action.

  3. Select Generate summary when no summary exists, or Regenerate to replace an existing one.

  4. Read the result alongside the source record before deciding what to do next.

The Summary tab of a Moxie ticket with the Ticket summary heading and the Generate summary action

A ticket summary draws on the ticket details, conversation, submitted answers, and time worked. The original record remains available for verification.

What to look for

  • The request, problem, or goal expressed by the client.

  • Important decisions, dates, constraints, or unanswered questions.

  • The current state of the conversation and a likely next action.

  • Patterns across a longer set of submitted answers.

Refresh when the source changes

A summary reflects the information available when it was generated. If new replies, answers, or material changes arrive, use the regenerate or refresh action when it is available. Always use the original conversation or submission as the source of truth.

A summary is not an action

Generating a summary does not reply to the client, change a ticket, or update the submission. It gives you a faster way to understand the record before you take the normal action in Moxie.


Continue exploring Moxie Assistant

Did this answer your question?