Customer support vs. customer service

Customer support is reactive and specific. Something is broken, confusing, or not doing what the customer expected, and the support team helps them fix it. The work has a clear beginning and a clear end, which is why it can be measured per interaction: first response time, resolution time, whether it took one exchange or five, and how the customer rated that exchange.

Customer service is the wider umbrella. It covers pre-purchase questions, onboarding, billing and invoices, returns and refunds, cancellations, and the general treatment a customer gets across the whole relationship, not just the moments when something breaks. Much of it has no ticket attached and no end state to close.

A quick test that settles most arguments about which is which: if the customer would not have written to you had the product worked as expected, it is support. If they would have written anyway, because they wanted to buy more, pay differently, or leave, it is service. "My export keeps failing" is support. "Can I switch to annual billing" is service. Both arrive in the same inbox.

For a team of two to ten people where everyone answers customers, the distinction is mostly academic, and you should not reorganize around it. The same three people handle the failed export and the billing change, often in the same thread, and splitting the queue into a support queue and a service queue at that size creates handoffs that cost more than they save. What you have is one inbox and one set of humans.

Where the distinction does earn its keep at your size is in three concrete decisions. First, metrics ownership: first response time and CSAT are support metrics that your team controls, while NPS and churn are service and relationship metrics that move on price, product, and reliability too, so holding two people accountable for NPS is unfair and unhelpful. Second, hiring: a job posting for a support person who will debug API errors attracts different applicants than one for a service person who will handle refunds and renewals, and mixing the two descriptions gets you neither. Third, tooling: support work wants conversation history, searchable past answers, and speed, while service work often wants your billing system and CRM open in the next tab.

The vocabulary is not standardized across the industry, so do not read too much into a job title. Many companies use customer service for everything, particularly in retail and ecommerce. Software companies lean toward customer support for the break-fix work and customer success for the proactive, account-growth side. All three sometimes sit under the same manager. When a vendor or a competitor says one word rather than the other, they are usually signaling which type of customer they sell to, not describing a different activity.

AcornReply is built for the support half of that job: one shared inbox for the email, contact form, and chat that come in, conversation history per customer, and AI drafts written from your help center and your own past replies so a reply takes a minute rather than ten. It does not touch billing, renewals, or account management, so the service-side work still happens in whatever tool owns your subscriptions. In practice most small teams run both out of the same inbox and only notice the difference when they report on it.