Escalation in customer service: when, to whom, how fast
How to decide when a ticket moves on, who takes it and what must go with it, and what Swedish law requires when you say no to a consumer's claim.
Articles on knowledge bases, AI in customer service, self-service and measurement. Written for people who run customer service, e-commerce or operations, with sources and without the sales pitch.
Subscribe via RSSHow to decide when a ticket moves on, who takes it and what must go with it, and what Swedish law requires when you say no to a consumer's claim.
A customer portal shows the customer's own tickets, orders and invoices behind a login. What to include, how to log customers in and when it pays off.
Most customers try to solve the question themselves, but few succeed. How to place, search and measure the help centre so self-service takes tickets.
How to set up chat in customer service: which questions it suits, what customers think of chatbots, what the AI Act requires and how to staff it.
A factual comparison of Supportifier and Gorgias for online stores: AI answers, per-ticket pricing, integrations, data storage and onboarding.
When you switch customer service system, tickets, customer records and the knowledge base are moved, pruned or deleted. How to do it right under GDPR.
E-commerce support is about orders, delivery, returns and payment. What customers expect in 2026, which questions take the time and how to answer them.
Many outsource the switchboard because calls are too many. How to count the calls that never needed making, what the law requires and when to outsource.
A buyer's guide to ticketing systems for customer service: core functions, what knowledge base and AI change, integrations, data rules and how to choose.
Access, erasure and rectification often arrive as ordinary emails. How to recognise a request, meet the deadline and decide when you are allowed to say no.
Black Friday falls on 27 November. How to train seasonal staff in two weeks: what they need on day one, which tickets to keep from them, what to measure.
Most ticket categories describe the organisation, not the customer's question. How to build a taxonomy that shows what to fix, and keep it clean over time.
Three years to complain, two years of reversed burden of proof and the order of remedies. How customer service answers complaints under Swedish law.
Customers expect answers in their own language. How to choose languages, build the knowledge base once, review translations and measure per language.
How to calculate customer service staffing per hour and channel: inflow, handling time, queue mathematics for phone and chat, email throughput, shrinkage.
Humany is now ACE Knowledge. What Telia's announced deal with LeadDesk may mean, how it differs from Supportifier and how to switch without losing answers.
A factual comparison of Supportifier and Zendesk: knowledge base, AI answers, pricing model, data storage and onboarding. How a small team chooses.
How to calculate AI in customer service: cost per ticket, where the saving is, which costs get forgotten and what to promise management. With an example.
Since June 2025 e-commerce and customer service must be accessible to all. How to know if you are covered, what chat and help centre must handle.
When AI answers from the knowledge base, someone has to own it. What the knowledge manager does: tasks, time, who fits and how the effect is measured.
A template for help articles that resolve the ticket: one question per article, the answer first, steps, exceptions and plain language. How to test it.
How to choose between in-house, outsourced and hybrid customer service: what you hand over, what it costs, how AI changes the maths and the contract.
CSAT measures the ticket, NPS the brand and CES how easy it was. How to choose a metric by the decision it drives, avoid survey fatigue and read results.
Order status questions fill the e-commerce inbox. How to answer before the customer asks, what applies when deliveries are late and how self-service helps.
Since 19 June 2026 Swedish online stores must offer a withdrawal function. What it means for customer service: new questions and what to tell customers.
How to prepare customer service for Black Week and Christmas from September: the answers that must exist, staffing by the hour and what to measure after.
Write help articles that Google and AI assistants find and cite: one question per article, the answer first, structured data, a sitemap and update dates.
The difference between a chatbot that answers from your knowledge base and one that guesses, what hallucinations cost and what to ask the vendor.
Legal basis, data processing agreements, EU storage and the AI Act's transparency rules for chatbots. What must be in place before AI reads your tickets.
Why reviewed AI drafts beat full automation at the start: trust, a knowledge base that gets trained, and the measures that show when a flow is ready.
How to choose channels in customer service: which questions customers solve alone, when they want a person, what a ticket costs per channel.
Seven customer service metrics with definition, method, common mistake and action: response time, resolution time, resolution rate, CSAT and self-service.
How to find knowledge gaps in ticket history, search logs, the chatbot's unanswered questions and agents' replies, and turn them into articles.
Minutes in chat, same day by email, within a day on social media: what customers expect in 2026, and why resolution matters more than a fast first reply.
A knowledge base is reviewed answers with owners, versions and permissions shared by every channel. How it differs from an FAQ, and how to build one.