Reply
| Description |
A HTML-formatted text box that allows to either reply to the sender and/or all CC-mentioned users. Please Note: This is not a workflow-terminating activity. The workflow should continue afterwards, e.g. with a “Mark as Handled”, “Queue” or “Disconnect” activity for a clear Reporting session result. Note: This activity will NOT inform the user that a reply has been sent. Use it to inform the customer that the mail is being processed in your workflow.
💡 An example reply text could be:
|
||||||
| Required Predecessor | Accept | ||||||
| License |
|
||||||
| Modalities | Audio / Video | Instant Messaging | External Task | ||||
| Configurable Properties | Description |
|---|---|
| Reply Type |
Mirrors the reply option available to users in My Sessions:
|
| Reply Text | A field for reply text in HTML. Supports Custom Parameters and/or System Fields and Parameters. Reply Text - Good to know:Unlike other workflow activities the “Reply Text” box renders HTML text and will try to retain formatting pasted from external sources. 💡Tip: You can use external HTML editors or your mailing software of choice to prepare HTML code to paste into this activity.  The HTML Text box supports:
Unsupported are layout-breaking elements such as:
|
Activity Exits
This activity has two exits that will correspond to folders in the originating Mailboxes:
-
Failed: If the activity failed this indicates underlying problems with the mailbox. The activity itself will be treated as ignored.
✅We recommend to Disconnect after the Failed exit to logically conclude the session. If you are using the Nimbus Power BI Template you can cross-check with the Nimbus Reporting Model > Service Session > “Service session Outcomes” > “Workflow Disconnect” as it could indicate issues on a particular service or mailbox. -
Replied: Exit taken when the mail reply has been successfully sent.
✅We recommend to follow up with “Mark as Handled”, “Queue” or “Disconnect” activity.