Channels
Same ticket. Different doors.
Widget, form, email, and Slack are channels on one conversation. Your team does not copy threads between tools. Slack is on Growth and Scale.
Email in
Customers write to your-slug@inbound.xupport.io. Put #123 in the subject to stay on that ticket. If the subject has no number, we match an open email ticket from the same sender, or we open a new one.
Mail is received through Resend on inbound.xupport.io. MX for that domain is already ours. You do not point your company MX at us unless you want every mailbox on that domain in Xupport — you usually do not. Give customers the slug address, or forward a dedicated mailbox to it.
Email out
Agent replies on email and form tickets, when the ticket has a customer email and the reply is not an internal note, can go back out through Resend. From-name is your workspace name. Subject is Re: … #N. Widget and Slack stay in-product.
Public form
/contact/your-slug → a ticket with channel form. Same thread rules as email for outbound mail.
Slack
Slack is on Growth, Scale, and Enterprise. In Settings, Add to Slack installs the Xupport bot into your Slack workspace. That does not mix tickets: each Xupport workspace stores its own bot token and one channel ID. Saving a channel moves it off any other Xupport workspace. A message or thread reply in that channel is the ticket (channel=slack) and is stored as the customer, not as your inbox agent.