Configuration Lifecycle

1. Anonymous website visitors land on a product configuration page and view the default product configuration.

2. Anonymous visitor interacts with the product configuration resulting in an anonymous web lead with a fingerprint tracking ID recorded on CRM records. A clone of the template is created. The platform event CONFIGURATION_START is raised, which can be used to trigger other flow actions.

3. Anonymous visitor further interacts and personalized the product. Each interaction triggers a CONFIGURATION_UPDATE platform event. Flow builder actions may respond with dynamic pricing or options based on customer selections.

4. The visitor selects “Request Quote” and provides contact information. The anonymous website visitor lead is converted to a pre-qualified Lead with contact details and lookup reference to their specific product configuration. A CONFIGURATION_SUBMIT platform event is raised to optionally apply territory rules and notify an internal representative to follow-up.

5. An internal MDR, SDR, or Sales Rep converts the Lead to an Opportunity and generates a quote from the customer self-service configuration. The Contact is invited to review and eSign the quote, agreement, or order.

6. The customer reviews the quote and suggests any further changes, either using the product configurator or directly messaging the Sales Rep in the quote room.

The customer eSigns the quote, raising the DOCUMENT_ESIGNED event.

7. The Opportunity is moved to Closed-Won. Order fulfillment and ERP integration processes are triggered.

Next: View the configuration API and SDK.