Questions, answered without the spin.

Yes. ReTicketDesk is built around Resend inbound and outbound email. If you already receive support mail through Resend, setup is mostly connecting your API key, importing recent received mail, and choosing which addresses should become inbox routes. If you are not on Resend yet, start there first so your domain, DNS, and receiving addresses are ready before you invite the team.

Starter is $15 per month, Team is $35 per month, and Growth is $79 per month. Each plan includes a set number of active teammates, with extras at $3 per teammate per month. That means a small team can add founders, support leads, and part-time helpers without immediately multiplying the bill by every named user the way many per-seat help desks do.

Setup has five concrete steps: create a workspace, connect Resend, let ReTicketDesk discover receiving addresses from existing mail, invite teammates, and send a test message through the queue. The time depends on whether your Resend domain and inbound routing already work. Changing domains, mailbox routing, or internal support processes adds work outside ReTicketDesk.

You can start with messages available through your connected Resend account and new mail that arrives after the webhook is connected. Bulk mbox import is not currently self-service or promised for a particular date. If older history is required, contact us before switching so we can confirm what can be imported and avoid setting the wrong migration expectation.

Test the support path your team will use every week. Connect a real Resend receiving address, send a customer-style message, assign the ticket, add an internal note, save a reply, snooze a follow-up, and send a response through Resend. Also invite one teammate with a non-owner role so you can confirm that setup screens and daily queue access feel right.

Yes. The trial runs for fourteen days with all features unlocked and no credit card required. You keep using your own Resend account the whole time, so you can test real inbound routing, replies, tags, saved replies, and teammate roles before choosing a paid plan.

The API, primary database, and secret storage run in Microsoft Azure North Europe. Provider keys and webhook secrets receive additional application encryption, workspace access is tenant-scoped, and inbound HTML is sanitized before display. Some delivery, authentication, billing, and analytics providers operate outside that region. The public privacy policy, DPA, and security page describe those providers and their roles. ReTicketDesk does not sell or train models on customer conversations.

The product app uses private endpoints today, but public API keys are not available yet. If API access is important for reporting, custom routing, or a migration workflow, contact us with the exact use case. We are prioritizing integrations that help small support teams operate safely without turning the product into a generic automation platform.

Yes. One workspace can have multiple inboxes, each connected to the receiving addresses you choose. Small teams often start with Support and Billing, then add VIP or Partnerships later if those queues need different ownership. Replies still go out through the connected Resend sender, and teammates can filter the ticket list by inbox.

Your tickets, messages, contacts, tags, saved replies, and audit events are stored in workspace-scoped tables. Self-service export is not available, but a verified workspace owner can request export or deletion assistance. The product is intentionally focused, so a team that needs voice, social, live chat, or enterprise workflow automation should expect to move to a broader platform.