> For the complete documentation index, see [llms.txt](https://docs.corpdev.ai/corpdev.ai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.corpdev.ai/corpdev.ai-docs/record-conversations-and-decisions.md).

# Record conversations and decisions

**Activity** is a timeline of relationship information: notes, calls, meetings, email and other supported entry types. Use it to connect what happened with the deal decisions that follow.

## Log an entry

1. Confirm the workspace and open **Activity**, or open activity from the relevant company.
2. Choose the appropriate entry type in the compose control.
3. Record what happened, including the date, participants, decision and next step where relevant.
4. Save the entry and check that it appears in the intended timeline.

Use the type filters and **Period** control to find entries. The count shown for loaded entries is not necessarily a count of all historical activity. Open an entry to review or work with its content.

## Capture email and meetings

Select **Capture email & meetings** where available and use a connected account. Company activity can offer capture scoped to that company. Check the domain, source account and capture scope before importing information.

Captured information becomes workspace content. It can include correspondence or excerpts from a personal account connection. Review the [sharing implications](https://docs.corpdev.ai/corpdev.ai-docs/sharing-and-data-handling) before capture, particularly when a workspace includes external participants.

Capture is bounded by provider access and the time range or result limits of the feature. It should not be treated as a complete mailbox archive or proof that every conversation has been collected. A connected account alone is not proof of a successful capture.

## Create a deal summary

Choose **Create deal summary**, then select the relevant entries. The current selection flow supports up to 30 source entries. Choose **Write summary** or **Draft with AI**, as offered.

Review the resulting summary against the source conversations. Keep decisions, reported facts and suggested next steps distinct. If an important conversation is absent, capture or log it first rather than letting the summary imply it was considered.

## Missing or duplicate information

Check the current company, workspace, type filter and period. If capture reports an integration error, repair the connection before retrying. Inspect existing entries before repeating an import so you do not mistake a second capture for new relationship activity.

Activity is a working record, not proof that a calendar invitation was delivered or a message sent. Verify those outcomes in the relevant provider or delivery record.