Advanced Requires 1.0.5-beta Updated March 2026

Communication Hub and IMAP Sync

Understand how threads, messages, status changes, matching, and inbound email sync work inside the Communication Hub.

The Communication Hub is built around threads and messages. It is not just an inbox skin. It tracks thread status, sender, matching, read state, attachments, and reply-driven action items.

Thread Statuses

  • New Inquiry
  • Needs Reply
  • Waiting on Client
  • Follow Up
  • Closed

How Matching Works

Mankai tries to match communication to a user by email address first. It can also try to match a session based on the attached user and the subject line.

Inbound and Outbound Messages

Each message stores direction, sender, recipient, body HTML, plain text, source, message IDs, references, and optional attachment IDs. Mankai also strips quoted email content so you are not reading the full thread every time.

IMAP Sync and Cron

Mankai schedules communication sync through cron. It registers dedicated communication schedules and runs sync on the configured interval. If cron is not firing, new mail will not appear automatically.

Why Outbound Logging Matters

When Mankai sends outbound email through its event system, it can also log that activity back into the communication thread so the whole conversation stays in one place.

Action Item Integration

New replies can create action items automatically, especially when a client response means you owe them a next step. That reduces the chance of a message sitting in a thread with no operational follow-through.

Best Practices

  • Keep client emails consistent so matching works better.
  • Use clear subject lines for session or project work.
  • Review cron health if replies stop appearing.
  • Do not assume shared hosting email problems are plugin bugs.