Quotes
A quote is a priced proposal for one customer that becomes a subscription once the customer agrees. This page shows how quotes and quote versions work. It also shows how to build a quote in Desk until you publish it.
Quoting is available on our Growth and Enterprise tiers. If you do not have this enabled in your tenant, reach out to your account executive.
How quotes work
You configure a quote in the same way as a subscription. It has one or more schedules. Each schedule has a pricing plan version, start and end dates, discounts, commitments and, if necessary, custom pricing. A quote also has an owner (a user of your platform, usually the sales rep), content for the customer, notes and attachments.

Each quote has one or more quote versions. A version is a complete proposal with its own subscription of type QUOTE, which holds the schedules and terms you offer. That subscription never bills. When the customer accepts, you convert the version into a new subscription of type BILLING, which does. See Share, accept and convert a quote.
To change a subscription that is already running, create an upgrade quote. It goes through the same versions, approvals and acceptance, and credits the unused part of the current period when it starts.
To create a schedule on a quote version, you need QUOTE_PRICING_PLAN_SCHEDULE.CREATE, not PRICING_PLAN_SCHEDULE.CREATE. A sales representative thus needs only the quote permission, and not the broader permission that controls changes to live subscriptions. The API accepts a new schedule only while the quote version is DRAFT. For a quote version in another status, it returns a validation error on quote_version_id. To change agreed terms, create a new quote version.
The custom fields set on a quote version carry over to the next version created from it, so a link a CRM establishes through a custom field, an opportunity ID in particular, survives a quote being rejected or returned to draft and continued as a new version. See the Salesforce quotes integration.
Quote version statuses
A quote version starts in DRAFT. The quote’s own status follows its versions.
A quote version has no expired status. If you set an expiry date, the status does not change on that date. After that date, Solvimon refuses every action on the version: edit, finalize, accept, reject, sign and convert.
Creating a quote
Set up the prerequisites
Before you create a quote, make sure your platform has:
- Billing entity details.
- The customer you want to quote. A draft customer is sufficient. Desk activates the customer when you convert the quote.
- An address with a country on the customer, so Solvimon can calculate tax for the invoice preview.
- Default subscription settings in the Settings menu (optional).
Configure the terms
Set the subscription terms. If you configured default subscription settings, they appear pre-filled.
If your team sends similar quotes repeatedly, select a quote template to pre-fill the pricing plan, subscription terms, content and attachments.

Click Continue to quote.
Build the pricing
Add schedules on the timeline. Each schedule has a pricing plan version with start and end dates. It can also have discounts, commitments or pricing of its own. Add more schedules for a ramp-up. Desk saves schedule changes automatically. Save changes saves the content and signers that you edited.
Add content, notes and attachments
Write the text the customer sees in the content editor. Open the ⋯ menu to Add note or Add attachment. The customer can view and download attachments from the quote page in the portal.
To collect a signature later, add signers to the version: an existing contact of the customer, or a name and email address.
Check the invoice preview
The side panel previews the first invoice: amount before tax, tax and total. Click Show full preview for the invoice lines. Without a customer address the panel shows “Cannot determine tax engine without customer address.” with a link to update it.
Finalize and publish
Click Finalize and publish. In the dialog, optionally set Quote version expires at, then confirm with Finalize and publish.
The version moves to FINAL, or to WAITING_APPROVAL if an approval policy applies. After that, you cannot edit its schedules and terms. To change the offer, create a new version.
Quote a ramp through the API
A ramp is one agreement sold in steps: year one discounted, the years after at list price. In Desk you add a schedule per step on the timeline, as above. Through the API, POST /v1/quotes/init takes the whole ramp in one call, as pricing_plan_schedules on the subscription:
Each entry is a full schedule with its own plan version, billing period and pricing currency, so a step can change more than the price.
Only the last step is measured against the subscription’s initial_term: an intermediate step is expected to end early, because the next one takes over at that moment. Editing a step afterwards with PATCH /v1/pricing-plan-schedules/{id} re-checks the term only when start_at or end_at change, so changing a step’s pricing cannot trip it.
Validation errors name the step by its index, as pricing_plan_schedules[1].start_at. The singular pricing_plan_schedule still works for a single-step quote and keeps the field paths it has always had. An AI client builds the same thing through the MCP server, with a slightly different request shape: see Ramps.
Next, share the quote and record the customer’s decision: Share, accept and convert a quote.