Skip to main content
The first onboarding step asks what you want RAUM to run for your organization.

​
Product choices

Zendesk AI Assistant

Use RAUM inside Zendesk for agent assistance and automated ticket handling. This path includes Zendesk authorization, trigger setup, the Zendesk Marketplace app, and optional Brand Voice analysis.

RAUM Chat

Add a customer-facing AI widget to your website. This path does not require Zendesk.

Both channels

Enable AI Assistant and AI Chatbot in one organization. The bundled offer is shown with its current discount in the onboarding UI.

​
How the choice changes onboarding

Chatbot configuration happens after signup because the web channel, allowed origins, widget appearance, and installation snippet belong to the authenticated Chatbot workspace rather than the public registration form.

​
Plan availability and pricing

RAUM does not hardcode purchasability in the onboarding page. The website requests the current offer catalog from the backend and uses the returned availability for each product and tier. This matters because:
  • self-serve availability can change without shipping a new website;
  • pricing and allowances can be updated centrally; and
  • the signup API verifies that the chosen offer is actually available before creating the account.
Use the pricing shown on the live RAUM website as the current source for prices, included usage, overage rates, billing periods, and plan availability.

​
Enterprise

Enterprise is sales-led rather than part of the normal self-serve registration path. If an Enterprise option is appropriate for your organization, use the contact path shown on the RAUM website rather than attempting to complete a standard self-serve signup.

​
Can I change products later?

Your initial selection determines the products provisioned for the new organization. Product and subscription changes are managed after signup from the RAUM account and subscription controls.
If you want both Zendesk and a website widget, select Both channels during signup. It keeps the initial organization and knowledge configuration together instead of making you treat the two products as unrelated installations.