Guides to Salesforce problems we fix
Each guide comes from a problem we solved in a production org: what causes it, how to confirm it, and the fix.
All guides
- Why a completed DocuSign envelope never reaches SalesforceThe signer finished, DocuSign shows Completed, and the Salesforce record still says Sent. In the orgs we work on it is almost always one of five causes, and the package logs every one of them.
- Connecting Claude to Salesforce through MCPSalesforce hosts MCP servers that let Claude query your org as the person using it. Setup takes an afternoon. Most questions afterwards come from four misunderstandings, all fixable.
- Salesforce data storage over the limit: what to delete firstWhen data storage passes 100%, inserts start failing, and integrations usually fail first. The fix is rarely more storage. It is usually years of activity history nobody reads.
- Salesforce record page blank in the mobile appThe record opens on a phone with a header and nothing else, while the same record looks fine on a laptop. If the page uses Dynamic Forms, the cause is usually the phone assignment.
- Agentforce readiness: what to fix before your first agentAn agent answers from your records. If the records disagree, it gives a confident wrong answer faster than a person would. These are the checks we run before any agent goes live, whether it is Agentforce inside Salesforce or Claude connected through MCP.
Talk to us about your systems.
Tell us which systems are involved and what is going wrong. We reply within one business day, and new engagements begin in January 2027.
hello@feldtgroup.com