Customers
The website writes into Salesforce, and Salesforce answers back.
Salesforce usually knows the outcome of an enquiry and nothing about how it began. Siteleon closes that gap. It writes enquiries in as Leads carrying the page, the service and the source that produced them, and reads Opportunities back, so you can see which content generates pipeline and which generates noise. Your administrator controls every field it is allowed to touch.
What connects
You connect one Salesforce org through an authorised user, map the fields that hold page, service and source, and nominate which objects and stages Siteleon may read. It writes Leads and activity, and nothing else.
What data moves, and which way
- Sent: a Lead for each enquiry, with the landing page, the requested service and the acquisition source in the fields your administrator mapped.
- Sent: later website activity for a known contact — pages viewed, forms submitted — as activity records, where you enable it.
- Received: Opportunity stage, amount, close date and loss reason, tied back to the enquiry that began it.
- Received: Account and Contact ownership, so an enquiry from an existing customer is recognised rather than arriving as a new name.
What Siteleon can do with it
- Report pipeline by landing page and campaign without exporting anything into a spreadsheet first.
- See that framework enquiries from property managers close more slowly and far larger than one-off repairs, and shift your content effort accordingly.
- Hold a Lead for review when a required field is missing, rather than pushing a broken record into your org.
- Give the sales team what the enquiry had been reading before they ring, inside the record they already work in.
Things you could ask for once it is on
- “Which pages produced the Opportunities we closed this quarter?”
- “Write hotel maintenance enquiries as Leads with the commercial record type, owned by the Valencia team.”
- “Why did Opportunities from the emergency repair page fall this month compared with last?”
Setting it up
Four steps, in this order.
- 01Connect Salesforce from Integrations using a user with API access — start in a sandbox.
- 02Create or nominate the fields that hold landing page, service and source, then map them.
- 03Choose which record types and pipelines Siteleon reads, and which stages count as won.
- 04Push a test enquiry, check the Lead against your validation and duplicate rules, then enable the live connection.
Permissions
Siteleon asks to read Leads, Contacts, Accounts and Opportunities, and to create and update only the Leads and activity records it produces, through the fields you mapped. It never asks for permission to delete records, change your org's configuration, run code, manage users, or read objects you did not map.
Where it stops
Your Salesforce configuration wins every argument. Validation rules, required fields and duplicate rules apply to what Siteleon writes, and when a record is refused Siteleon shows you the refusal rather than quietly dropping the enquiry. It does not delete records, does not change stages or amounts, and does not touch Opportunities beyond reading them. One org per Siteleon workspace, and the connection is only ever as complete as the field mapping you approved.
Customers
Others in this group.
Your business online. Built to adapt.
Start with the site you already have, or create something new. Siteleon helps you build it, understand it and keep improving it as the business changes.
No technical setup · Keep your existing site if you want to · [email protected]