Find your fit
Who it is for
A support team handling messages through several inboxes can use Unassigned, Mine and Assigned views to see who owns the next response. Check actual mailbox routing and team access with fictional messages before moving customer traffic.
A business whose customers often ask the same questions can combine a help center with live chat. Trial a small set of articles and one Assistant inbox to make sure chats and contact requests reach the intended team.
The work it supports
Core capabilities
Incoming conversations appear in shared inbox views, while an agent can also create a ticket for a phone call or start a fresh email. The new conversation form includes a sending mailbox, recipients, subject and labels, which help direct follow-up.
The team can mark a conversation Active, Pending or Closed, assign it in the detail view or while replying, and add private notes that customers do not see. Bulk assignment is available from the inbox when several conversations need an owner.
If a customer opens two conversations about the same issue, an agent can merge them into one thread. The merge is permanent, so preview the main thread and participants before confirming it.
Snooze temporarily removes a conversation from the active inbox and returns it at a chosen time. Use a fictional follow-up to check that the return time matches the team’s working hours and escalation routine.
Workflow rules match conditions and perform actions such as tagging, replying or changing status. A rule runs once per conversation; test a small set of representative cases and exceptions before letting automation change live support messages.
ThriveDesk Docs provides customer-facing answers. A Chat Assistant can be linked to an inbox so chats and contact forms enter the team’s queue. Confirm the published article view and where each request arrives after installing the widget.
Understand the offer
Pricing and getting started
The official pricing page advertises Basic, Standard and Unlimited with different teammate and inbox allowances. Its captured static text renders overlapping monthly/yearly cards and inconsistent Basic amounts, so treat any displayed amount as a starting point and confirm the selected term, seats, inboxes and tax at checkout.
The pricing page advertises a seven-day free trial without a credit card. The workflow guide places automation on Standard and Unlimited; check the intended team’s exact plan rights before designing rules around it.
The billing guide defines a User as a teammate with a login, while customers do not need logins. It says prices are displayed in USD and that account-specific plans may differ from documentation, so compare the actual offer for the number of agents and inboxes you expect to use.
Look a little closer
Before you choose
Send a harmless test request into each planned inbox, assign it, add an internal note, reply, change status and snooze it. Check who can see each step and where it reappears before directing real customers to the new address.
For duplicate messages, inspect which thread should be retained before merging; there is no unmerge. For automated routing, use a few fictional subjects and edge cases because a workflow runs only once on each conversation.
Confirm the current plan quote and trial offer in the actual account, including billing cadence, taxes, teammate count, inbox count and Standard/Unlimited workflow rights. The public static pricing text does not establish a single reliable Basic price.
11 distinct sources behind this profile. Research observed Oct 27, 2026. Features and offers can change.
View sources and research →
