Chatra Chat Integration

Summary of what the module offers

Chatra Chat Integration connects a PrestaShop store to an in-page Chatra conversation and adds precise control over placement, audience, shopping context, connection timing and store-specific configuration.

• Chatra service: live and offline conversations, typing insight, visitor information and team tools stay in the Chatra account.
• Audience routing: ordered rules send each language, customer group and shopping context to the appropriate Chatra route.
• Commerce context: selected customer, product, cart and order details accompany the conversation.
• Storefront placement: the whole store, product pages, categories, or cart and checkout form the basic scope, with detailed inclusions and exclusions on top.
• Measured connection: first interaction or a maximum wait starts Chatra once, while mobile visibility remains a separate choice.
• Reliable setup: one Widget ID starts a simple store, and diagnostics plus store-specific settings support a larger operation.

Which shoppers reach which Chatra conversation?

You choose a basic scope: the entire store, product pages only, category pages only, or cart and checkout only. Detailed rules add exact page addresses, selected products and categories, store language, customer group, login status and working hours.

Rules have a visible priority, and the first complete match decides. A signed-in wholesale customer reaches B2B sales, a visitor using the German store reaches the German-speaking team, and an evening question follows the route prepared for offline handling. A default Chatra window covers shoppers who match no special rule.

Each rule selects its own Chatra identity and, where the Chatra plan includes agent groups, the responsible sales or support group. You retain one straightforward setting for a small store and gain precise routing as languages, teams and storefronts grow.

When does Chatra connect, and where does it appear?

The external Chatra connection waits for the shopper's first scroll, click or touch. The delay chosen in the module is the maximum waiting time, so a quiet visit still receives the conversation window. Whichever condition happens first starts the connection once and removes the remaining triggers.

You choose whether Chatra appears on phones independently from the page rules. Turning mobile visibility off stops the connection before the service is contacted on those devices. Page and audience rules apply the same principle to excluded products, categories and parts of the buying path.

Timing, device and scope work together. The first useful shop content appears before the conversation service joins the page, while support is ready at the product or checkout decision where it matters.