Guides

Done for you

Don't want to build the agent yourself? Describe your business and what the agent should do, and volai's founder builds it by hand for a fixed catalog price - ready within 24 business hours of payment.

What Done for you is

Done for you is a one-time paid service: start an order (in the portal at /done-for-you, over REST POST /v1/setup-orders, or the MCP tool create_setup_order), describe your business and what the agent should do in one message, and get a fixed-price quote right away. The price always comes from a catalog in code (packages, add-ons, an hourly rate for extra work) - the model only picks items from the conversation, it never invents or adjusts a price.

After payment, volai's founder builds the agent by hand - this is not an automated template. A phone number, system prompt, knowledge from your website and price list, transfer to a colleague and structured call data are part of every package.

A shorter overview for ads (without the API and MCP detail) is on the Receptionist done for you page.

Who it's for

Done for you fits when you don't want to configure the agent yourself in the editor, or you want a second phone number, multiple agents, or a calendar or invoicing connection and don't want to wire it up by hand.

How the conversation works

The model may ask at most five follow-up questions before it must produce a quote - an order started over REST or MCP (create_setup_order) is one-shot from the start: the first message must contain everything relevant, the model never asks a follow-up, and anything unclear becomes an assumption in the quote (selection.assumptions) instead of a question. In the portal the model may ask follow-up questions until it reaches that cap.

While the order is waiting for payment (status quoted or awaiting_confirmation), another message REPLACES the quote with a new one - the same one-shot rule applies to it too. Once the customer opens checkout, the quote freezes for 24 hours and rejects a further message with the checkout_open error, so they never pay the old price for a changed scope.

An item outside the catalog (customItems) is priced in half-hour increments at the hourly rate; once custom items add up to more than the threshold below, the quote waits for the founder to confirm it (awaiting_confirmation) - the price is provisional until confirmed.

Pricing

The catalog in code is the single source of prices - the quote, the invoice and this page all show the same numbers.

Packages (one-time setup)

Add-ons

Work outside the catalog

Anything outside the packages and add-ons (an unusual integration, a longer change) is priced in half-hour increments at the hourly rate; past this threshold total, the quote waits for the founder to confirm it before it can be paid. (1,490.00 CZK / hour, threshold 4 hours)

The quote also shows an estimated monthly running cost (number, call minutes, agent) from the same calculator as /pricing - that is not part of the setup price, it is billed from credit as the agent is actually used.

The revision rounds included in the package (Business 2, Company 3) count from the `ready` status, not from the start of the build. A round beyond that costs 490.00 CZK and is deducted from credit once the founder finishes it (`revision -> ready`) - not when the message is sent.

What gets paid, and when

One payment covers the setup price AND a first credit top-up (choose an amount of 200, 500, 1000 or 2000 CZK) - credit then pays for the agent's actual running cost like on any account. Checkout is opened and paid by a HUMAN; nothing is charged automatically from MCP or REST - the tools only return a Stripe Checkout link.

After payment you get a tax document for the setup fee (and for the credit top-up), the same as with a card top-up - in /credit or through list_billing_documents/get_billing_document.

Timeline and guarantee

Ready within 24 business hours of payment - hours falling on Saturday or Sunday don't count toward the deadline. The Express add-on shortens this to 4 hours.

Order statuses

An order moves through fixed allowed transitions - both the customer and the founder can only take a limited set of steps (POST /v1/setup-orders/{id}/launch and .../cancel, or the Launch and Cancel order buttons in the portal).

Cancelling it yourself (cancel_setup_order/POST .../cancel) only works on an UNPAID order (draft, quoted, awaiting_confirmation or declined) - a paid order can only be cancelled by the founder.

What you do yourself

A few steps always stay with the customer, because no one else can do them on their account with the carrier:

1. Forwarding an existing number to the new agent number with your own carrier (you get a guide with the finished agent), or simply using the new number as is.
2. Connecting a Google or Apple Calendar with one click, if you ordered the calendar booking add-on.
3. A test call to the finished agent before launching it (launch_setup_order) - launching is the customer's own confirmation, it is never done automatically on their behalf.

REST and MCP

Seven endpoints under /v1/setup-orders (create, list, detail, message, checkout, launch, cancel) and the same seven MCP tools (create_setup_order, list_setup_orders, get_setup_order, message_setup_order, checkout_setup_order, launch_setup_order, cancel_setup_order) call the same service layer - same rules, same prices, same statuses.

The full reference with the errors for each endpoint is in the Setup orders section of the REST API reference.

Each MCP tool's description is in the Done for you area on the MCP server page.