Support is rarely one job. It is a queue, a conversation, a written answer, a rule that saves someone an hour and a report that explains the week. Here is each part, and where it lives.
Each one has a page of its own. Start wherever your day starts.
A conversation worth keeping together.
Tickets, customer context and clear ownership in one shared workspace.
Be there at the moment of “how?”
Website conversations with the context to continue beyond the chat.
Your best answer. Ready for the next person.
A searchable help centre and internal knowledge, written by your team.
The routine can look after itself.
Rules, reusable scenarios and execution history for the work between replies.
One team. Plenty of ways to organise it.
Team structure, brands and permissions that fit your support operation.
Know how the work is really going.
Support reports, SLA visibility and customer feedback in one place.
Email, the website chat widget, the customer portal, requests raised by your own team and the API all become tickets in the same queue, with the same ownership and the same service deadlines.
See the channels and integrationsRoles and granular permissions decide which product areas a member reaches and which actions they can take. Two-factor authentication, SAML single sign-on and SCIM provisioning support connected identity management where configured.
Read about security and accessConfigure brand identity, sender details, signatures and portal hosts so each of your brands presents the face your customers recognise, without splitting your team across systems.
Explore workspaces and brandsThe API, webhooks and MCP connections to external AI assistants extend the workspace. Connector scopes narrow an integration’s access to the permissions of its owner.
Explore integrations and AI connectionsThe same workspace, arranged for the shape of your support operation.
Connect your inbound email configuration. Incoming messages become tickets, with the sender linked to a contact. Replies can remain attached to the same conversation.
The widget is designed to be embedded on a website with a script snippet. Your workspace settings provide the configuration for your installation.
Yes. Articles have public or internal visibility. An article appears in the customer help centre only when it is both published and public.
Yes. The rule editor supports a dry run against a ticket. It lets you inspect the evaluation before activating the rule.
No. Brands are customer-facing identities within a workspace. Separate workspaces have their own tenant context; choose the boundary that matches your operation.
Ticket reports generally filter by ticket creation date. A request created in March and resolved in April belongs to the March creation cohort. The Time logged report instead uses the date the time entry was performed.
Give your customers your best.
Give your team a workspace that helps.
helpdash