Testing Prebuilt

Testing the prebuilt features

Adding Record in CRM

We can perform a test run on prebuilt modules after installing them to understand their functionality. Records can be added both manually and automatically through workflows and connectors. To test the modules, we can start by manually adding records along with checking the required fields and validations.

If modifications are needed in the CRM, we can use the module builder to make necessary changes, such as adding, deleting, or editing fields, as well as implementing field validations or adjusting field settings, changing the role wise permissions. After making these changes, it’s crucial to ensure that the fields display and function correctly. We can test the associated records and modules with 360 view of each record also. Additionally, we can test the Filter View and Kanban View by adding sample test data into the modules. This approach will help us confirm that the different views operate as expected and provide an accurate representation of the records.

Testing Chatbots

We can test each flow to understand its functionality at every stage. For Chatbots, we can utilize the Test Flow feature or adding contacts to the Chatbot. By executing these tests, we gain insights into how the Chatbot will interact with customers and how it captures user responses and adding, updating in CRM. This process also helps us verify how the chatbot updates CRM fields using the data lookup feature, ensuring that the information flows correctly into the system.

Testing Workflows

For workflows, we can test them by creating trigger events within the linked CRM module to see how the workflow executes each step, performing actions such as updating or adding data in the CRM, enrolling contacts into Chatbots, adding tasks, triggering funnels, and more. Alternatively, instead of creating real-time triggers in the CRM, we can use the Test Flow feature, which allows us to directly add the record ID into the workflow. This approach helps simulate the workflow actions, making it easier to observe how the processes will behave without needing live data.

Testing Funnels

For funnels also we can test by adding Funnels manually against the record or by triggering the Workflows which is adding the record to Funnel or by adding the Record ID in to the Test Funnel feature as same as in the workflow.

Testing Connectors

For testing Connectors, you can use the Simulate Test feature to manually trigger the Connector or set it to trigger automatically with Schedulers. Before initiating the Connector, ensure that the CRM modules have sample data, and that this data matches the filter conditions.

For example, if you are testing a Meeting Reminder Connector, you would need to add a meeting record in the Meeting Module with a valid scheduled date. Additionally, set the Meeting Status to "Scheduled - New," as it is used in the filters. Make sure that a lead is added as a lookup to the meeting record. When the Connector is triggered, it will search for records in the Meeting Module based on the filters applied (e.g., checking if the scheduled date matches). If a match is found, the Connector will pull the lead details from the associated record and send a reminder message to the lead’s phone number.

In this case, data from two modules - Meeting and Leads are essential for the Connector’s proper functioning. Therefore, always ensure the necessary data is available and meets the conditions when executing the Connector.