Create and verify a support department
Create a Pixie CRM support department with live clicks. Set its name and client visibility, save it and reopen the department to verify the retained settings.
Customer work, connected.
Support
Customers need to know that someone has understood their request. A support team needs the context to act without repeatedly asking for it. Pixie CRM support desk connects tickets with customer information, helping departments share a readable history and keep the next action clear.
Keep the customer context, responsible person and next step together. Start with a familiar task, agree the information the team needs and check the result with the people who will use it.
Learn with Pixie CRM
Follow real application screens at your own pace, with English captions and a matching written guide.
Create a Pixie CRM support department with live clicks. Set its name and client visibility, save it and reopen the department to verify the retained settings.
Create a Pixie CRM ticket service with live clicks. Enter its label, save the new option and reopen the Edit form to verify that the name is retained.
Create a Pixie CRM ticket priority with live clicks. Enter its label, save the new option and reopen the Edit form to verify that the name is retained.
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.
Create a Pixie CRM knowledge-base group with live clicks. Set its name, colour, description and order, save it and reopen the group to verify the retained settings.
Create an internal Pixie CRM knowledge-base article with live clicks. Set its title and group, choose Internal Article, write the guidance and verify the saved audience and content.
Recorded in a demonstration workspace; available options depend on your plan and permissions.
Visit the Pixie CRM YouTube channel
Define the types of request each department handles and how new tickets reach the right team. Use priorities that reflect impact and urgency, with a clear route for correcting a mistaken classification. Capture a useful subject, the customer's description and the information needed to investigate. Where email piping is configured, check how replies are associated with the existing ticket so the conversation stays together.
A ticket status should explain whether someone is working, waiting for information or reviewing a resolution. Record ownership when work changes hands and distinguish internal notes from customer-visible replies. Predefined responses can save time, but they still need to answer the specific question. Review aged and unassigned requests alongside response measures. Do not promise a service level through the website unless it is part of the actual support agreement and operating process.
Useful answers
Practical details for a better informed conversation.
Email piping is a listed support capability. It needs the appropriate mailbox and routing configuration, including checks that replies join the correct ticket and attachments are handled safely.
Departments and ticket queues are part of the offering. Agree ownership, escalation and visibility rules so a handover does not leave the customer waiting between teams.
Continue exploring
Your workflow is a good place to start
Bring your current tools, your priorities and the handovers you want to improve. We’ll help you define a useful next step.
Verify your email. Send your enquiry.
Keep your ticket reference.
Explore the tasks behind Support Desk. Check the guide against your enabled modules and role, then confirm the result in your workspace.