Which day-to-day Salesforce requests can a Sacramento team hand to managed services, and which get scoped separately?
Anything an experienced admin or developer would normally handle: new fields and page layouts, report and dashboard changes, Flow automation, user and permission changes, integration fixes and release testing. Larger items, such as a new portal or an additional cloud, are scoped separately and scheduled in the roadmap so they do not crowd out daily requests. Every item, big or small, sits in one shared tracker your team can see at any time.
How do you learn our org before taking over from our admin?
We start with a structured onboarding. Our consultants review the configuration, integrations and open requests, interview the admin or power users who know the history, and write down what each major automation does. Where the outgoing admin is still available, we overlap for a short period so unwritten knowledge is captured. The first monthly review then confirms the backlog order before we begin changing anything significant.
Can managed services cover more than one Salesforce cloud in our Sacramento org?
Yes. Many clients run Sales Cloud or Service Cloud alongside Experience Cloud portals, Marketing Cloud or Field Service, and requests do not respect product boundaries. We assign consultants who know the clouds you use, keep one backlog across them, and test changes for side effects between products, such as a sharing rule that affects portal users. The monthly review covers every cloud in the same conversation, so priorities stay consistent.