Contents
Opening a ticketSLA times and the working calendarEscalationWorking a ticketParts, labour and invoiceField visit, signature and CAPASupport in the customer portalBoard, knowledge base and reportsOn the phoneService tickets: support requests, SLA and field service
Collects customer faults, complaints, questions and service requests in one place. Every ticket opens with an SLA time counted in working hours; the people responsible are warned when it is close to running out and when it is exceeded. Parts and labour can become a sales invoice, and a complaint a corrective action (CAPA).
Window: Sales / CRM › Service Tickets; the Service tab on the account card; Support in the customer portal. Administrators and CRM users see all tickets; other users see and work only the tickets assigned to them.
Opening a ticket
A ticket is opened from the customer portal (Support › New support request) or manually with + New ticket: customer, optional product, serial number and lot, type, priority, category, subject and description. When a product is chosen, the customer's last sales invoice containing it is found and the warranty status (warranty period on the stock card, otherwise the default in settings) is written to the ticket. The number is SR, year and sequence; a number is never reused.
SLA times and the working calendar
An SLA policy gives response and resolution times by priority and type; a policy for a framework agreement or an account group comes before the general one. Without a policy, default times apply (urgent 1/8, high 4/16, normal 8/40, low 16/80 working hours). Times are counted within working hours; weekends and the public holidays of the country package are skipped. A 24/7 policy has no calendar.
While a ticket is in Waiting for customer reply, the clock stops; the waiting time is added to the resolution target. When the customer replies in the portal, the ticket goes back to In progress by itself.
Escalation
When 80% of the resolution time is used, the assignee gets a system message; when the time is exceeded, the assignee's manager (the effective manager in the organization chart); when it is exceeded by half as much again, the administrators. Each level is written to the ticket only once. The check runs manually with Board › Run SLA check now, or regularly if the server task is on.
Working a ticket
States: new, assigned, in progress, waiting for customer reply, resolved, closed, cancelled. The first reply visible to the customer stops the first response time; an internal note is not shown to the customer. A resolved ticket can be reopened within the period in settings. If two people change the same ticket at once, the second gets a warning and refreshes the screen.
Parts, labour and invoice
Parts and labour lines are chosen from stock and service items; on a ticket under warranty the lines are suggested free of charge. Issue sales invoice writes a normal sales invoice from the lines; stock and account balance follow the invoice's own rules, and a negative stock warning asks for confirmation. One invoice is issued per ticket; if the invoice is deleted, the ticket can be invoiced again.
Field visit, signature and CAPA
Add to route adds the customer visit on the chosen day to the technician's route list (the Route tab of the field page). On the phone, photos and the customer's signature are attached to the ticket as files. On a complaint ticket, Open CAPA opens a corrective action sourced from a customer complaint in the quality module; the ticket and the CAPA are linked both ways.
Support in the customer portal
On the Support page the customer sees their requests, the company's replies and the status; internal notes are not shown. They can reply, close a resolved request or reopen it if the problem persists, and rate the service once from 1 to 5. When the status changes, a portal notification and a message on the customer's chosen channel are sent. Solution articles published to the portal are listed under Common problems.
Board, knowledge base and reports
The board shows open, breached, at-risk and unassigned tickets, SLA compliance, the median first response and resolution times, a category Pareto, technician workload and recurring problems. If many tickets are opened in a short time for the same product or lot, an anomaly appears in the Notification Center. Articles are written to the knowledge base from resolved tickets. Analysis Studio has a Service tickets cube; the Owner Dashboard and Pulse show SLA risk.
On the phone
On the phone, tickets are listed as cards, a ticket opens full screen and all buttons are large touch targets. A new ticket is opened in three steps: customer and product, subject, description.
Related guides
- CRM Module — A Guide from Scratch for SalespeopleThis guide is written for a salesperson who has never used a CRM. The goal is not to make you memorise buttons but to explain why it works this way.
- My Sales Cockpit: the salesperson’s single daily screenThe cockpit gathers the six things a salesperson should check at the start of the day in one window: this month’s target and actual sales.
- Sales Counter: price, delivery, credit and approval on one screenWhen a customer asks “how much, when, can you deliver?” , answer without opening a document. The counter shows the price engine’s price and its reason.
- Customer Briefing: one paragraph before the visitCustomer Briefing gathers an account’s purchases over the last 12 months, payment habits, recent contacts and key contacts into one rule-based paragraph.
- Product learning cards and quick reviewEach product gets a learning card so that a new salesperson can get to know the range quickly: photo, the product in one sentence, where and how it is used.
- Portfolio handover: a salesperson’s customers, their history and bulk handoverWhen a salesperson leaves or a new one joins, customers changing hands means lost knowledge. The Portfolio Handover window gathers a salesperson’s customers.