The following is a list of pills available for engagement configuration:
DESIGN
| Message tone | Define the tone used for messages (Humourous, Friendly, Serious). |
| Schedule Resolution | Work with users to schedule automations to resolve the issue. |
| Reminder | Configure how often users get reminders. |
| Triage (Yes/No) | Ask users a Yes/No question and launch automations based on responses |
| Custom Message | Write a custom message which can include links and/or images. |
| Additional Context | Provide Ampy with additional prompting information and/or instructions. Especially powerful when used with custom findings. |
| Instructions | Provide AI generated instructions to fix the issue. |
| Launch Action | Immediately launch an automation before user engagement occurs. This could be used to start a ticket or even launch containment steps |
| Delay Engagement | Delay engagement for a certain amount of time. This is good for enforcing SLAs. |
| Action Button | Create Buttons for the end user and tie automations with them. This is useful when there are multiple remediation paths. |
ESCALATE
| Resolution Deadline | Define a Deadline. |
| Resolution Expiry Action | Run a automaion when the deadline expires. |
| Escalate to New Channel | Escalate to a new channel. For example, if the engagement is in Slack you can escalate it to email. |
| Redirect Engagement | Redirect messages from the user to another channel or user. |
CONCLUDE
| Mark Complete | Provide a button for users to mark when an action is completed. This puts the findings into a "Pending Verification" status. Once the finding is confirmed, it will be closed. |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article