What reaches the record Agentforce works from
An AI agent that drafts a renewal email from your CRM is only as current as the CRM. Salesforce knows this. Its Agentforce page says Agentforce is “grounded in Data 360 and Customer 360, so every agent knows the customer before it says a word.” In September Salesforce announced AIforce, which brings Salesforce into Claude, Slack and its own Lightning interface, so an agent can work from the same customer data wherever someone asks it a question.
Snowflake, Databricks, Google, Meta, OpenAI and the context graph vendors have all made the case that an AI agent is only as useful as what it knows about your company. Salesforce makes it too, about the customer specifically, and it has already built the part we care about most: turning conversations into updates to the record.
What Salesforce built
Agentforce agents work from Salesforce CRM data and from Data 360, Salesforce’s data platform. The Atlas Reasoning Engine breaks a request into smaller tasks and plans how to complete them. In a post after Dreamforce, Salesforce wrote that an agent “needs current information, a way to connect the details, and clear rules about what it can access and use,” and that “Customer records tell only part of the story.” Its Agent Context Engine brings call transcripts, policy documents and knowledge articles in alongside the structured data.
Salesforce also updates the record from conversations. Its sales agent turns “calls, meetings, emails, and seller notes” into “structured, objective opportunity field updates,” including Stage and Next Steps, either as suggestions or on its own. Salesforce says the goal is to “keep opportunities current based on what actually happened.” Einstein Automated Contacts finds new contacts and opportunity contact roles in email and calendar activity, and either suggests them or adds them, depending on how an admin sets it up. Salesforce said at Dreamforce that Slackforce, the part of AIforce that works inside Slack, would be generally available in October. Salesforce says Slack CRM, a new part of Slackforce, “connects every Slack conversation, user, and update to Salesforce,” and Slackbot can read “the support cases and Slack threads behind” an account that’s going quiet, reassign the owner, create a follow-up task and draft the win-back email.
So Agentforce works from the customer record, and Salesforce keeps that record current from the calls, meetings, emails and Slack conversations it captures.
A renewal that moved to procurement
Imagine you sell software to a 300-person logistics company. Their operations lead has been your champion for two years. Six weeks before the renewal, the operations lead messages your customer success manager in the Teams chat the two companies share: “Heads up, renewals over $50k now go through procurement. Please work with Dan Ortiz on ours. I’m still your contact for everything else.” The customer success manager replies “Thanks, I’ll let the team know,” and then spends the rest of the afternoon on a support escalation.
Your account manager owns the renewal in Salesforce but wasn’t in the chat. The opportunity still lists the operations lead as the contact, and nothing in it mentions procurement. The message was a Teams chat to someone else, so none of the conversations Salesforce captures contained it.
Three weeks later, the account manager asks Slackbot to draft the renewal email. Slackbot works from the record, as it should, and drafts a clear email to the operations lead about a renewal that now goes through someone the record doesn’t mention. The draft is grounded and confident, but it’s out of date. Procurement now has three weeks instead of six.
Salesforce’s State of Sales report found that reps spend 9% of their week manually entering customer and sales information. Automated opportunity updates take on part of that work, for the conversations Salesforce captures. For everything else, someone still has to remember to type it in, and in this case the customer success manager also had to remember to tell the account manager.
A record is as current as what reaches it
Salesforce’s own post opens with an agent that prepares an offer for a loyal customer but “misses the service case they’ve spent the past week trying to resolve.” In that example the information was in Salesforce, but the agent didn’t have it in context. In the procurement example the information never reached Salesforce. The customer told the person they talk to every week, in the chat they always use. The account manager, who had to act on it, never saw the thread.
Salesforce is right that an agent should work from the customer record rather than guess. For that to work, every change a customer sends has to reach the record, whichever channel the customer used and whoever on the team received it.
How to automate it
Something reads the team’s messages across the channels they use, notices that this message says the renewal now goes through procurement and names a new contact, and proposes the updates in Salesforce: Dan Ortiz on the opportunity, a note that the renewal goes through procurement, and a task for the account manager to start the procurement process, each linked to the message it came from. The account manager confirms them, and from then on Slackbot, Agentforce and anyone who opens the opportunity see the change.
That’s the layer we’re building at this+that. We read the messages a company already gets across Gmail, Outlook, Slack, Microsoft Teams, and Google Chat. Our address book, Contacts, builds itself from those channels, so when Dan Ortiz writes back, their name, title and history are already there. DoBox turns the message into a task and routes it to a workflow or a person, and a workflow can update Salesforce or HubSpot through MCP, the open standard AI tools use to connect to other software, as the message arrives, with a person approving the change.
Try it on last quarter’s renewals. Pick one where the customer changed something, like a new contact, a new process or a new date, and check whether the change reached the CRM, and if it did, whether it got there from the message or because someone remembered to type it in. If it never got there, or someone had to remember, see how our workflows can help.