Salesforce MVP Hall of Fame (Shivanath Devinarayanan) · Founded 2022
Three questions. Then a runtime.
For customer support, use Agentforce when the cases, customers and permissions already live in Salesforce. Use a custom agent when the work happens on WhatsApp, a portal or another system, or when you need a specific model or hosting region. Use both when you have both, joined through the CRM.
Founded 2022 · Founder in the Salesforce MVP Hall of Fame · Dubai HQ · Kochi studio
- 01Models · Claude, Gemini, OpenAI, Bedrock
- 02Agentic systems · Agentforce, CrewAI, ADK, A2A
- 03Agentic memory · Neo4j, Cognee, IndyKite
- 04Automation and voice · n8n, Retell
- 05Deployment and governance · identity, evals, policy, audit
The questions
Where the users sit. Where the data sits. Who owns the plane.
The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.
- Where do the users already work?
- Agentforce if they live in the Salesforce console, Experience Cloud, or Slack. Slack-first teams can run Agentforce in Slack when the work and permissions live in Salesforce. Custom or Claude if the job spans other tools, runs on WhatsApp, or sits in a portal that is not Experience Cloud.
- Where does the system of record live?
- Agentforce if the org already holds knowledge, cases, opportunities, and Data Cloud grounding that respects sharing. Custom when ERP, a warehouse, or documents would only see Salesforce as a middleman.
- Who must own the control plane?
- Agentforce if you want Salesforce procurement, Trust Layer, and inherited profiles. Custom if you need BYOM, MCP connectors, A2A between runtimes, or an audit trail Salesforce will not emit.
The answer
Agentforce, or custom.
The same three questions, answered both ways.
Agentforce when
Custom when
- Users work in the Salesforce console, Experience Cloud or Slack
- The job spans other tools, WhatsApp, or a non-Salesforce portal
- Knowledge, cases and grounding already live in the org
- ERP, a warehouse or documents hold the record
- You want Salesforce procurement, Trust Layer and inherited profiles
- You need your own model, MCP connectors or your own audit trail
Hybrid
Most real orgs need both.
Do not buy seats for work that lives outside Salesforce. Do not build a custom agent to avoid reading the org. In Slack, both can sit in the same channel.
Worked examples
Three desks, three answers.
Example
Service lead at a US software company
Today: Cases and knowledge are in Service Cloud.
After: Agentforce in the console.
AgentforceExample
Sales manager at a Dubai car dealer
Today: Buyers write on WhatsApp. Stock is in a dealer system.
After: A custom agent on WhatsApp that writes the lead to Salesforce.
WhatsApp agentsExample
Ops head at a Riyadh contractor
Today: Approvals in Slack, contracts in Salesforce, costs in the ERP.
After: Both: Agentforce for Salesforce work and a custom agent across tools, in the same Slack channel.
Slack
The brief
Send the three answers.
We will tell you which runtime, or an honest no. The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days.
