> ## Documentation Index > Fetch the complete documentation index at: https://docs.meetdarwin.ai/llms.txt > Use this file to discover all available pages before exploring further. # Outcomes: quote requests and qualifying forms > Agent Studio → Outcomes: build a form the agent opens in the chat, like Request a quote, Request a callback or fit questions before the calendar. Answers come to you by email, Zapier, webhook or API.
Find it in Darwin Agent Studio → Outcomes Open this screen ↗
An outcome is a short form your agent opens in the chat when a visitor wants it: a quote request, a callback, or a few questions before they book. The visitor answers one question at a time without leaving the chat, and the answers come to you. Booking a meeting is built in, and you can give it questions of its own. Other outcomes add the things a visitor can get done, and can end in a meeting too. Open **Agent Studio → Outcomes**. **Book a meeting** comes first, then your forms, each with how many visitors started and sent it in the last 30 days. Use a form's switch (2) to take it live or off. Under **Start from a template**, pick the closest one (1): * **Request a quote**: what they need, when, any details, then their email. * **Request a callback**: the topic, a good time to call, and a phone number. * **Start from scratch**: your own questions. The Outcomes tab: Book a meeting (built in, 4 questions first, 4 started, 3 fit, 1 not a fit), Request a quote with its Live switch marked 2, and the three templates with Request a quote marked 1. At the top of the form, type its name. **Offer it when the visitor…** tells the agent when to open it, in your own words, such as "asks what a job would cost or wants an estimate". **Their button** is the button visitors see above the message box when the agent offers the form. Turn on **Also at the top of the chat** to put that button under your agent's name, in place of Book a meeting. One form at a time can have that spot. The top of the Request a quote form: its name and Live switch, the Offer it when the visitor sentence, Their button set to Get a quote, and the Also at the top of the chat switch. Each question shows the way the visitor will see it. Select one to edit it: write the question, then pick its type (1): **Short**, **Long**, **Choice**, **Multiple**, **Number**, **Phone**, **Date** or **Yes / no**. Select **Done** to close it. A form can have up to seven questions; add one from the **Add a question** row, and use the arrows to reorder. Two switches on each question: * **Required**: the visitor has to answer it. * **Agent can fill it in from the chat** (2): if the visitor already said it ("I need a quote for a kitchen refit"), the agent fills it in and the step shows as already answered. The visitor can go back and change it. A question open for editing, When do you want it done?, with the eight answer types marked 1, three choices each with a Not a fit flag, and the Required and Agent can fill it in from the chat switches, the second marked 2. Fit rules decide who goes on to book: * On a **Choice**, **Multiple** or **Yes / no** question, select **Not a fit** beside the answers that rule a visitor out. Any one of them makes the visitor not a fit. * On a **Number** question, fill in **Fits between** with the lowest and highest that fit. Leave a side empty for no limit. At least one answer has to be a fit. A question with a fit rule is always required, so it can't be skipped. **Name and email** is always the last step, so every request reaches you with a way to reply. Choose **No phone**, **Phone optional** or **Phone required**. The last step, Name and email, always last, with the phone choice marked: No phone, Phone optional and Phone required. Under **After the form**, pick one: * **Show a message** thanks the visitor with your **Thank-you message**, such as "We'll send your quote within one business day." * **Book a meeting** (marked) goes on to booking once the form is sent: your Book a meeting questions if you set some, then the calendar, under your **Above the calendar** message. Tick **Visitors can send the request without booking** if a booking is welcome but not needed. When a question has a fit rule, **If they're not a fit** sets the message a visitor sees instead of the calendar. Their request still comes to you, marked **Not a fit**. After the form: Show a message selected, Book a meeting marked, and the Thank-you message field. Turn on the switch at the top to make the form **Live**, then select **Save changes** in the bar at the bottom, the same bar as the rest of Agent Studio. **Discard** puts back what was saved. A form that's off is saved but never shown to visitors. The bar at the bottom of Agent Studio: Unsaved changes, Discard, and Save changes marked. The form works in the preview right away. Ask the agent for a quote, or whatever the form is for, and it opens there. ## Ask questions before any meeting To qualify visitors before they book, select **Book a meeting** at the top of the list and add questions. Suggestions such as **Team size** and **Budget** add a ready-made question in one tap. Mark the answers that rule a visitor out with **Not a fit** (marked), then select **Save changes**. From then on, every meeting request opens these questions first, whether the visitor asks the agent, uses the **Book a meeting** button at the top of the chat, or comes from a form that ends in a meeting. Visitors who fit go on to the calendar. Visitors who don't see your not-a-fit message, their answers still come to you, and they aren't offered a meeting again in that chat. Remove every question to send visitors straight to the calendar again. Book a meeting, built in, set to Questions first: How big is your team? with five choices and Just me flagged Not a fit (marked). ## What visitors see When a visitor asks for what the form is for, the agent says a line and opens the form in the chat. One question shows at a time and answered steps fold into a line above it; **Back** changes an answer. Name and email come last, and **Send request** sends it. They then see your message, or, if the form ends in a meeting, your Book a meeting questions and the calendar. The Request a quote form in the website chat on step 2 of 4: the first answer, Brand refresh, folded into a line, then When do you want it done? with three choices and a Back link. To open a form from your own page, make a [chat button](/assistant/chat-buttons) with **Open a form**. A click opens the chat straight into the form. ## Where requests go Every sent request is saved with its conversation, and goes wherever you set it up. **Send answers to**, at the bottom of each form, shows what's connected and links to each. Send answers to: Email (on, your team, with sales@evolve.example added), Zapier (not connected, Connect Zapier) and Webhook or API (not set up, Set up a webhook). | Where | How to set it up | | - | - | | **Conversations** | Nothing to set up. The conversation shows a badge with the form's name and, on the right, the answers, the contact, whether they fit, and the billing state. **Meetings → Requests** lists every request, with search. | | **Email** | Everyone on your team with **Bookings and requests** turned on in [Notifications](/account/notifications) gets an email with the answers. Under **Also send to**, add up to five more addresses, such as sales@ or a shared inbox. | | **Zapier** | The **New Outcome Request** trigger gives each answer its own field, for HubSpot, Salesforce, a sheet or Slack. See [Connect Zapier](/integrations/zapier). | | **Webhook or API** | The `outcome.submitted` [webhook event](/api-reference/webhooks), and the `/v1/outcomes` and `/v1/outcome_requests` endpoints. AI assistants connected through the [MCP server](/api-reference/mcp) can read requests with `list_outcome_requests`. | The panel beside a conversation in Conversations: Request a quote, Sent, with each question and answer, the visitor's name and email, when it was sent and the billing line. ## How requests are billed A sent request counts like a booked meeting: it uses an included booking first, then your plan's rate. See [Plans and usage](/account/plans). A request isn't billed when: * it was sent from the Agent Studio preview, * the visitor wasn't a fit, * the same email sent the same form in the last 30 days, or * a meeting was booked in the same conversation. One conversation is charged once, and the meeting counts instead. A request counts three days after it's sent; the panel shows the date, for example **Included · counts Oct 16**. Until then, select **Not a real request** in the panel to take it off your bill. ## Good to know * A workspace can have up to 10 outcomes. Each form has up to seven questions, plus name and email. * Turning a form off stops the agent offering it. **Remove**, at the top of the form, removes it; requests already sent stay in Conversations and Meetings → Requests. * The agent opens one form at a time, and never asks a form's questions in plain messages. Open a form straight from a button on your page. Send each request's answers to your CRM or a sheet. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.