Salesforce
Managed Services

Salesforce ships three major releases a year, in Spring (February), Summer (June) and Winter (October), and the upgrades are mandatory under the Salesforce contract. Sandbox preview instances are upgraded four to five weeks before each release, and the maintenance schedule is published a year ahead.

That preview window is when a managed services team reads the release notes, tests your automation and integrations in the upgraded sandbox, and plans any changes, so production upgrades without surprises.

For a cost comparison of outsourced administration, see Salesforce administration outsourcing. Not sure what state the org is in? Start with a Salesforce health check, or request a free Salesforce org audit. If you are weighing Salesforce's own support plans, read Salesforce Premier Support explained. Managed services contracts often follow industry rules, so see Salesforce for healthcare, Salesforce for financial services and Salesforce for manufacturing. To scope a contract for your org, book a discovery call.

Most managed services problems trace back to a contract that was vague about what is included. Check each provider on your shortlist against this list before you sign:

• Scope per release. The contract says what is covered in each Salesforce release cycle: reading the release notes, testing in the sandbox preview, applying release updates and fixing what breaks.
• Response targets written into the contract. Each priority level has a written response target and a defined way to raise urgent issues, including outside your business hours. Targets in a sales deck do not count.
• A named team. You know who works on your org, by name and role, and how a replacement is introduced if someone leaves. Check their certifications on Trailhead.
• Release management. Changes move from sandbox to production through a defined process, with source control or a deployment tool, testing and a rollback plan, not edits made directly in production.
• Reporting. A regular report shows requests raised and closed, hours or services used against the allowance, open risks and what is planned next.
• Exit terms. The contract sets out notice periods, a handover of documentation, credentials and open work, and how access is removed at the end, so you can change provider without losing knowledge of the org.

Ask each provider to show a sample monthly report and a sample release plan, and compare them side by side. For the questions to ask any Salesforce partner, see choosing a Salesforce consulting partner.

A US company keeps ownership of priorities and approvals, and the delivery team in India does the support, build and release work against an agreed scope. Techila Global Services is headquartered in Frisco, Texas, and its main delivery center is in Pune, India.

India Standard Time is UTC+5:30 with no daylight saving, so India is 9.5 to 13.5 hours ahead of the continental US, depending on the time zone and the time of year. A normal India working day falls during the US night. Contracts therefore name the US hours that are covered live, how urgent issues are raised outside them, and the response target for each priority.

Common patterns are a shift that overlaps the US morning, follow-the-sun work where requests raised in the US day are ready by the next morning, and a US-based lead in front of the India team. Access is controlled with standard Salesforce features: named users, least-privilege permission sets, login IP ranges and login hours on profiles, and Setup Audit Trail to review configuration changes.

For coverage models, access controls and contract terms in more detail, see offshore Salesforce managed services for US companies. Companies running a global capability center can use GCC managed services.