Each request is saved in Salesforce with its parts and the page and campaign that produced it, so you can show how much pipeline the website creates.
Ready-made connections, scoped before we quote a timeline. Integrations are the real driver of a replatform schedule.
The specific answer, because a page that says "seamless integration" tells an evaluator nothing they can act on.
Object | Direction | Sync | Notes |
|---|---|---|---|
Leads and Contacts | Write | On submit | Created or matched, with source page and campaign attribution. |
Accounts | Read / Write | On submit | Matched against existing accounts before a duplicate is created. |
Opportunities | Write | On qualification | With source page, first-touch offer and detected platform as fields you can report on. |
Opportunity line items | Write | On RFQ submit | The BOM as line items with quantities and attributes. |
Price books | Read | On request | Contract pricing resolved per account where Salesforce holds it. |
Cases | Write | On support request | So a product question raised from a catalog page reaches the right queue with the part attached. |
Field-level mapping is agreed during scoping. Customisation in your instance changes the mapping, not the model.
CPQ deployments are supported. Where CPQ owns quoting, the catalog hands off rather than attempting to price.
Field-level mapping is agreed during scoping. The goal is that a revenue leader can filter won deals by the page where the buyer first arrived, without building a report from scratch.
Present, Partial or Missing, each rating followed by the specific observation behind it. Five business days, and there is no call first.