Transport
Modules and context.To the right destination.
Psssst connects a site and its services: delivering module configuration, carrying events and preserving connection context.
From task to outcome
A working connectionneeds a clear route.
Configuration travels to the website, events travel from it, and permitted context reaches the connected module. Domain, launcher and scope keep that exchange within its proper boundaries.
How it works
- To the site
- The launcher receives and caches configuration, then passes it to the appropriate SDKs and modules.
- From the site
- Signals reach the analytics layer with the visitor, session and source connection attached.
- Between participants
- Permitted information lets modules continue the same interaction while retaining their own product responsibilities.
In practice
A form and a chat can participate in the same visit. Shared context links their actions; the individual scenarios and interfaces remain with the products responsible for them.
Boundaries and context
Transport owns the technical connection. Conversation content, CRM decisions and automation belong to the products that use the delivered context.
In brief
Does Psssst run the chat scenario?
It delivers configuration and context. WiHooks and Commy Me define chat behavior.
Can every module access everything?
Only the permitted information within the corresponding connection scope should be passed on.
Where do we start?
Start with your task, data sources and expected result. Then we can agree on configuration and connection.
Start with your task.
Tell us what your website or product needs. Together we can define the right connection.
Discuss a connection