--- url: https://docs.codefox.ai/apps/across-the-apps/enquiry-to-signed-agreement.md --- # Turn a website enquiry into a signed agreement This tutorial follows one enquiry from your website to a signed agreement: a visitor fills in a Pampas form, the response becomes a lead in Fennec, the opportunity's agreement goes out for signature from Corsac, and the signed copy comes back to the deal in Fennec and is filed in Library. Each part says what to set up once, and what happens on its own after that. ## Before you start The four apps must be on the same server and connected to each other. When they were installed together, the installer connected them. When one was added later, the Owner selects **Connect the products** on Foxden Admin's **Server** › **Products** page. The section **How your products work together** on that page shows the three links this tutorial uses, and whether each one works: | Link on the Products page | What it does here | |---|---| | **Website leads** | Pampas sends a form's responses to Fennec as leads. | | **Signatures from a deal** | Fennec drafts agreements in Corsac, and every view and signature comes back to the deal. | | **Signed documents in the Library** | Corsac files the signed PDF in Library. | You also need: * An email sender, set by the Owner on **Server** › **Connections**. Without one, Corsac sends no invitations, and you send each signer their link yourself. See [Set up email](/self-host/email). * A Corsac template for each kind of agreement you send, such as an NDA. Make the document in Corsac, use **Save as template**, and share the template with members (**Share with members**), so Fennec may use it. * Someone who can manage Fennec, to choose those templates in Fennec once (step 3). ## 1. Send the form's responses to Fennec In Pampas: 1. Open **Settings** and find **Fennec pairing**. When the products are connected, it reads **By this server**, and there is nothing to do. If it asks for a **Base URL**, connect the products in Admin first. 2. Open your form, then **Destinations**. 3. Select **Add destination**, then **Fennec**. 4. Map your form's questions to the lead's fields: at least the person's **Email**, and their name and company if you ask for them. Answers you do not map are added to the lead's message. 5. Select **Create destination**. 6. On the new destination, select **Send test**. Pampas sends Fennec a lead made of sample answers and shows Fennec's answer. The test lead appears in Fennec's **Leads** like any other. Every response needs an email address to become a lead: either the answer you mapped to **Email**, or the address the respondent proved with a code. Publish the form and share it as you usually do; see [Pampas](/apps/pampas/). ## 2. A visitor fills in the form When someone submits the form, Pampas sends the response to Fennec. Fennec then: * finds the person by their email address, or makes a new contact, and opens a lead in **Leads**, with the form it came from at the top of its message; * if that person already has an open lead, adds the message to it as **New inbound message** instead of opening a second one; * runs your team's routing rules, which can give the lead an owner; * adds a task to reply to the lead within one business day, unless your team changed that, and alerts the team as your alert settings say. The visitor's side is in [Fill in a form](/apps/pampas/fill-in-a-form). ## 3. Choose the agreement's template in Fennec (once) Someone who can manage Fennec does this once for the whole team: 1. In Fennec, open **Settings** › **Options**. 2. Under **Agreements drawn at the stage**, choose the Corsac template for each kind of agreement. A new Fennec has two kinds, NDA and SOW. A kind with no template is never drawn. 3. Choose which Fennec fact fills each box of the template, such as the company and the signer's name and email. Boxes you leave as **Left for the signer** are filled in by the signer. 4. If the template has a place for your own company to sign, set who signs on **Settings** › **Workspace**, under **Signs contracts as**. 5. Save. ## 4. Qualify the lead 1. In Fennec, open the lead from **Leads**. 2. Once you know the enquiry is worth pursuing, select **Convert to Opportunity**. The lead becomes an opportunity on your pipeline. Your Fennec may call leads and opportunities by other names: the team can rename both. ## 5. Prepare the agreement On a new Fennec, opening an opportunity at **Qualified** drafts its NDA in Corsac by itself, and moving it to **Proposal** drafts its SOW. Fennec gives you a task when a draft is ready to check. 1. Open the opportunity and find its **Agreements** card. 2. If no draft is there yet, select **Prepare the NDA** (or the kind you need). Fennec drafts it in Corsac from the template and fills the boxes from the opportunity. 3. Check the purpose or scope line. To change it, select **Edit** and type the line. 4. If you changed it, select **Redraw with this line**. 5. To see the whole document, select **Open in Corsac**. Nothing is sent yet: a draft goes out only when a person sends it. ## 6. Send it for signature 1. On the **Agreements** card, select **Send**. 2. Confirm. The agreement can no longer be edited, and its status changes to **Out for signature**. Corsac emails every signer their invitation. If email is not set up, Fennec says so: select **Copy signing link** and send the link to the signer yourself. The signer's side is in [Sign a document](/apps/corsac/sign-a-document). ## 7. The signed copy comes back When the last signer signs, Corsac seals the PDF and adds a trusted timestamp a moment later. Then, with no step from you: * In Fennec, the agreement shows **Signed**, and the opportunity's timeline records the signature for each contact who signed, with the signed PDF. Fennec opens the PDF from Corsac when you open it, so it always shows Corsac's final, timestamped copy. * For a closing agreement (the SOW on a new Fennec), Fennec marks the opportunity as signed and proposes moving it to **Won**. A person confirms or dismisses that: a signature never moves the opportunity by itself. * In Library, the signed PDF is filed in the **Corsac** space, in the folder **Signed documents**, with a note that links back to the document in Corsac. People who can manage Library can read it there. Anyone can check that the PDF is the one that was signed; see [Verify a signed document](/apps/corsac/verify-a-document). ## What is filed, and what is not * Corsac files a signed document in Library according to the filing choice in the Library section of Corsac's **Signing** settings page. A new Corsac files **Documents made for a room or a deal**, which includes every agreement Fennec drafts. A document a person made directly in Corsac is filed only when the setting is **Every signed document**. Someone who can manage Corsac changes it. * A **Private** document, and a practice document, never leave Corsac: they are not filed in Library and not shown in Fennec. * Fennec hears of a document only when it drafted it, or when the document is shared with members. ## Troubleshooting ### Fennec is greyed out under Add destination Pampas is not paired with Fennec, and the menu says **Pair Fennec in Settings first**. Ask the Owner to select **Connect the products** on Admin's **Products** page, then reload the form's **Destinations**. ### A response did not become a lead 1. On the form's **Destinations**, check the Fennec destination's deliveries in Pampas. 2. Check that the response had an email address: a response with none is never sent. 3. Fennec accepts each response first and reads it a moment later, so a delivery Pampas shows as delivered can still fail inside Fennec. Someone who can manage Fennec sees each delivery, and the reason one failed, on **Settings** › **Webhooks**, under **Recent deliveries**. ### The Agreements card is missing, or has no Prepare button Fennec is not linked to Corsac, or the kind of agreement has no template. Check **Signatures from a deal** on Admin's **Products** page, then the templates on Fennec's **Settings** › **Options**. A draft Corsac could not make shows **Could not be prepared**, with a task to draw it up by hand; select **Prepare again** once the template is fixed. ### Fennec says Corsac sends no mail Email is not set up on the server, so nobody was emailed. Copy each signer's link from the agreement and send it yourself, and ask the Owner to set the email sender on **Server** › **Connections**. ### The signed copy is not in Library Check, in this order: **Signed documents in the Library** works on Admin's **Products** page; Corsac's filing setting is not **None**; the document is not **Private**. A copy filed in Library is readable only by people who can manage Library.