Commercial proposals
Prepare a proposal using the customer brief and current prices.
- Proposals are rebuilt each time and may contain old prices or incorrect customer details.
Example paths: the agreed action or human review. This diagram does not run on your live data.
- 01Input: Brief · prices · template.
- 02The brief is matched to services and approved prices; the template receives scope, prices and terms for a manager to review before sending.
- 03Output to verify: Draft for manager.
- 04Unknown items, missing prices and non-standard terms are flagged for the manager.
- ✓The draft uses approved prices, customer details and scope; sending requires manager approval.
- ✓We check repeated processing and connection failures using agreed examples.
An illustration of the logic, not a customer case. Connections and results are agreed before implementation.
What inputs do we need?
We need an example of “Brief · prices · template”, processing rules and an owner for “Draft for manager”. Access is requested after connections are agreed.
What happens if data is missing or an error occurs?
We check “Prices current?”. Unknown items, missing prices and non-standard terms are flagged for the manager.
How is the result accepted?
The draft uses approved prices, customer details and scope; sending requires manager approval.
How long does implementation take?
Scope, price and timing are defined after checking systems, access and exceptions. This page describes a possible workflow, not a ready connection to your data.
Other automations
Customer follow-up
Follow up on open enquiries and commitments on time.
View details →OPERATIONSVoice receptionist
Answer calls, clarify the request and route the caller.
View details →OPERATIONSCustomer support
Handle requests, answer from approved knowledge and escalate complex cases.
View details →