> For the complete documentation index, see [llms.txt](https://docs.greytrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.greytrix.com/sage-crm-add-ons/gumu-co-pilot-for-sage-crm/installation-+-setup/important-configuration-guidelines.md). # Important Configuration Guidelines Please follow the guidelines below when creating actions, capabilities, and prompts. #### 6.1 Use Lowercase Object Names The **Object/Entity Name must always be entered in lowercase**. For example: **Correct:** ``` vcustomersaleshistory ``` **Incorrect:** ``` vCustomerSalesHistory ``` #### 6.2 Use Lowercase Field Names All field names specified in the **Input** and **Output** sections must be entered in lowercase and should match the field names exposed by the Sage CRM XML/Web Services response. For example: ``` chis_compid ``` ``` chis_name ``` ``` chis_date ``` Do not change the field names to mixed-case or uppercase. #### 6.3 Action Name and Script Name Must Match The action name and the corresponding script/function name must be identical. For example: ``` Action Name: vcustomersaleshistory ``` and ``` async def vcustomersaleshistory(...) ``` Both names must match exactly. #### 6.4 Configure Appropriate Prompts Prompts should be added to the actions to help the GUMU™ Co-Pilot Agent understand **when and how the corresponding action should be used**. For example, if an action retrieves customer aging information, an appropriate prompt could be: **Show customer aging data for the specified customer.** This helps the Agent identify the appropriate action when the user asks for customer-specific aging information.