> ## Documentation Index > Fetch the complete documentation index at: https://docs.mercora.io/llms.txt > Use this file to discover all available pages before exploring further. # Deal capture > Turn deal recaps and contracts that arrive by email, WhatsApp, Teams or the Copilot into Inbox items you review, then create the contract in Mercora and, if connected, in your CTRM. A **recap** is the short message that confirms the terms of a deal once it is agreed: the buyer and seller, product, quantity, price, delivery period and so on. Deal Capture reads recaps and contract terms wherever they arrive, extracts the terms, and puts each deal in the Inbox for you to review. Nothing enters your book until you review the deal and click **Create contract**. > [!NOTE] > > Available when the **Deal Capture** module is turned on for your workspace. Ask your workspace admin. ## Where deals come from | Source | How it reaches the Inbox | | - | - | | **Email** | Recaps and contracts sent or forwarded to your workspace's email inbox are recognized and captured. See [Email ingestion](https://docs.mercora.io/documents/email-ingestion.md). | | **Copilot on Home** | Paste or forward a recap into the chat, or type **/trade** with it. The deal goes straight into the Inbox. | | **Copilot on WhatsApp** | Forward a recap to Mercora on WhatsApp. The Copilot asks "Should I create a deal out of this?" and captures it after you reply yes (or 👍). | | **Microsoft Teams** | Paste, forward or quote a recap in your chat with Mercora, or ask it to capture one it can find ("capture the recap Kofi sent me"). In channels an admin set to **Deal capture**, posted deals are captured automatically. | A few things are not deals and aren't captured: freight rate quotes and free-time offers (those belong to [Freight rates](https://docs.mercora.io/workflows/freight-rates.md)), futures fills and hedge orders (see [Hedging](https://docs.mercora.io/workflows/hedging.md)). The Copilot captures deals from message text only. For a recap inside a PDF or other file, upload the file instead. See [Uploading documents](https://docs.mercora.io/documents/uploading.md). The same recap handed in twice becomes one Inbox item, not two. ### Capture a deal from the Copilot **1. Paste the recap** On **Home**, paste the recap into the message box. To be explicit, type **/trade** first, or pick it under **Commands** in the / menu. For example: ```text theme={"system"} /trade Recap: Veltana Commodities SA sells to Meridian Foodstuffs 27 MT white refined sugar ICUMSA 45, USD 565/MT CIF Singapore, payment by L/C at sight. ``` **2. Open the Inbox item** The Copilot replies with one line saying the deal is in the Inbox for review, with a link. It doesn't restate the terms or claim a trade exists yet. **3. Review and create** Review the deal in the Inbox, as below. If you give a correction together with your yes on WhatsApp ("yes, but USD 566"), the Copilot doesn't apply it. Make the correction on the Inbox item. ## Review a captured deal Open the item in the **Inbox**. The card shows where the deal came from (for example "WhatsApp · Sam Lee" or "Teams · Kofi Mensah", or the email), and the terms Mercora extracted. **1. Check the source** Read the original message next to the extracted terms. **2. Check the parties** Mercora works out the buyer, the seller and which side is your company. When it fills your side in from who wrote the message, the field says so: "Filled in as your company from who wrote the message — check it". **3. Correct the fields** Fix anything under **Extracted fields**: product, quantity, price basis, unit price, currency, Incoterms, laycan, ports, payment terms, quality and weight terms, and more. For the recap above, check that the quantity reads 27 MT, the price USD 565/MT, the Incoterms CIF Singapore and the payment terms L/C at sight. **4. Create the contract** Click **Create contract**. The line beside the button says exactly what the click creates. What **Create contract** creates in Mercora depends on your workspace's modules: | Your workspace has | The click creates | | - | - | | **Contracts** on | A contract. With **Trades** also on, **Start a new deal with this contract** (on by default) wraps it in a new deal. | | **Trades** on, **Contracts** off | The contract inside a new trade. | See [Contracts](https://docs.mercora.io/records/contracts.md) and [Trades](https://docs.mercora.io/trades/overview.md). To reject a deal, click **Dismiss** in the card's header. Nothing is created. ## Push the deal to your CTRM A **CTRM** (commodity trading and risk management system) is the system many trading firms book their contracts in. If your workspace is connected to Agiblocks and **Deal Capture sync** is on, **Create contract** also creates the contract in Agiblocks. Buttons and messages here name it by its vendor, Agiboo. > [!NOTE] > > Available when **External systems sync** and its **Deal Capture sync** switch are turned on for your workspace. Ask your workspace admin. Your role also needs the **External sync** permission under Deal Capture. When the deal arrives, Mercora checks in the background what Agiblocks will need, without writing anything to it. The card then opens with: * the fields Agiblocks requires flagged on their rows, and **Blocked by:** listing anything still missing; * the counterparty it will select, with a picker if it can't find one; * any similar contracts already in Agiblocks. Then: * **Create contract** creates it in Agiblocks first, then in Mercora: "Creates it in Agiboo, then as a contract in Mercora". If Agiblocks needs anything, nothing is created anywhere, and the card says why. * **Skip Agiboo**, then **Confirm: create without Agiboo**, records the deal in Mercora only. You can push it later with **Sync to Agiboo**, which stamps that same contract instead of creating a second one. * **Already in Agiboo? Link it instead** is for a contract someone already keyed in by hand. Enter its number; Mercora looks it up read-only and refuses one that can't be this deal (the wrong side, another counterparty, already linked to another deal, or cancelled). **Link and create** then records the deal against it without a push. * For a possible duplicate, choose **This is the one** to link it, or **Not a duplicate** to carry on. * If the background check couldn't reach Agiblocks, **Check again** reruns it. It never writes to Agiblocks. The push takes about a minute. You can move on: the item shows **Syncing to Agiboo** in **Waiting** until Agiblocks answers. If it fails, it comes back to **Needs you** with the reason. See [External systems](https://docs.mercora.io/integrations/external-systems.md). ## Who can do what | Permission | What it allows | | - | - | | **Deal Capture** (edit) | Hand deals in from the Copilot, edit the extracted terms and create the contract. | | **External sync** under Deal Capture (edit) | Push the captured contract to the connected CTRM. | Deal Capture access is separate from access to the Contracts book itself. See [Roles and permissions](https://docs.mercora.io/concepts/roles-and-permissions.md). If the **Deal Capture** module is turned off, new deals stop arriving, and items already in the Inbox stay available to finish. ## Next steps > **[Contracts](https://docs.mercora.io/records/contracts.md)** > > Find the contract you just created and pair it into a deal. > **[Trades](https://docs.mercora.io/trades/overview.md)** > > Follow the trade the contract started, through shipping and documents. > **[Walkthrough](https://docs.mercora.io/getting-started/walkthrough.md)** > > See Veltana's sugar trade end to end. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.