Conversation entry points
Use the support inbox and optional live chat experience to give visitors a clear route to an answer, article or human agent.
Configured in workspaceConnected operations
HelSup separates the integration definition from each connection, protects credentials, normalizes events and lets tickets, customers, automation and reports work from the same context.
Different jobs, clear boundaries
Channels carry conversations. Connectors carry business context. Providers supply the external service. Webhooks move signed events between systems.
Use the support inbox and optional live chat experience to give visitors a clear route to an answer, article or human agent.
Configured in workspaceNormalize connected data so agents can see relevant customer and order context without making the ticket service call provider APIs directly.
Adapter-basedSend signed events through a queue with retry handling, delivery logs, sanitized requests and idempotent fingerprints.
HMAC + logsWhat happens after connect
Health is derived from the connection state: connected, warning, error, disabled or not configured. Secrets are never presented through the catalog, and logs retain the operational trail teams need to troubleshoot.
Extend without losing control
Explore the catalog, activate the extensions you need and keep connection health visible to the people responsible for support.
A healthier connection model
Integration value is not only the connection itself. It is the shared context that becomes useful in tickets, customer records, automations, reports and product operations.