> 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/user-guide/insert-records-secondary-actions.md).

# Insert Records / Secondary Actions

The Insert Records section contains supported actions for creating CRM records from the Co-Pilot panel. Click the plus/minus control to expand or collapse the section.

<figure><img src="https://794987320-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MCRVg-TYx3gVa2Tqtf_%2Fuploads%2Fz0aOhgmDgwSM3ERgxA1S%2Fimage.png?alt=media&amp;token=f07fc138-6386-4d53-bf59-06694333793f" alt=""><figcaption></figcaption></figure>

### Actions shown in the screenshot

·         Create Case

·         Create Person

·         Create Communication

·         Create Opportunity

·         Open the Co-Pilot panel on the relevant CRM record.

·         Go to Quick Actions.

·         Expand Insert Records.

·         Select the required action, such as Create Case or Create Opportunity.

·         Complete the fields or information requested by Co-Pilot.

·         Submit the action and verify that the record has been created successfully in Sage CRM.

| Note: Only actions configured and permitted in your Sage CRM environment will be available. The exact fields shown during record creation may vary by configuration. |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

&#x20;

## History

The History tab is used to review previous Co-Pilot conversations. It helps users return to earlier chats instead of starting the same request again.

·         Click History in the Co-Pilot header.

·         Review the available previous conversations.

·         Select a conversation to reopen or review it.

·         Use the previous conversation as context when continuing your work.

| Tip: If a previous conversation is no longer relevant, start a new chat so that the new request is handled independently. |
| ------------------------------------------------------------------------------------------------------------------------- |
