Salesforce Admin Request Agent

1. 01

   Capture request

   Classify the request, search existing metadata, ask up to 4 questions and log the story.

2. 02

   Check existing

   Tells a user whether a field or open request already exists.

3. 03

   Security requests

   Access, permission and sharing requests, flagged and routed without detail gathering.

• The agent never creates or changes fields, permissions, flows or users.
• Ask at most 4 clarifying questions, one at a time, then log what is known.
• Only list fields the signed-in user can access (field-level security respected).
• If a similar open request exists, show it and ask whether to add to it instead of creating a new one.
• Do not store customer data, passwords or screenshots with personal data in the request.
• Business value is taken from what the requester said and never guessed.

Runs on Agentforce, Salesforce Platform license, Slack for Salesforce, Prompt Builder. Confirm editions and licenses with your Salesforce account team.

Salesforce products

AgentforceSalesforce Platform licenseSlack for SalesforcePrompt Builder

Editions and licenses

Agentforce must be enabled in your org. Confirm editions and licenses with your Salesforce account team; we check them in the first workshop.

Agent type

Agentforce Employee Agent

From you

Agentforce, Slack for Salesforce and Platform licenses. · The names of an admin channel and an admin owner.

Language

English. The agent writes in your locale and follows your wording settings.

Where it runs

Inside your Salesforce org. Records are read and written through the agent’s approved actions only.

Not included

Making the change in the org or deploying metadata. · Jira or ticket tool synchronization. · Prioritization scoring and sprint planning.

Designed in full before a line is built, with 8 scripted test conversations. The numbers become verified results when the agent is delivered.

• Deployable sourceThe agent, its actions, objects and screens as Salesforce metadata, in your repository.
• Solution designA Solution Design Document with UML: architecture, data model, sequence and security.
• Test suiteApex tests on every action, plus scripted conversations replayed before every release.
• Least-privilege accessIts own permission sets, so the agent and your staff see only what the job needs.
• Runbook and handoverHow to run it, change its rules and roll back, with a walkthrough for your team.

• Least-privilege access

  It runs as its own user with a permission set written for this agent, so it can reach only what the job needs.

• Changes only through approved actions

  The agent cannot edit records freely. Every change goes through one of its 5 actions, each with one job.

• People make the big calls

  The agent never creates or changes fields, permissions, flows or users.

• Runs inside Salesforce

  Agentforce runs on the Salesforce platform and its Einstein Trust Layer. Confirm which Trust Layer features apply to agents in your org with your Salesforce account team.

• Every change is on the record

  What the agent does lands as normal Salesforce records with their full history, so you can see who changed what and when.

• The review is free

  A 60-minute call with an architect about the Salesforce Admin Request Agent and your org, with a written plan you keep.

• A fixed-scope proposal first

  Before any work starts you get a written proposal with milestones. You approve it, or you do not.

• Timing follows scope

  How long it takes depends on your setup and your rules. The proposal states the milestones up front.

• Or inside a monthly plan

  Agents can be built and run through one of our monthly delivery plans, alongside your other Salesforce work.

Salesforce licenses, including Agentforce, are bought from Salesforce and are not part of our fee. See our plans and pricing →

• One-page brief (PDF)

  What it does, the rules it follows and what you need, on one page you can forward.

  Get the brief →

• Slide deck (PDF, 6 slides)

  For your team or steering group: the problem, what it does, the rules it follows and how we deliver it.

  Get the slides →

• Talk to an architect

  A free 60-minute session on how it would work in your org, with your processes, your data and your rules.

  Book a session →

• The whole library

  Every agent we offer, by business area.

  Browse agents →

Further reading from our architects

• Claudeforce: what actually changes for the people who run the orgSalesforce and Anthropic announced Claudeforce on 26 August 2026. What the sources actually state, what nobody has published yet, and what to do in your org before the beta reaches you.
• The grounding checklist we run before an agent talks to a customerTwelve pre-flight checks we run before an AI agent is allowed near a real customer, each with the failure it catches and the fix. A go or no-go list, not a readiness score.
• Personalisation with an agent in the loopWhere generated marketing content needs a human gate, and why the answer follows from how reversible the channel is rather than from how good the model has become.

• What does the Salesforce Admin Request Agent do?

  An Agentforce Employee Agent that takes Salesforce change requests from staff in Slack, checks whether the field or report already exists, asks a few clarifying questions and logs a structured user story for the admin team. A clean, de-duplicated backlog instead of vague messages.

• Which Salesforce products does it run on?

  Agentforce, Salesforce Platform license, Slack for Salesforce, Prompt Builder. Confirm editions and licenses with your Salesforce account team.

• Where do people use it?

  Slack (primary), Lightning Experience agent panel.

• What does it not do?

  Making the change in the org or deploying metadata; Jira or ticket tool synchronization; Prioritization scoring and sprint planning.

• Is there a demo?

  Not yet. This agent is in our build program and is coming soon. We can scope it for your org now, and show you the agents that are already live.