LiveChat Integration

Summary of what the module offers

LiveChat Integration adds an in-page LiveChat conversation window to a PrestaShop store and gives the merchant precise control over placement, customer-data handoff and selection of the right LiveChat group.

One License ID starts the normal path, while the same configuration grows into exact visibility, schedule, appearance, language and context rules.

• Store control: broad page scopes, exact inclusions, office hours and phone visibility determine where the conversation entry appears.
• Module value: shop settings connect LiveChat with customer identity, commerce context and group selection.
• LiveChat service: the shopper stays on the current page while a real person answers from the LiveChat workspace.
• Timing and appearance: interaction-first loading, a maximum wait, product-page entry and visual settings shape the storefront experience.
• Conversation context: the viewed product, cart, order and delivery facts reach the selected team under merchant control.
• Setup and health: connection validation, readiness states and repair tools sit beside the everyday settings.

What does LiveChat give the sales and support team?

In August 2026, LiveChat's official partner site reports more than 37,000 customers. The service offers a 14-day trial without a card, and its Starter plan begins at $19 per person each month when billed annually. That plan includes tracking for up to 100 visitors, 60 days of conversation history and one user; higher plans expand visitor limits, history, campaigns, customization and reporting.

LiveChat shows customer details such as name, email, location and the page currently being viewed. Its workspace holds active and queued conversations, archives, reusable replies and shared files, and the team works in a browser, on desktop or on a phone. The conversation window opens over the current shop page, so the shopper remains beside the product or checkout while the team answers. The module supplies the controlled shop entry and context for that service workflow.

Which team receives each conversation, and with what context?

For a signed-in customer, the module sends LiveChat the name and email address together with the viewed product, cart lines and total, relevant orders, delivery state and direct shop links for the agent. Guests remain without account identity. Independent switches keep the merchant in charge of identity and commerce-data handoff.

Priority rules send each conversation to a LiveChat group according to store context. Store language, customer type, login state, page, product, cart and office hours select the group, and an unavailable group leads to the next matching route or the default group. LiveChat remains the owner of agents, availability and conversation history; the module supplies the store facts and predictable destination.