Use AI ticket summary and reply suggestions
Generate an assisted summary or draft response while keeping staff responsible for final review.
Feature pathOpen ticket → AI actions
Before you beginThe screen or action may be hidden when your role lacks permission, the related module is inactive, or a required setting has not been configured. Ask an administrator to review access rather than using another person’s account.
What this feature does
Generate an assisted summary or draft response while keeping staff responsible for final review. Britixo CRM keeps the result connected to the relevant customer, staff member and operational history where the feature supports those relationships. That connection is important for search, reporting, client portal visibility and future automation.
Step-by-step workflow
- Start from Open ticket → AI actions and open the relevant record or view.
- Confirm that the record is in the correct status and that you have permission to perform the action.
- Review the related customer, dates, amounts, recipients and attachments before continuing.
- Choose the action described by “Use AI ticket summary and reply suggestions” and complete the displayed options.
- Preview client-facing content or the resulting document where Britixo CRM provides a preview.
- Confirm the action and wait for the success message before leaving the page.
- Check the activity timeline, status, email queue, gateway or generated record to verify the outcome.
Important fields and decisions
DepartmentConfirm this information is accurate and appropriate for the record.
ServiceConfirm this information is accurate and appropriate for the record.
PriorityConfirm this information is accurate and appropriate for the record.
SubjectConfirm this information is accurate and appropriate for the record.
Message and attachmentsConfirm this information is accurate and appropriate for the record.
Checks before completion
- Avoid exposing private notes to the customer.
- Use the correct department and status.
- Review attachments before sending.
- Check whether the result should be visible to a customer contact or only to staff.
- Confirm the final status, activity entry, generated document or notification before leaving the record.
Permission and data safetyDeletion, refunds, signature clearing, module changes, payment configuration and privacy actions can affect linked records or legal history. Use the least destructive action available and follow your organisation’s approval process.
Browse connected topics:paymentcheckapprovalschedulingserviceclient portalnotificationsemailcustomers
Related guides
Was this guide helpful?