Action Patterns in Manitou NEO

This tutorial introduces Manitou NEO's Enhanced Action Patterns, showcasing their powerful new interface and features. It covers three case studies: night-time call management, service ticket creation for Joe's Grocery, and video monitoring for threat assessment. Each case demonstrates how to build, test, and apply action patterns effectively. The tutorial concludes by encouraging users to explore and create their own action patterns.

What is one of the new capabilities of Enhanced Action Patterns in Manitou NEO?

• Ability to send emails

• Use of SQL queries for database testing

• Integration with social media

• Automatic software updates

Where can Action Patterns be found in Manitou NEO?

• Under the Help menu

• In the User Settings

• Within Customer, Dealer, and Monitoring Company records

• In the Reports section

What is the purpose of using Action Pattern categories in Manitou NEO?

• To enhance security

• To organize patterns into logical groups

• To reduce system load

• To improve network speed

In Case 1, what does the customer want during business hours?

• Phone calls

• Text messages

• Emails

• No notifications

What is the first step in creating an action pattern for Case 1?

• Close the alarm

• Contact the keyholder

• Create a general schedule

• Notify the customer

In Case 2, what is the initial action taken by Joe's Grocery?

• Submit a web form

• Call the service company

• Send an email

• Log a manual entry

What happens if the service ticket is not accepted in Case 2?

• The system sends an alert

• The operator waits 5 minutes and tries again

• A new request is submitted immediately

• The alarm is closed

In Case 3, what should operators do if they are unsure about a threat?

• Ignore the video

• Close the alarm

• Dispatch the police

• Review additional video sources

What is the purpose of the prompt in Case 3?

• To log operator actions

• To help operators make decisions

• To notify the customer

• To close the alarm

What is the final step before an action pattern is ready for delivery?

• It must be documented

• It must be approved by management

• It must be tested

• It must be shared with all users