Skip to content

Quick start checklist

Use this checklist to get a new tenant ready for customers.

Admin dashboard setup checklist in Muninx

Go to Settings and open the Tenant tab. Set a display name customers will recognize.

This name appears in email notifications and in the customer portal. Keep it close to your company, product, or support brand.

Every tenant has a default support@$TENANT_SLUG.muninx.com address. To use an address on your own domain, follow Custom support email and configure both external forwarding and outbound sender verification.

Choose how customers can create tickets by email:

  • Open: anyone can create tickets by email except senders from blocked domains.
  • Restricted: authenticated users and users from allowed domains can create tickets by email.
  • Closed: only authenticated users can create tickets.

Most small teams should start with Restricted unless they intentionally want open inbound support.

Muninx can show replies as the individual agent or as your tenant.

Use Agent identity when customers should see who replied. Use Tenant identity when replies should appear from the support team as a whole.

This only changes the customer-facing author shown in tickets and notification emails. Admins and agents still see which team member wrote each reply.

Auto-solve can solve pending tickets after a configured number of hours and optionally notify participants with a solving message.

When participant email is enabled, the solving message is what gets emailed to ticket participants.

Example solving message email sent when auto-solve notifies participants

Auto-close can close inactive tickets. Closed tickets are permanently locked; customers need to open a new ticket for further help.

Admins manage team members from Team. Add admins or agents, choose whether each is a human agent or AI-assisted agent, and resend activation emails when needed.

Admins also act as agents, so choose an agent type for admins as well.