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.
Ways to work
A customer who asks for help should not have to reconstruct the whole relationship for every colleague. Pixie CRM connects support requests to customer context and gives service teams a structured place to manage the next action. Department queues, knowledge articles and reusable replies support a consistent response without removing individual judgement.
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
Agree how requests enter the team, how they are categorised and what makes an issue urgent. Assign ownership and record the information needed for the next action. A request awaiting a customer reply should be distinguishable from one awaiting internal investigation. When a ticket moves between teams, include the work already completed and the question still unresolved. Clear handovers matter more than simply changing the assigned name.
Review recurring issues and decide whether an article, clearer onboarding or a product change would reduce confusion. Predefined replies can provide a useful starting point, but staff should check that the wording fits the actual request. Use reporting to examine queue age, unresolved work and reasons for reopening, with definitions the team understands. Keep internal investigation notes separate from information suitable for the customer portal.
Useful answers
Practical details for a better informed conversation.
Department-based handling can be scoped around your service structure. Define the categories, access boundaries and transfer rules, then test a request that needs more than one team's involvement.
Customer-facing communication and internal working information need separate visibility rules. Review portal access, attachments and ticket updates during configuration so staff understand what the customer can see.
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.