INC Email Mailbox Folders

Mailbox Folder name1 Description / Task relevance
Inbox (Default)

When a new mail is reaching the inbox, Nimbus creates a Reporting2 Service Session.

☝ Caution: Check your inbox for spam / malware

  • Nimbus can detect automatic replies and will not create extra tasks. Such Emails are moved into the Failed folder.
  • Nimbus cannot detect automatic distribution emails like weekly Microsoft summaries, advertisements, spam. Also, malicious links to external websites may still pass-through.

✅ As Administrator: → Ensure that you check incoming mail for spam and malware before it reaches the Inbox and gets distributed by Nimbus.

 
<Custom Folder> 
(Any name)

Allows subscription of one service per folder. A folder already assigned to another service (via Modalities Service Settings) cannot be selected again.

⮑ A warning “This folder is already assigned to another service” is shown.

✅ Recommended Action - Pre-Sorting: Use Outlook/Exchange rules to pre-sort incoming mail into subfolders, so only mails in folders subscribed by your services turn into a Nimbus task.

 
Handled

The Email is moved here when 

  • The Workflow Activity > “Marked as handled” was used. Ends with Reporting(1) status “Workflow Marked as handled”.
  • A user presses the “Marked as handled” button in the UI.
  • A user accepted the task and successfully “Replied” to the mail.
WF ended Moved here when the “Disconnect” Conversation Handling Activity was used. Applies to either Reporting(1) status: “Workflow Disconnect After Queue” or “Workflow Disconnect”
Failed

The Email is moved here when:

  • A Workflow Activity > “Reply / Mark as handled” ended in a technical error.
  • An Admin kills the task via Operations panel.
  • An automatic reply Email was identified in the “Inbox”.
Exchange Email folders and their relevance to task handling

1  Only Nimbus-managed folders (Handled/Workflow Ended/Failed), and custom subfolders are selectable in Modalities Service Settings; other well-known system folders (Drafts, Sent Items, Junk Email, etc.) are excluded from the picker.
2 🔎See Nimbus Reporting Model  > Static Dimensions > User Session Outcomes / Service Session Outcomes. By checking Historical Sessions or the Nimbus Power BI Template you can see which actor (user/system) lead to the final session outcome.

Table of Contents