One widget, two very different jobs
Live chat looks like a single feature, but a support team and a sales team are doing almost opposite things with it. Support is reactive, resolution-oriented, and measured on efficiency. Sales is proactive, conversation-oriented, and measured on pipeline. Bolt them onto the same widget without a plan and each degrades the other — a sales pop-up annoys a frustrated support seeker, and a support queue buries a hot lead.
Different goals, different definition of “good”
For support, a good chat is a solved problem in as little time as reasonable. For sales, a good chat is a qualified conversation that moves toward a decision — and spending twenty minutes with a serious prospect is a win, not a cost. If you judge your sales chats by handle time or your support chats by revenue, you will optimize both into mediocrity.
Different triggers
Support chat should be easy to find but rarely pushed — the person already has a problem; do not interrupt them solving it. Sales chat is where proactive invitations earn their keep: a well-timed message on a pricing page or after real engagement can start a conversation that would never have started otherwise. Same proactive engine, opposite restraint.
Different staffing and skills
Support agents need product depth and troubleshooting patience. Sales chatters need product-to-need translation and comfort with a soft close. The overlap is real but the emphasis differs, and pretending one person is equally good at both usually shortchanges whichever they are weaker at. Small teams often have the same humans doing both — that is fine, as long as they know which mode they are in for a given chat.
Run both without confusing either
Route by context so the visitor lands with the right intent: a chat from the docs goes to support, a chat from the pricing page can go to sales. Departments keep the queues and the metrics separate, so support's efficiency numbers and sales's pipeline numbers each stay honest. The visitor never sees the seam — they just get the right kind of help.
How MyLiveChat supports both modes
MyLiveChat's departments and routing let one deployment serve support and sales as distinct lanes, and proactive rules let you push where it helps (sales-intent pages) while staying quiet where it doesn't (someone mid-troubleshoot). You run one widget, two playbooks — without the two stepping on each other.