Searchlab Cloud Setup & Config
Out of the box, Salesforce is a set of defaults. Configuration is what turns it into your pipeline, your routing rules and your service targets. This work covers the setup inside Sales Cloud and Service Cloud that makes daily use fast instead of tolerable.
In Sales Cloud we configure the revenue path end to end. Lead sources, assignment rules and conversion field mapping, opportunity stages with written exit criteria, products and price books, quote templates, and forecast categories that roll up correctly. Path guidance puts coaching notes directly on the stage bar, so a new rep sees what good looks like without opening a manual.
Service Cloud setup is about routing and time. Case record types, email to case and web to case intake, auto response rules, assignment and escalation rules, entitlement processes with milestones for response and resolution targets, and Omni Channel routing based on skills and capacity. Knowledge articles and macros then cut handling time on the questions that repeat every day.
Both clouds share the same configuration layer, and that layer is where usability is won. Lightning record pages built in App Builder, dynamic forms and dynamic actions so fields and buttons appear only when relevant, compact layouts driving the highlights panel, list views per role, and global actions for the tasks people repeat dozens of times a day.
We configure with change control. Everything is built in a sandbox, checked against the requirement it came from, then deployed. Org wide feature switches such as Person Accounts, State and Country picklists, multi currency and Opportunity Splits are flagged early, because several of them cannot be switched off cleanly once they are enabled in production.
Everything in Cloud Setup & Config
Sales process configuration
Stages, exit criteria, path guidance, opportunity types, close date discipline and forecast categories set up so the pipeline report means one thing to everyone.
Lead management setup
Lead sources, web to lead capture, assignment rules, queues, conversion field mapping and a documented rule for when a lead becomes an opportunity.
Products, price books and quotes
Product catalogue, standard and custom price books, quote line editor setup and branded quote templates that generate a PDF your reps can send directly.
Case management setup
Case record types, email to case, web to case, auto response rules, assignment and escalation rules, and status values that match how support actually works.
Entitlements and Omni Channel
Entitlement processes with response and resolution milestones, plus skills or capacity based routing so cases reach the right agent instead of a shared inbox.
Lightning page and layout build
Record pages assembled in App Builder with dynamic forms, dynamic actions, compact layouts and related lists ordered by what the user needs first.
Knowledge and macros
Article types, a publishing and approval workflow, article suggestions on cases, and macros for the replies and field updates agents run all day.
Configuration workbook
A written record of every setting changed, why it was changed, and which settings are irreversible, so nobody has to guess about it a year later.
The process
Requirement mapping
We take each process from discovery and decide whether it is a setting, a layout, an automation or a build. Anything Salesforce already does natively wins by default.
Sandbox configuration
Both clouds are configured in a sandbox with realistic sample records, so stages, routing rules and entitlement clocks can be tested against actual deal and case scenarios.
User walkthrough
Two or three of your daily users run a normal working week inside the sandbox. The friction list they produce drives the next round of layout and automation changes.
Deploy and enable
Configuration moves to production through change sets or SFDX, org wide feature switches are enabled in a planned window, and users receive a short what changed note.
Questions about Cloud Setup & Config
What is the difference between configuration and customisation?
Configuration uses the tools Salesforce gives administrators: fields, layouts, rules, flows, permission sets. Customisation means code, usually Apex and Lightning Web Components. Configuration is faster, cheaper and upgrade safe, so we exhaust it first and write code only when the platform genuinely cannot do the job.
Can we run Sales Cloud and Service Cloud in the same org?
Yes, and most mid sized companies should. Shared accounts and contacts mean a rep can see open cases before a renewal call. The real work is separating the two experiences with record types, layouts, apps and permission sets, so neither team has to wade through screens built for the other.
Do we need Salesforce CPQ for quoting?
Not usually at the start. Standard products, price books and quotes handle simple catalogues and percentage discounts well. CPQ earns its cost when you have bundles, tiered or usage based pricing, subscription renewals and approval driven discounting. We prefer to configure standard quoting first and revisit CPQ when the complexity is real.
Which settings cannot be reversed?
Several org wide switches are one way or messy to undo, including Person Accounts, State and Country picklists, multi currency, Opportunity Splits and some sharing model changes. Every irreversible setting goes in the configuration workbook, gets tested in a sandbox, and needs written sign off before we enable it.
Ready to talk about Cloud Setup & Config?
Tell us where you are stuck. We reply within the hour on WhatsApp, usually sooner.
Or email Searchlabtools@gmail.com