Cloud
weclapp
v1 and v2 both have /quotation. v2 adds POST accept, a new version, and linking a quotation to an opportunity. The read is the status and the link. Accept is the seller's click.
CRM quote questions: which quote is open, and who may not accept it.
CRM quote questions stop at status. weclapp documents a call that accepts a quotation, and that call is not a tool. Sage CRM lists quotes and orders as entities. Sugar can create records with the same token that reads them. Pexon reads the open quote and leaves accept and order with the seller.
A CRM quote question is allowed when all three are true
- The object exists on this release. weclapp has /quotation. Sage lists Quotes. A CAS or cobra database might not. Absence is an answer.
- The caller is the seller, not an admin token. Sage still applies territory. A weclapp administrator token sees every customer.
- Accept, send and order are not in the tool list. weclapp documents accept as its own POST. Reading status does not require it.
Three products that actually name a quote
Status, version, and the click that accepts
ERP side
Sage CRM
The 2024 R2 guide lists Quotes and Orders as primary entities, next to Opportunity. Each request carries that user's password, and territory still limits the rows. Creating an order is out.
Suite
SugarCRM
The REST API that reads an Account can create one. Quotes are a module on the same pattern. The refresh token is how we avoid posting the password again. Create stays off.
A deal amount is not a quotation
HubSpot, Salesforce and Pipedrive will answer which deal is open and what it is worth. That number is the opportunity. A quotation is a document with lines, a date and a status, and on weclapp it can be versioned and linked back to the opportunity. An agent that reports the deal value as the quote total has merged two records the CRM kept apart.
CAS and cobra are in the same shortlist and are not in this paragraph as quote systems. CAS exposes types per database, and opportunities are a module. cobra exposes the tables an administrator turned into endpoints. Until that installation shows a quote table, the honest tool list does not have a quote line.
Read the quote, leave the signature
01
Find the document
Quotation id, customer, status, date. On weclapp v2, also whether an opportunity is linked.
02
Say which version
v2 can create a new version of a quotation. The agent names the version it read. It does not create the next one.
- status
- version
- customer
03
Stop before accept
Accept, price recalculation, purchase-order request and the order itself are documented writes. They are not tools.
Use cases
Which CRM quote question is a read
| Question | System | Agent |
|---|---|---|
| Which quotations for this customer are still open? | weclapp | GET /quotation. Not accept |
| Is a quotation linked to this opportunity? | weclapp v2 | Read the link. Do not create it |
| What is the status of this quote? | Sage CRM | GET Quote, inside that user's territory |
| What is the deal worth? | HubSpot, Salesforce, Pipedrive | That is the opportunity, and this page says so |
| Accept it and make the order | weclapp, Sage | No tool |
weclapp changelog and Sage 2024 R2 developer guide, read 6 October 2026.
The call that is refused
weclapp publishes the accept action. Publishing it is why it is named in the deny line, not why it is built.
allow: quotation_status, linked_opportunity
deny: accept_quotation, create_order, send_quote
source: weclapp | sage | sugarOn a CRM with no quote object the allow line stays empty. HubSpot deal value is not a substitute.
One suite
weclapp is also the ERP. A quote question that turns into a stock question has left the CRM. Say so, and keep the warehouse on a different tool list.
weclapp connectorWhen the quote should stay a PDF
If the seller already opens the quotation, checks the lines and accepts it in weclapp or Sage, an agent in front of that button is a second click with a worse audit. Build the read when someone is copying the status into a forecast. The map of all ten systems is the CRM MCP server. The deal questions, which are not quotes, are the sales questions.
The quote has a deal, and the deal has a system
- weclapp — open quotations, accept left out
- Sage CRM — quotes inside the user's territory
- Sales questions — open deals and owners, which are not quote totals
What finance and sales will both ask
Which CRMs in this set actually have a quote object?
weclapp documents /quotation on v1 and v2, including an accept action on v2. Sage CRM 2024 R2 lists Quotes and Orders among its primary entities. Sugar's REST guide covers record CRUD, and quotes are a standard module. The others in the ten are opportunity or deal systems first. We do not invent a quote endpoint for CAS or cobra.
Can the agent accept the quote if I say so in the chat?
The APIs can. weclapp documents POST /quotation/id/{id}/accept. That is the line we leave out. A person accepts in weclapp, where the price and the version are visible. The agent may say the status. It may not change it.
Is a quote the same as an opportunity?
No. An opportunity is the deal. A quotation is a priced document, sometimes versioned. weclapp can link a quotation to an opportunity. Reading the link is useful. Treating the deal amount as the quote total is how two numbers get presented as one.
What does it cost to check one quote flow?
A two-week Readiness Blueprint at €4,900 net, on the CRM you already run. We confirm whether a quote read exists on that release and whether accept is a separate call. A pilot after that is usually from €15,000.
Next step
Name the quote someone copies into a mail every week
Two weeks. We look at whether that status is a documented read, and whether accept is a separate call we will not add.