โ† All modulesยทSTARTER PLAN

Email Hub

Shared mailboxes that turn into tickets โ€” not a second inbox to forget about.

Connect the mailboxes your clients already email. Plenix polls them, threads the conversation, and converts anything that needs work into a ticket with the client already attached. Replies go back out from the same address.

4
Sub-modules
5
Module integrations
22
Features

SUB-MODULES

Everything inside Email Hub.

๐Ÿ“ฎ

Shared Mailboxes

Connect support@, accounts@ or any IMAP mailbox and work it as a team instead of forwarding to each other.

  • โœ“IMAP mailbox connection with credential test before saving
  • โœ“Multiple mailboxes per tenant
  • โœ“Automatic polling โ€” no manual refresh
  • โœ“Threaded conversation view
  • โœ“Assign a thread to a person
  • โœ“Archive without deleting
๐ŸŽซ

Email โ†’ Ticket

One click โ€” or one rule โ€” turns an email thread into a tracked ticket, matched to the right company.

  • โœ“Convert a thread to a ticket with full history attached
  • โœ“Sender matched to an existing company & contact
  • โœ“Attachments carried across to the ticket
  • โœ“Reply to the client from inside the ticket
  • โœ“Threading preserved so replies land back on the ticket
  • โœ“Auto-conversion rules for monitored mailboxes
โœ๏ธ

Templates & Signatures

Consistent outbound email without anyone rewriting the same reply for the fifth time.

  • โœ“Reusable email templates with merge fields
  • โœ“Per-user and per-brand email signatures
  • โœ“Templates for invoices, reminders and invitations
  • โœ“Branded sender name per tenant
  • โœ“Preview before sending
๐Ÿ“ค

Outbound Delivery

Every transactional email the platform sends, from one auditable place.

  • โœ“Transactional sending for invoices, invitations and alerts
  • โœ“Per-tenant sender identity
  • โœ“Delivery logging
  • โœ“Bounce visibility
  • โœ“Unsubscribe handling on marketing sends

REAL-WORLD WORKFLOWS

See it in action.

LIVE FLOW

Client emails โ†’ ticket โ†’ resolved โ†’ invoiced

The most common path in a service business, with nothing typed twice.

1
Email HubEmail arrives

Client emails support@ โ€” poller picks it up and threads it

2
Email HubSender matched

Address matched to an existing company and contact in CRM

3
TicketingConverted to ticket

Thread becomes a ticket with history and attachments attached

4
TicketingWorked and replied

Engineer replies from the ticket โ€” client sees it from support@

5
BillingTime billed

Logged time flows to the next invoice for that company