How-to guide

Use predefined ticket replies

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Follow this guide to create reusable response content and insert it into ticket replies.

Audience: Support leadFeature: TicketPermission-aware

Plain textJump to steps

Learn with Pixie CRM

Watch this workflow

Follow real application screens at your own pace, with English captions and a matching written guide.

All video tutorials

1:46 English captions

Create and verify a predefined support reply

Create a Pixie CRM predefined support reply with live clicks. Enter its name and message, save the reusable text and reopen it to verify the retained wording.

Chapters & transcript Watch on YouTube

Recorded in a demonstration workspace; available options depend on your plan and permissions.
Visit the Pixie CRM YouTube channel

Where to goSetup → Support → Predefined Replies

Before you startThe 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 guide helps you do

Create reusable response content and insert it into ticket replies. Pixie 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.

Follow these steps

Start from Setup → Support → Predefined Replies and open the relevant record or view.
Verify that the record is in the correct status and that you have permission to perform the action.
Check the related customer, dates, amounts, recipients and attachments before continuing.
Select the action described by “Use predefined ticket replies” and complete the displayed options.
Preview client-facing content or the resulting document where Pixie CRM provides a preview.
Verify 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.

Settings to check

Customer contact or emailCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.

DepartmentCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.

ServiceCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.

PriorityCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.

SubjectCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.

Message and attachmentsCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.

Checks before you finish

Avoid exposing private notes to the customer.
Use the correct department and status.
Check 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:payment check approval service client portal notifications email customers leads

Was this guide useful?Your response is stored only in this browser.