{"id":1647,"date":"2026-11-19T15:33:20","date_gmt":"2026-11-19T10:03:20","guid":{"rendered":"https:\/\/www.dhruvsoft.com\/blog\/?p=1647"},"modified":"2026-11-19T15:35:23","modified_gmt":"2026-11-19T10:05:23","slug":"how-agentforce-ai-handles-tier-1-support-tickets","status":"publish","type":"post","link":"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/","title":{"rendered":"How Agentforce Handles Tier-1 Support Tickets Automatically\u00a0\u00a0"},"content":{"rendered":"\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/www.dhruvsoft.com\/blog\/wp-content\/uploads\/2026\/11\/How-Agentforce-Handles-Tier-1-Support-Tickets-Automatically.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"323\" src=\"https:\/\/www.dhruvsoft.com\/blog\/wp-content\/uploads\/2026\/11\/How-Agentforce-Handles-Tier-1-Support-Tickets-Automatically.png\" alt=\"\" class=\"wp-image-1648\" title=\"How Agentforce Handles Tier-1 Support Tickets Automatically\" srcset=\"https:\/\/www.dhruvsoft.com\/blog\/wp-content\/uploads\/2026\/11\/How-Agentforce-Handles-Tier-1-Support-Tickets-Automatically.png 1024w, https:\/\/www.dhruvsoft.com\/blog\/wp-content\/uploads\/2026\/11\/How-Agentforce-Handles-Tier-1-Support-Tickets-Automatically-300x95.png 300w, https:\/\/www.dhruvsoft.com\/blog\/wp-content\/uploads\/2026\/11\/How-Agentforce-Handles-Tier-1-Support-Tickets-Automatically-767x242.png 767w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The Opportunity to Automate Tier-1 Customer Support<\/strong>\u00a0\u00a0\u00a0<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Customer service teams spend a large share of their day on the same handful of requests: password resets, order-status questions, plan and billing FAQs, basic account updates, and routine troubleshooting. None of these require deep expertise, yet each one still takes an agent&#8217;s time to read, look up, and answer. As ticket volumes grow, this repetitive workload crowds out the complex, judgment-heavy cases that actually need a skilled human agent, and response times slip across the board.<\/p>\n\n\n\n<!--more-->\n\n\n\n<p class=\"wp-block-paragraph\">As a business scales, this volume grows with it. More products mean more FAQs, more customers mean more account questions, and wider distribution means more shipment enquiries. Leadership teams want to grow ticket capacity without growing headcount at the same rate.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Traditional chatbots were meant to solve this, but they follow fixed scripts and break the moment a customer phrases a request differently. The shift now is toward AI agents that reason about a request, retrieve the right information from business systems, and take permitted actions on the customer&#8217;s behalf.Salesforce Agentforce is built for exactly this shift. It combines large language model reasoning with direct access to an organization&#8217;s own Salesforce data, knowledge base, and configured business processes, so its responses are grounded in what is actually true for that customer rather than generic, templated text. This article walks through what Agentforce is, how it works, what a well-designed Tier-1 automation strategy looks like in practice, and the governance and measurement practices that keep it reliable once it is live.<\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_86 ez-toc-wrap-left-text counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 eztoc-toggle-hide-by-default' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#What_Is_Agentforce\" >What Is Agentforce?\u00a0\u00a0\u00a0<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#Agentforce_in_Salesforce\" >Agentforce in Salesforce\u00a0\u00a0\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#How_Agentforce_Differs_From_a_Traditional_Chatbot\" >How Agentforce Differs From a Traditional Chatbot\u00a0\u00a0\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#Where_Agentforce_Fits_in_the_Service_Operation\" >Where Agentforce Fits in the Service Operation\u00a0\u00a0\u00a0<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#What_Makes_a_Ticket_Suitable_for_Agentforce_Automation\" >What Makes a Ticket Suitable for Agentforce Automation?\u00a0\u00a0\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#How_Agentforce_Handles_a_Tier-1_Ticket\" >How Agentforce Handles a Tier-1 Ticket\u00a0\u00a0\u00a0<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#Example_Scenario_1_%E2%80%9CWhere_Is_My_Order%E2%80%9D\" >Example Scenario 1: &#8220;Where Is My Order?&#8221;\u00a0\u00a0\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#Example_Scenario_2_Password_or_Account_Access_Questions\" >Example Scenario 2: Password or Account Access Questions\u00a0\u00a0\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#Example_Scenario_3_Product_or_Service_FAQ\" >Example Scenario 3: Product or Service FAQ\u00a0\u00a0\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#Example_Scenario_4_Basic_Troubleshooting\" >Example Scenario 4: Basic Troubleshooting\u00a0\u00a0\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#Example_Scenario_5_Creating_a_Support_Case_Automatically\" >Example Scenario 5: Creating a Support Case Automatically\u00a0\u00a0\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#Example_Scenario_6_Subscription_and_Billing_Cycle_Questions\" >Example Scenario 6: Subscription and Billing Cycle Questions\u00a0\u00a0\u00a0<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#What_Agentforce_Needs_to_Automate_Tier-1_Support_Successfully\" >What Agentforce Needs to Automate Tier-1 Support Successfully\u00a0\u00a0\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#Agentforce_Salesforce_Service_Cloud_How_They_Work_Together\" >Agentforce + Salesforce Service Cloud: How They Work Together\u00a0\u00a0\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#Measuring_the_Impact_of_Tier-1_AI_Automation\" >Measuring the Impact of Tier-1 AI Automation\u00a0\u00a0\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#Governance_Security_and_Human_Oversight\" >Governance, Security, and Human Oversight<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-17\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#Implementation_Roadmap_for_Agentforce_Tier-1_Support\" >Implementation Roadmap for Agentforce Tier-1 Support\u00a0\u00a0\u00a0<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-18\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#Industry_Examples\" >Industry Examples\u00a0\u00a0\u00a0<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-19\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#Dhruvsofts_Approach_to_Agentforce_Implementation\" >Dhruvsoft&#8217;s Approach to Agentforce Implementation\u00a0\u00a0\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-20\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#Final_Thoughts_Automate_the_Routine_Escalate_the_Complex\" >Final Thoughts: Automate the Routine, Escalate the Complex\u00a0\u00a0\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-21\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#Frequently_Asked_Questions\" >Frequently Asked Questions<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-22\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#Ready_to_Explore_Agentforce_for_Your_Customer_Service_Operations\" >Ready to Explore Agentforce for Your Customer Service Operations?\u00a0\u00a0\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-23\" href=\"https:\/\/www.dhruvsoft.com\/blog\/how-agentforce-ai-handles-tier-1-support-tickets\/#About_Dhruvsoft\" >About Dhruvsoft\u00a0\u00a0\u00a0<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_Is_Agentforce\"><\/span><strong>What Is Agentforce?<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Agentforce_in_Salesforce\"><\/span><strong>Agentforce in Salesforce<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.dhruvsoft.com\/salesforce-agentforce\/\" target=\"_blank\" rel=\"noopener\">Agentforce<\/a> is Salesforce&#8217;s platform for building and deploying AI agents that work alongside human teams rather than replacing the systems they already use. Agents built on Agentforce operate directly on top of Salesforce CRM data, existing automation, and business processes, which means they can act on real customer, case, and order records instead of generic scripted content.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Each agent is built from sub-agents (called topics before April 2026). A sub-agent covers one job, such as order inquiries or account management, and has its own instructions and actions. An Agent Router decides which sub-agent handles each customer message.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_Agentforce_Differs_From_a_Traditional_Chatbot\"><\/span><strong>How Agentforce Differs From a Traditional Chatbot<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A traditional chatbot matches a customer&#8217;s message to a predefined question and returns a fixed response, and it breaks down the moment a request falls outside its scripted flow. An Agentforce agent instead understands natural-language requests, pulls in relevant business context, and works out the next appropriate action within boundaries an organization defines. When a situation falls outside what it is authorized to handle, it escalates to a human agent with the conversation history intact, rather than leaving the customer stuck in a dead-end script.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For steps that must always run the same way, such as identity verification or refunds, Agentforce lets teams define deterministic logic alongside the LLM&#8217;s reasoning. Critical processes follow fixed rules instead of being left to the model&#8217;s judgment.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Where_Agentforce_Fits_in_the_Service_Operation\"><\/span><strong>Where Agentforce Fits in the Service Operation<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Agentforce typically operates across four layers of a service operation: self-service for customers looking for quick answers on their own, Tier-1 support for routine requests that would otherwise consume agent time, assistance for human agents handling active cases, and structured escalation and case management for anything that needs a person&#8217;s judgment.This layered view matters because it reframes Agentforce as part of the service operation rather than a bolt-on widget. In the self-service layer, customers get answers on their own terms, at any hour, without waiting in a queue. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In Tier-1 support, the agent absorbs the repetitive volume that would otherwise sit between the customer and a live representative. Where a human agent is already working a case, Agentforce can act as an assistant, surfacing relevant knowledge, summarizing case history, or drafting a response for the agent to review. And at the escalation layer, it hands off cleanly to a person with full context, rather than dropping the customer back to square one.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_Makes_a_Ticket_Suitable_for_Agentforce_Automation\"><\/span><strong>What Makes a Ticket Suitable for Agentforce Automation?<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Not every ticket is a good candidate for automation, and choosing the right ones is the single biggest factor in a successful rollout. Good candidates are high-volume, low-complexity requests such as frequently asked questions, order-status enquiries, basic account information, and standard troubleshooting. They also tend to follow well-defined processes with clear business rules, known resolution paths, and reliable knowledge articles behind them. And the actions involved are low risk, such as providing information, creating a case, checking status, or sending pre-approved content.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Some tickets should stay with human agents regardless of how mature the automation program becomes. This includes sensitive account changes, complex technical issues, complaints that require judgment and empathy, security-related incidents, and any request that falls outside the organization&#8217;s defined business rules. Recognizing this boundary up front, rather than discovering it after a bad customer experience, is central to designing Agentforce responsibly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A useful way to think about ticket suitability is to plot requests along two dimensions: how often they occur, and how much judgment or risk is involved in resolving them. High-frequency, low-judgment requests sit squarely in Agentforce&#8217;s sweet spot. High-frequency, high-judgment requests, such as billing disputes or service complaints, are better handled with AI assistance for the human agent rather than full automation. Low-frequency requests of any complexity are usually not worth automating at all, since the engineering effort to configure and test a reliable workflow rarely pays back against a handful of tickets a month. This kind of prioritization exercise, done early with real ticket data, prevents teams from automating the wrong things simply because a use case sounds impressive on paper.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_Agentforce_Handles_a_Tier-1_Ticket\"><\/span><strong>How Agentforce Handles a Tier-1 Ticket<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A Tier-1 interaction generally follows a consistent pattern from the customer&#8217;s first message to resolution. The customer starts a conversation through the website, a service portal, a messaging channel, or another supported service channel. Agentforce then interprets the natural-language request and identifies the relevant context behind it, before retrieving the information it needs from Salesforce CRM records, knowledge articles, approved business content, or connected systems where configured.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the request involves the customer&#8217;s own account, orders, or cases, the agent first verifies their identity. Salesforce&#8217;s standard Customer Verification sub-agent asks for the customer&#8217;s email address or username, sends a one-time code, and unlocks protected actions only once the code matches. General questions answered from public knowledge need no verification.From there, the agent determines the appropriate action, whether that is answering the question directly, retrieving information, performing an authorized action, creating or updating a case, or escalating to a human.It responds to the customer while maintaining full conversation context, and if escalation is required, it transfers the interaction to a human service representative through Omni-Channel routing, along with the relevant conversation and case history, so the customer never has to repeat themselves. Escalation rules can also require the agent to collect key details, such as an order number or email address, before handing off, so the representative starts with everything they need.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Example_Scenario_1_%E2%80%9CWhere_Is_My_Order%E2%80%9D\"><\/span><strong>Example Scenario 1: &#8220;Where Is My Order?&#8221;<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Customer: &#8220;Can you tell me when my order will arrive?&#8221;<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Agentforce identifies this as an order-status question, verifies the customer&#8217;s identity, finds their account, retrieves the relevant order information from the configured system (such as Salesforce Order Management or a connected ERP), and checks available shipment data before providing the latest status. If the order information is unavailable or needs investigation, it escalates the case to a human agent instead of guessing or giving an unreliable answer. This single use case alone can meaningfully reduce repetitive status enquiries, give customers faster access to information at any hour, and free agents to focus on genuine exceptions rather than routine lookups.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Example_Scenario_2_Password_or_Account_Access_Questions\"><\/span><strong>Example Scenario 2: Password or Account Access Questions<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Customer: &#8220;I can&#8217;t access my account. How can I reset my password?&#8221;<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Agentforce identifies the request and walks the customer through the organization&#8217;s approved password-reset process, directing them to the appropriate secure workflow, such as the self-service reset link on the customer portal. In most setups, the reset itself happens in the organization&#8217;s identity system, not inside the conversation. If the standard process does not resolve the issue, it creates or escalates a case rather than attempting to work around it. This is an important boundary to design in from the start: Agentforce should never bypass authentication or security controls, and any sensitive account action must continue to follow the organization&#8217;s configured security policies.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Example_Scenario_3_Product_or_Service_FAQ\"><\/span><strong>Example Scenario 3: Product or Service FAQ<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Customer: &#8220;What is included in my service plan?&#8221;<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Agentforce identifies the customer&#8217;s question, retrieves approved knowledge content, and uses relevant account or service context where it is authorized and the customer has been verified before providing the answer. If the customer&#8217;s specific situation falls outside standard policy, it offers escalation rather than giving an answer that cannot fully support. The business value here is straightforward: consistent, accurate responses every time, faster resolution for the customer, and a meaningful drop in repetitive ticket volume for the service team.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Example_Scenario_4_Basic_Troubleshooting\"><\/span><strong>Example Scenario 4: Basic Troubleshooting<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Customer: &#8220;My device isn&#8217;t connecting. What should I check?&#8221;<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Agentforce identifies the product and the issue, retrieves the approved troubleshooting procedure, and guides the customer step by step through the documented process. It then determines whether the issue appears resolved, and if further technical support is required, it creates or escalates a case with the troubleshooting steps already attempted, so a human agent does not have to start from zero.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Example_Scenario_5_Creating_a_Support_Case_Automatically\"><\/span><strong>Example Scenario 5: Creating a Support Case Automatically<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Customer: &#8220;My invoice is incorrect. I need someone to review it.&#8221;<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Agentforce recognizes that this request requires human investigation, collects the relevant details from the customer, creates a Salesforce case, categorizes it correctly, routes it according to configured rules, and confirms the next steps to the customer. The clear benefit is that the customer does not need to repeat information to a human agent once the case is escalated, since everything gathered during the conversation carries forward automatically.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Example_Scenario_6_Subscription_and_Billing_Cycle_Questions\"><\/span><strong>Example Scenario 6: Subscription and Billing Cycle Questions<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Customer: &#8220;When does my subscription renew, and can I change my plan before then?&#8221;<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Agentforce verifies the customer, looks up their subscription record, identifies the renewal date, and checks which plan changes are permitted before that date under the organization&#8217;s configured business rules. It explains the available options directly, and if the customer wants to proceed with a change that falls within its authorized actions, it can initiate the update through a configured action (built in Flow or Apex during implementation) and confirm the new terms. If the request involves a refund, a contract exception, or a plan change outside standard rules, it creates a case and routes it to the billing team instead of attempting to resolve it unilaterally. This kind of request is common across subscription-based businesses and illustrates how Agentforce can move beyond answering questions into safely completing simple transactions.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_Agentforce_Needs_to_Automate_Tier-1_Support_Successfully\"><\/span><strong>What Agentforce Needs to Automate Tier-1 Support Successfully<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Reliable automation depends on a few foundational elements being in place. High-quality knowledge, meaning accurate articles, current troubleshooting procedures, and approved customer-facing content, gives the agent something trustworthy to draw from. Reliable CRM data across customer records, product information, service history, and case history ensures responses reflect what is actually true for that customer. Clearly defined actions, spelling out exactly what the agent can read, what it can change, what requires approval, and what must be escalated, keep automation within safe boundaries. And well-designed service processes, including case categorization, routing rules, escalation paths, and service-level agreements, give the agent a structure to operate inside rather than making decisions in a vacuum.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Two platform prerequisites are easy to overlook. First, Data 360 (formerly Data Cloud) must be enabled: knowledge articles and other approved content are indexed in Data 360 through an Agentforce Data Library, which powers the agent&#8217;s knowledge answers. Second, the agent needs a deployed messaging channel, such as Enhanced Chat on the website or WhatsApp, connected to Omni-Channel routing so it can receive conversations and hand them to human queues.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Agentforce_Salesforce_Service_Cloud_How_They_Work_Together\"><\/span><strong>Agentforce + Salesforce Service Cloud: How They Work Together<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Agentforce and Service Cloud are designed to complement each other rather than compete. Agentforce handles the conversational AI interaction itself, executes configured actions, and supports both autonomous and human-assisted service workflows. Service Cloud provides the underlying case management, knowledge base, service console, customer information, and routing processes that already run the service operation. Together, AI handles the routine interactions that fit its defined scope; Salesforce supplies the customer and service context needed to do that well, and human agents remain focused on the complex or sensitive issues that genuinely need their judgment.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Measuring_the_Impact_of_Tier-1_AI_Automation\"><\/span><strong>Measuring the Impact of Tier-1 AI Automation<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A useful measurement framework tracks Tier-1 ticket volume, automated resolution rate, escalation rate, first-response time, average handling time, customer satisfaction, case backlog, and cost per interaction. It is important to measure both automation performance and the actual customer experience side by side since a high automation rate on its own is not a success metric if customers are left frustrated. Ongoing monitoring should specifically watch for incorrect responses, unnecessary escalations, and interactions that end without genuine resolution.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Cost per interaction depends on how Agentforce is licensed. Salesforce offers per-action pricing through Flex Credits (about $0.10 per standard action at list price), per-conversation pricing, and per-user licenses. Each lookup, verification step, or case creation counts as an action, so well-scoped conversations with fewer steps cost less to run. It also helps to track these metrics over time rather than as a single snapshot after launch. Automation performance typically improves over the first few months as knowledge content is refined, edge cases are identified, and configuration is tuned based on real conversations.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"> A dip in customer satisfaction immediately after launch is not automatically a failure signal, but a sustained dip that does not recover as the system matures usually points to a scope, knowledge, or escalation problem that needs attention. Reviewing a sample of actual conversations every week, not just the aggregate metrics, is often what surfaces these issues early.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Governance_Security_and_Human_Oversight\"><\/span><strong>Governance, Security, and Human Oversight<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"alignright size-large is-resized\"><a href=\"https:\/\/www.dhruvsoft.com\/blog\/wp-content\/uploads\/2026\/11\/Secure-AI-Governance-Security-Human-Oversight.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"512\" src=\"https:\/\/www.dhruvsoft.com\/blog\/wp-content\/uploads\/2026\/11\/Secure-AI-Governance-Security-Human-Oversight-1024x512.png\" alt=\"Secure AI Governance, Security &amp; Human Oversight\" class=\"wp-image-1649\" style=\"width:729px;height:auto\" title=\"Secure AI Governance, Security &amp; Human Oversight\" srcset=\"https:\/\/www.dhruvsoft.com\/blog\/wp-content\/uploads\/2026\/11\/Secure-AI-Governance-Security-Human-Oversight-1024x512.png 1024w, https:\/\/www.dhruvsoft.com\/blog\/wp-content\/uploads\/2026\/11\/Secure-AI-Governance-Security-Human-Oversight-768x384.png 768w, https:\/\/www.dhruvsoft.com\/blog\/wp-content\/uploads\/2026\/11\/Secure-AI-Governance-Security-Human-Oversight-300x150.png 300w, https:\/\/www.dhruvsoft.com\/blog\/wp-content\/uploads\/2026\/11\/Secure-AI-Governance-Security-Human-Oversight.png 1200w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure>\n<\/div>\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Define Agent Permissions:<\/strong> Limit the agent&#8217;s data access and available actions to exactly what each use case requires, nothing broader.<\/li>\n\n\n\n<li><strong>Require Customer Verification:<\/strong> Gate every sub-agent and action that touches account data behind identity verification.<\/li>\n\n\n\n<li><strong>Establish Escalation Rules:<\/strong> Identify in advance the situations that must always be handed to a human rather than leaving this to be discovered in production.<\/li>\n\n\n\n<li><strong>Test Before Every Change:<\/strong> Run test conversations covering normal requests, edge cases, incorrect inputs, and escalations before each release, not just before launch.<\/li>\n\n\n\n<li><strong>Monitor Agent Activity:<\/strong> Regularly review interactions, track outcomes, and identify recurring failure patterns before they affect many customers.<\/li>\n\n\n\n<li><strong>Keep Knowledge Current:<\/strong> Remove outdated articles and review knowledge content on a regular schedule since the agent is only as accurate as what it is given to work with.<\/li>\n\n\n\n<li><strong>Protect Sensitive Data:<\/strong> Follow organizational security policies and apply appropriate Salesforce permissions and access controls to every agent configuration. The Einstein Trust Layer adds toxicity detection, prompt defense, and audit logging to every LLM interaction.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">The most common mistakes we see are the reverse of these practices: automating poorly documented processes, giving the agent excessive permissions, relying on outdated knowledge, automating complex cases too early, skipping escalation paths or testing, and judging success by ticket deflection alone while ignoring customer feedback.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Implementation_Roadmap_for_Agentforce_Tier-1_Support\"><\/span><strong>Implementation Roadmap for Agentforce Tier-1 Support<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A structured rollout typically moves through six phases. The first phase identifies automation opportunities by analyzing support-ticket history and pinpointing high-volume repetitive requests. The second phase categorizes and prioritizes these requests into low-risk informational tickets, standard service requests, and those requiring human judgment. The third phase prepares data and knowledge, cleaning CRM records, reviewing knowledge articles, setting up Data 360 and the Agentforce Data Library, and defining approved responses.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The fourth phase configures Agentforce itself, setting up sub-agents, instructions, actions, customer verification, permissions, and escalation paths. The fifth phase tests the configuration thoroughly in a sandbox against positive scenarios, edge cases, incorrect inputs, and escalation scenarios before anything reaches real customers. The sixth and final phase launches with a limited set of use cases, tracks performance closely, reviews actual conversations, and expands automation gradually as confidence and data quality improve.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Industry_Examples\"><\/span><strong>Industry Examples<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Manufacturing:<\/strong> Order status, product information, shipment enquiries, and basic technical support are common early automation targets for manufacturers with high transaction volumes.<\/li>\n\n\n\n<li><strong>SaaS:<\/strong> Account questions, subscription information, product FAQs, and basic troubleshooting make up a large share of SaaS support volume and automate well.<\/li>\n\n\n\n<li><strong>Healthcare:<\/strong> General service information, appropriate appointment-related support, and non-sensitive FAQs can be automated, with strict controls maintained around any protected or sensitive information, including HIPAA requirements for US providers. See our <strong><a href=\"https:\/\/www.dhruvsoft.com\/salesforce-health-cloud\/\" target=\"_blank\" rel=\"noopener\">Health Cloud post<\/a><\/strong> for more.<\/li>\n\n\n\n<li><strong>Financial Services:<\/strong> General account information, product FAQs, and routine service requests can be automated alongside strong authentication and compliance controls given the sensitivity of financial data.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Dhruvsofts_Approach_to_Agentforce_Implementation\"><\/span><strong>Dhruvsoft&#8217;s Approach to Agentforce Implementation<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Salesforce Crest Partner \u00b7 15+ years \u00b7 200+ Salesforce projects \u00b7 50+ certified consultants \u00b7 100+ clients \u00b7 7 industries<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dhruvsoft begins every Agentforce engagement with a service process assessment, analyzing existing support operations and identifying which requests are genuinely suitable for automation rather than assuming every ticket type qualifies. From there, we define an Agentforce strategy that establishes appropriate use cases along with clear escalation and governance rules from day one.On the technical side, we configure <a href=\"https:\/\/www.dhruvsoft.com\/salesforce-service-cloud\/\" target=\"_blank\" rel=\"noopener\">Service Cloud<\/a>, knowledge, <a href=\"https:\/\/www.dhruvsoft.com\/salesforce-data-cloud\/\" target=\"_blank\" rel=\"noopener\">Data 360<\/a>, case management, and Agentforce actions to work together as one coherent system, and integrate relevant enterprise systems where required with controlled, permissioned data access. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Before anything goes live, we validate responses against real scenarios through our <a href=\"https:\/\/www.dhruvsoft.com\/salesforce-com-testing-services\/\" target=\"_blank\" rel=\"noopener\">Salesforce Testing Services<\/a> team, which includes dedicated Agentforce testing, and once launched, we continue monitoring automation performance and refining workflows so the system keeps improving rather than stalling after the initial rollout.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Final_Thoughts_Automate_the_Routine_Escalate_the_Complex\"><\/span><strong>Final Thoughts: Automate the Routine, Escalate the Complex<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Tier-1 support contains a large share of interactions that follow predictable, well-documented patterns, which makes them genuinely good candidates for automation. Agentforce can draw on Salesforce data, knowledge content, and configured actions to handle these requests reliably, but successful automation always depends on data quality, well-defined processes, carefully scoped permissions, customer verification, thorough testing, and clear human escalation paths. The goal is not to remove human service teams from the equation, but to reduce the repetitive workload on them so agents can focus on the cases that genuinely need expertise and judgment. A phased approach, starting narrow and expanding gradually, lets organizations measure real performance before scaling AI automation further.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Frequently_Asked_Questions\"><\/span><strong>Frequently Asked Questions<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<div class=\"wp-block-esab-accordion esab-tnsflr4h\" data-mode=\"global\" data-close=\"true\"><div class=\"esab__container\">\n<div class=\"wp-block-esab-accordion-child\"><div class=\"esab__head\" role=\"button\" aria-expanded=\"false\"><div class=\"esab__heading_txt\"><p class=\"esab__heading_tag\"><strong>What types of support tickets can Agentforce automate?<\/strong><\/p><\/div><div class=\"esab__icon\"><div class=\"esab__collapse\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m3.5 20.5c-4.7-4.7-4.7-12.3 0-17 4.7-4.7 12.3-4.7 17 0 4.6 4.7 4.6 12.3 0 17-4.7 4.6-12.3 4.6-17 0zm0.9-0.9c4.2 4.2 11 4.2 15.2 0 4.2-4.2 4.2-11 0-15.2-4.2-4.3-11-4.3-15.2 0-4.3 4.2-4.3 11 0 15.2z\"><\/path><path d=\"m11.4 15.9v-3.3h-3.3c-0.3 0-0.6-0.3-0.6-0.6 0-0.4 0.3-0.6 0.6-0.6h3.3v-3.3c0-0.3 0.3-0.6 0.6-0.6 0.3 0 0.6 0.3 0.6 0.6v3.3h3.3c0.3 0 0.6 0.2 0.6 0.6q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2h-3.3v3.3q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2c-0.4 0-0.6-0.3-0.6-0.6z\"><\/path><\/svg> <\/div><div class=\"esab__expand\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m12 24c-6.6 0-12-5.4-12-12 0-6.6 5.4-12 12-12 6.6 0 12 5.4 12 12 0 6.6-5.4 12-12 12zm10.6-12c0-5.9-4.7-10.6-10.6-10.6-5.9 0-10.6 4.7-10.6 10.6 0 5.9 4.7 10.6 10.6 10.6 5.9 0 10.6-4.7 10.6-10.6z\"><\/path><path d=\"m5.6 11.3h12.8v1.4h-12.8z\"><\/path><\/svg> <\/div><\/div><\/div><div class=\"esab__body\">\n<p class=\"wp-block-paragraph\">High-volume, low-complexity requests such as order-status questions, password and access guidance, product and service FAQs, and standard troubleshooting are well suited to automation, provided clear processes and knowledge already exist.<\/p>\n<\/div><\/div>\n\n\n\n<div class=\"wp-block-esab-accordion-child\"><div class=\"esab__head\" role=\"button\" aria-expanded=\"false\"><div class=\"esab__heading_txt\"><p class=\"esab__heading_tag\"><strong>Can Agentforce create Salesforce cases automatically?<\/strong><\/p><\/div><div class=\"esab__icon\"><div class=\"esab__collapse\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m3.5 20.5c-4.7-4.7-4.7-12.3 0-17 4.7-4.7 12.3-4.7 17 0 4.6 4.7 4.6 12.3 0 17-4.7 4.6-12.3 4.6-17 0zm0.9-0.9c4.2 4.2 11 4.2 15.2 0 4.2-4.2 4.2-11 0-15.2-4.2-4.3-11-4.3-15.2 0-4.3 4.2-4.3 11 0 15.2z\"><\/path><path d=\"m11.4 15.9v-3.3h-3.3c-0.3 0-0.6-0.3-0.6-0.6 0-0.4 0.3-0.6 0.6-0.6h3.3v-3.3c0-0.3 0.3-0.6 0.6-0.6 0.3 0 0.6 0.3 0.6 0.6v3.3h3.3c0.3 0 0.6 0.2 0.6 0.6q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2h-3.3v3.3q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2c-0.4 0-0.6-0.3-0.6-0.6z\"><\/path><\/svg> <\/div><div class=\"esab__expand\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m12 24c-6.6 0-12-5.4-12-12 0-6.6 5.4-12 12-12 6.6 0 12 5.4 12 12 0 6.6-5.4 12-12 12zm10.6-12c0-5.9-4.7-10.6-10.6-10.6-5.9 0-10.6 4.7-10.6 10.6 0 5.9 4.7 10.6 10.6 10.6 5.9 0 10.6-4.7 10.6-10.6z\"><\/path><path d=\"m5.6 11.3h12.8v1.4h-12.8z\"><\/path><\/svg> <\/div><\/div><\/div><div class=\"esab__body\">\n<p class=\"wp-block-paragraph\">Yes. When a request needs human investigation, Agentforce can collect the relevant details, create a properly categorized case, route it according to configured rules, and confirm next steps to the customer.<\/p>\n<\/div><\/div>\n\n\n\n<div class=\"wp-block-esab-accordion-child\"><div class=\"esab__head\" role=\"button\" aria-expanded=\"false\"><div class=\"esab__heading_txt\"><p class=\"esab__heading_tag\"><strong>Can Agentforce access customer information?<\/strong><\/p><\/div><div class=\"esab__icon\"><div class=\"esab__collapse\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m3.5 20.5c-4.7-4.7-4.7-12.3 0-17 4.7-4.7 12.3-4.7 17 0 4.6 4.7 4.6 12.3 0 17-4.7 4.6-12.3 4.6-17 0zm0.9-0.9c4.2 4.2 11 4.2 15.2 0 4.2-4.2 4.2-11 0-15.2-4.2-4.3-11-4.3-15.2 0-4.3 4.2-4.3 11 0 15.2z\"><\/path><path d=\"m11.4 15.9v-3.3h-3.3c-0.3 0-0.6-0.3-0.6-0.6 0-0.4 0.3-0.6 0.6-0.6h3.3v-3.3c0-0.3 0.3-0.6 0.6-0.6 0.3 0 0.6 0.3 0.6 0.6v3.3h3.3c0.3 0 0.6 0.2 0.6 0.6q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2h-3.3v3.3q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2c-0.4 0-0.6-0.3-0.6-0.6z\"><\/path><\/svg> <\/div><div class=\"esab__expand\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m12 24c-6.6 0-12-5.4-12-12 0-6.6 5.4-12 12-12 6.6 0 12 5.4 12 12 0 6.6-5.4 12-12 12zm10.6-12c0-5.9-4.7-10.6-10.6-10.6-5.9 0-10.6 4.7-10.6 10.6 0 5.9 4.7 10.6 10.6 10.6 5.9 0 10.6-4.7 10.6-10.6z\"><\/path><path d=\"m5.6 11.3h12.8v1.4h-12.8z\"><\/path><\/svg> <\/div><\/div><\/div><div class=\"esab__body\">\n<p class=\"wp-block-paragraph\">Agentforce can access Salesforce CRM data and connected systems within the permissions an organization configures, ensuring it only sees and uses the information relevant to its authorized use cases. For account-specific requests, it verifies the customer&#8217;s identity first.<\/p>\n<\/div><\/div>\n\n\n\n<div class=\"wp-block-esab-accordion-child\"><div class=\"esab__head\" role=\"button\" aria-expanded=\"false\"><div class=\"esab__heading_txt\"><p class=\"esab__heading_tag\"><strong>How does Agentforce verify a customer&#8217;s identity?<\/strong><\/p><\/div><div class=\"esab__icon\"><div class=\"esab__collapse\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m3.5 20.5c-4.7-4.7-4.7-12.3 0-17 4.7-4.7 12.3-4.7 17 0 4.6 4.7 4.6 12.3 0 17-4.7 4.6-12.3 4.6-17 0zm0.9-0.9c4.2 4.2 11 4.2 15.2 0 4.2-4.2 4.2-11 0-15.2-4.2-4.3-11-4.3-15.2 0-4.3 4.2-4.3 11 0 15.2z\"><\/path><path d=\"m11.4 15.9v-3.3h-3.3c-0.3 0-0.6-0.3-0.6-0.6 0-0.4 0.3-0.6 0.6-0.6h3.3v-3.3c0-0.3 0.3-0.6 0.6-0.6 0.3 0 0.6 0.3 0.6 0.6v3.3h3.3c0.3 0 0.6 0.2 0.6 0.6q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2h-3.3v3.3q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2c-0.4 0-0.6-0.3-0.6-0.6z\"><\/path><\/svg> <\/div><div class=\"esab__expand\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m12 24c-6.6 0-12-5.4-12-12 0-6.6 5.4-12 12-12 6.6 0 12 5.4 12 12 0 6.6-5.4 12-12 12zm10.6-12c0-5.9-4.7-10.6-10.6-10.6-5.9 0-10.6 4.7-10.6 10.6 0 5.9 4.7 10.6 10.6 10.6 5.9 0 10.6-4.7 10.6-10.6z\"><\/path><path d=\"m5.6 11.3h12.8v1.4h-12.8z\"><\/path><\/svg> <\/div><\/div><\/div><div class=\"esab__body\">\n<p class=\"wp-block-paragraph\">Through Salesforce&#8217;s standard Customer Verification sub-agent. It sends a one-time code to the customer&#8217;s email address and unlocks protected actions only after the customer enters the correct code.<\/p>\n<\/div><\/div>\n\n\n\n<div class=\"wp-block-esab-accordion-child\"><div class=\"esab__head\" role=\"button\" aria-expanded=\"false\"><div class=\"esab__heading_txt\"><p class=\"esab__heading_tag\"><strong>How does Agentforce escalate a ticket to a human?<\/strong><\/p><\/div><div class=\"esab__icon\"><div class=\"esab__collapse\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m3.5 20.5c-4.7-4.7-4.7-12.3 0-17 4.7-4.7 12.3-4.7 17 0 4.6 4.7 4.6 12.3 0 17-4.7 4.6-12.3 4.6-17 0zm0.9-0.9c4.2 4.2 11 4.2 15.2 0 4.2-4.2 4.2-11 0-15.2-4.2-4.3-11-4.3-15.2 0-4.3 4.2-4.3 11 0 15.2z\"><\/path><path d=\"m11.4 15.9v-3.3h-3.3c-0.3 0-0.6-0.3-0.6-0.6 0-0.4 0.3-0.6 0.6-0.6h3.3v-3.3c0-0.3 0.3-0.6 0.6-0.6 0.3 0 0.6 0.3 0.6 0.6v3.3h3.3c0.3 0 0.6 0.2 0.6 0.6q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2h-3.3v3.3q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2c-0.4 0-0.6-0.3-0.6-0.6z\"><\/path><\/svg> <\/div><div class=\"esab__expand\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m12 24c-6.6 0-12-5.4-12-12 0-6.6 5.4-12 12-12 6.6 0 12 5.4 12 12 0 6.6-5.4 12-12 12zm10.6-12c0-5.9-4.7-10.6-10.6-10.6-5.9 0-10.6 4.7-10.6 10.6 0 5.9 4.7 10.6 10.6 10.6 5.9 0 10.6-4.7 10.6-10.6z\"><\/path><path d=\"m5.6 11.3h12.8v1.4h-12.8z\"><\/path><\/svg> <\/div><\/div><\/div><div class=\"esab__body\">\n<p class=\"wp-block-paragraph\">When a request falls outside its defined scope or an escalation rule is triggered, Agentforce transfers the conversation to a human agent through Omni-Channel routing, along with the relevant context, so the customer does not need to repeat information.<\/p>\n<\/div><\/div>\n\n\n\n<div class=\"wp-block-esab-accordion-child\"><div class=\"esab__head\" role=\"button\" aria-expanded=\"false\"><div class=\"esab__heading_txt\"><p class=\"esab__heading_tag\"><strong>Is Agentforce suitable for complex technical support?<\/strong><\/p><\/div><div class=\"esab__icon\"><div class=\"esab__collapse\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m3.5 20.5c-4.7-4.7-4.7-12.3 0-17 4.7-4.7 12.3-4.7 17 0 4.6 4.7 4.6 12.3 0 17-4.7 4.6-12.3 4.6-17 0zm0.9-0.9c4.2 4.2 11 4.2 15.2 0 4.2-4.2 4.2-11 0-15.2-4.2-4.3-11-4.3-15.2 0-4.3 4.2-4.3 11 0 15.2z\"><\/path><path d=\"m11.4 15.9v-3.3h-3.3c-0.3 0-0.6-0.3-0.6-0.6 0-0.4 0.3-0.6 0.6-0.6h3.3v-3.3c0-0.3 0.3-0.6 0.6-0.6 0.3 0 0.6 0.3 0.6 0.6v3.3h3.3c0.3 0 0.6 0.2 0.6 0.6q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2h-3.3v3.3q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2c-0.4 0-0.6-0.3-0.6-0.6z\"><\/path><\/svg> <\/div><div class=\"esab__expand\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m12 24c-6.6 0-12-5.4-12-12 0-6.6 5.4-12 12-12 6.6 0 12 5.4 12 12 0 6.6-5.4 12-12 12zm10.6-12c0-5.9-4.7-10.6-10.6-10.6-5.9 0-10.6 4.7-10.6 10.6 0 5.9 4.7 10.6 10.6 10.6 5.9 0 10.6-4.7 10.6-10.6z\"><\/path><path d=\"m5.6 11.3h12.8v1.4h-12.8z\"><\/path><\/svg> <\/div><\/div><\/div><div class=\"esab__body\">\n<p class=\"wp-block-paragraph\">Complex, judgment-heavy technical issues are generally better handled by human agents. Agentforce is best suited to well-documented, lower-complexity troubleshooting, with escalation built in for anything more involved.<\/p>\n<\/div><\/div>\n\n\n\n<div class=\"wp-block-esab-accordion-child\"><div class=\"esab__head\" role=\"button\" aria-expanded=\"false\"><div class=\"esab__heading_txt\"><p class=\"esab__heading_tag\"><strong>Can Agentforce integrate with ERP systems?<\/strong><\/p><\/div><div class=\"esab__icon\"><div class=\"esab__collapse\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m3.5 20.5c-4.7-4.7-4.7-12.3 0-17 4.7-4.7 12.3-4.7 17 0 4.6 4.7 4.6 12.3 0 17-4.7 4.6-12.3 4.6-17 0zm0.9-0.9c4.2 4.2 11 4.2 15.2 0 4.2-4.2 4.2-11 0-15.2-4.2-4.3-11-4.3-15.2 0-4.3 4.2-4.3 11 0 15.2z\"><\/path><path d=\"m11.4 15.9v-3.3h-3.3c-0.3 0-0.6-0.3-0.6-0.6 0-0.4 0.3-0.6 0.6-0.6h3.3v-3.3c0-0.3 0.3-0.6 0.6-0.6 0.3 0 0.6 0.3 0.6 0.6v3.3h3.3c0.3 0 0.6 0.2 0.6 0.6q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2h-3.3v3.3q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2c-0.4 0-0.6-0.3-0.6-0.6z\"><\/path><\/svg> <\/div><div class=\"esab__expand\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m12 24c-6.6 0-12-5.4-12-12 0-6.6 5.4-12 12-12 6.6 0 12 5.4 12 12 0 6.6-5.4 12-12 12zm10.6-12c0-5.9-4.7-10.6-10.6-10.6-5.9 0-10.6 4.7-10.6 10.6 0 5.9 4.7 10.6 10.6 10.6 5.9 0 10.6-4.7 10.6-10.6z\"><\/path><path d=\"m5.6 11.3h12.8v1.4h-12.8z\"><\/path><\/svg> <\/div><\/div><\/div><div class=\"esab__body\">\n<p class=\"wp-block-paragraph\">Yes. Agentforce can be configured to retrieve information from connected enterprise systems, including ERP platforms, where appropriate integration and access controls are in place.<\/p>\n<\/div><\/div>\n\n\n\n<div class=\"wp-block-esab-accordion-child\"><div class=\"esab__head\" role=\"button\" aria-expanded=\"false\"><div class=\"esab__heading_txt\"><p class=\"esab__heading_tag\"><strong>Does Agentforce require Data 360?<\/strong><\/p><\/div><div class=\"esab__icon\"><div class=\"esab__collapse\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m3.5 20.5c-4.7-4.7-4.7-12.3 0-17 4.7-4.7 12.3-4.7 17 0 4.6 4.7 4.6 12.3 0 17-4.7 4.6-12.3 4.6-17 0zm0.9-0.9c4.2 4.2 11 4.2 15.2 0 4.2-4.2 4.2-11 0-15.2-4.2-4.3-11-4.3-15.2 0-4.3 4.2-4.3 11 0 15.2z\"><\/path><path d=\"m11.4 15.9v-3.3h-3.3c-0.3 0-0.6-0.3-0.6-0.6 0-0.4 0.3-0.6 0.6-0.6h3.3v-3.3c0-0.3 0.3-0.6 0.6-0.6 0.3 0 0.6 0.3 0.6 0.6v3.3h3.3c0.3 0 0.6 0.2 0.6 0.6q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2h-3.3v3.3q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2c-0.4 0-0.6-0.3-0.6-0.6z\"><\/path><\/svg> <\/div><div class=\"esab__expand\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m12 24c-6.6 0-12-5.4-12-12 0-6.6 5.4-12 12-12 6.6 0 12 5.4 12 12 0 6.6-5.4 12-12 12zm10.6-12c0-5.9-4.7-10.6-10.6-10.6-5.9 0-10.6 4.7-10.6 10.6 0 5.9 4.7 10.6 10.6 10.6 5.9 0 10.6-4.7 10.6-10.6z\"><\/path><path d=\"m5.6 11.3h12.8v1.4h-12.8z\"><\/path><\/svg> <\/div><\/div><\/div><div class=\"esab__body\">\n<p class=\"wp-block-paragraph\">Answering questions from knowledge articles uses an Agentforce Data Library, which runs on Data 360 (formerly Data Cloud), so Data 360 must be enabled. Confirm licensing requirements with Salesforce or your implementation partner.<\/p>\n<\/div><\/div>\n\n\n\n<div class=\"wp-block-esab-accordion-child\"><div class=\"esab__head\" role=\"button\" aria-expanded=\"false\"><div class=\"esab__heading_txt\"><p class=\"esab__heading_tag\"><strong>How do companies measure Agentforce ROI?<\/strong><\/p><\/div><div class=\"esab__icon\"><div class=\"esab__collapse\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m3.5 20.5c-4.7-4.7-4.7-12.3 0-17 4.7-4.7 12.3-4.7 17 0 4.6 4.7 4.6 12.3 0 17-4.7 4.6-12.3 4.6-17 0zm0.9-0.9c4.2 4.2 11 4.2 15.2 0 4.2-4.2 4.2-11 0-15.2-4.2-4.3-11-4.3-15.2 0-4.3 4.2-4.3 11 0 15.2z\"><\/path><path d=\"m11.4 15.9v-3.3h-3.3c-0.3 0-0.6-0.3-0.6-0.6 0-0.4 0.3-0.6 0.6-0.6h3.3v-3.3c0-0.3 0.3-0.6 0.6-0.6 0.3 0 0.6 0.3 0.6 0.6v3.3h3.3c0.3 0 0.6 0.2 0.6 0.6q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2h-3.3v3.3q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2c-0.4 0-0.6-0.3-0.6-0.6z\"><\/path><\/svg> <\/div><div class=\"esab__expand\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m12 24c-6.6 0-12-5.4-12-12 0-6.6 5.4-12 12-12 6.6 0 12 5.4 12 12 0 6.6-5.4 12-12 12zm10.6-12c0-5.9-4.7-10.6-10.6-10.6-5.9 0-10.6 4.7-10.6 10.6 0 5.9 4.7 10.6 10.6 10.6 5.9 0 10.6-4.7 10.6-10.6z\"><\/path><path d=\"m5.6 11.3h12.8v1.4h-12.8z\"><\/path><\/svg> <\/div><\/div><\/div><div class=\"esab__body\">\n<p class=\"wp-block-paragraph\">Common measures include automated resolution rate, escalation rate, first-response time, average handling time, cost per interaction, and customer satisfaction, tracked together rather than in isolation. Factor in Agentforce&#8217;s usage-based pricing too, since cost per interaction depends on how many actions each conversation uses.<\/p>\n<\/div><\/div>\n\n\n\n<div class=\"wp-block-esab-accordion-child\"><div class=\"esab__head\" role=\"button\" aria-expanded=\"false\"><div class=\"esab__heading_txt\"><p class=\"esab__heading_tag\"><strong>What data does Agentforce need to automate Tier-1 support?<\/strong><\/p><\/div><div class=\"esab__icon\"><div class=\"esab__collapse\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m3.5 20.5c-4.7-4.7-4.7-12.3 0-17 4.7-4.7 12.3-4.7 17 0 4.6 4.7 4.6 12.3 0 17-4.7 4.6-12.3 4.6-17 0zm0.9-0.9c4.2 4.2 11 4.2 15.2 0 4.2-4.2 4.2-11 0-15.2-4.2-4.3-11-4.3-15.2 0-4.3 4.2-4.3 11 0 15.2z\"><\/path><path d=\"m11.4 15.9v-3.3h-3.3c-0.3 0-0.6-0.3-0.6-0.6 0-0.4 0.3-0.6 0.6-0.6h3.3v-3.3c0-0.3 0.3-0.6 0.6-0.6 0.3 0 0.6 0.3 0.6 0.6v3.3h3.3c0.3 0 0.6 0.2 0.6 0.6q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2h-3.3v3.3q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2c-0.4 0-0.6-0.3-0.6-0.6z\"><\/path><\/svg> <\/div><div class=\"esab__expand\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m12 24c-6.6 0-12-5.4-12-12 0-6.6 5.4-12 12-12 6.6 0 12 5.4 12 12 0 6.6-5.4 12-12 12zm10.6-12c0-5.9-4.7-10.6-10.6-10.6-5.9 0-10.6 4.7-10.6 10.6 0 5.9 4.7 10.6 10.6 10.6 5.9 0 10.6-4.7 10.6-10.6z\"><\/path><path d=\"m5.6 11.3h12.8v1.4h-12.8z\"><\/path><\/svg> <\/div><\/div><\/div><div class=\"esab__body\">\n<p class=\"wp-block-paragraph\">Accurate, current knowledge articles and reliable CRM data covering customer records, product information, and service or case history are the foundation for dependable automation, with Data 360 indexing that knowledge for the agent.<\/p>\n<\/div><\/div>\n\n\n\n<div class=\"wp-block-esab-accordion-child\"><div class=\"esab__head\" role=\"button\" aria-expanded=\"false\"><div class=\"esab__heading_txt\"><p class=\"esab__heading_tag\"><strong>How can businesses prevent incorrect AI responses?<\/strong><\/p><\/div><div class=\"esab__icon\"><div class=\"esab__collapse\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m3.5 20.5c-4.7-4.7-4.7-12.3 0-17 4.7-4.7 12.3-4.7 17 0 4.6 4.7 4.6 12.3 0 17-4.7 4.6-12.3 4.6-17 0zm0.9-0.9c4.2 4.2 11 4.2 15.2 0 4.2-4.2 4.2-11 0-15.2-4.2-4.3-11-4.3-15.2 0-4.3 4.2-4.3 11 0 15.2z\"><\/path><path d=\"m11.4 15.9v-3.3h-3.3c-0.3 0-0.6-0.3-0.6-0.6 0-0.4 0.3-0.6 0.6-0.6h3.3v-3.3c0-0.3 0.3-0.6 0.6-0.6 0.3 0 0.6 0.3 0.6 0.6v3.3h3.3c0.3 0 0.6 0.2 0.6 0.6q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2h-3.3v3.3q0 0.2-0.2 0.4-0.2 0.2-0.4 0.2c-0.4 0-0.6-0.3-0.6-0.6z\"><\/path><\/svg> <\/div><div class=\"esab__expand\"> <svg version=\"1.2\" viewBox=\"0 0 24 24\" width=\"24\" height=\"24\"><path fill-rule=\"evenodd\" d=\"m12 24c-6.6 0-12-5.4-12-12 0-6.6 5.4-12 12-12 6.6 0 12 5.4 12 12 0 6.6-5.4 12-12 12zm10.6-12c0-5.9-4.7-10.6-10.6-10.6-5.9 0-10.6 4.7-10.6 10.6 0 5.9 4.7 10.6 10.6 10.6 5.9 0 10.6-4.7 10.6-10.6z\"><\/path><path d=\"m5.6 11.3h12.8v1.4h-12.8z\"><\/path><\/svg> <\/div><\/div><\/div><div class=\"esab__body\">\n<p class=\"wp-block-paragraph\">Maintaining current knowledge content, defining clear permissions and escalation rules, testing thoroughly before launch, and continuously monitoring live conversations all help reduce the risk of incorrect responses.<\/p>\n<\/div><\/div>\n<\/div><\/div>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Ready_to_Explore_Agentforce_for_Your_Customer_Service_Operations\"><\/span><strong>Ready to Explore Agentforce for Your Customer Service Operations?<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Dhruvsoft helps businesses assess Tier-1 support opportunities, design Agentforce use cases, integrate Salesforce data, establish governance, and deploy AI-powered service workflows. As a Salesforce Crest Partner, we&#8217;ll help you identify where Agentforce fits into your service strategy.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.dhruvsoft.com\/blog\/contact-us\/\" target=\"_blank\" rel=\"noopener\">Book an Agentforce Readiness Assessment<\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"About_Dhruvsoft\"><\/span><strong>About Dhruvsoft<\/strong>\u00a0\u00a0\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Dhruvsoft is a Salesforce Crest Partner with 15+ years in business, 200+ Salesforce projects delivered and 50+ certified consultants. We serve 100+ clients across seven industries through a global delivery model. Our services span <a href=\"https:\/\/www.dhruvsoft.com\/agentforce-implementation-services\/\" target=\"_blank\" rel=\"noopener\">Salesforce implementation<\/a>, Agentforce, <a href=\"https:\/\/www.dhruvsoft.com\/salesforce-marketing-cloud\/\" target=\"_blank\" rel=\"noopener\">Marketing Cloud<\/a>, CPQ, Health Cloud and managed services, alongside Oracle NetSuite and Zoho practices. Dhruvsoft is ISO 9001 and ISO 27001 certified.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Opportunity to Automate Tier-1 Customer Support\u00a0\u00a0\u00a0 Customer service teams spend a large share of their day on the same handful of requests: password resets, order-status questions, plan and billing FAQs, basic account updates, and routine troubleshooting. None of these require deep expertise, yet each one still takes an agent&#8217;s time to read, look up, [&hellip;]<\/p>\n","protected":false},"author":36,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[187],"tags":[],"class_list":["post-1647","post","type-post","status-publish","format-standard","hentry","category-salesforce","entry"],"_links":{"self":[{"href":"https:\/\/www.dhruvsoft.com\/blog\/wp-json\/wp\/v2\/posts\/1647","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dhruvsoft.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dhruvsoft.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dhruvsoft.com\/blog\/wp-json\/wp\/v2\/users\/36"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dhruvsoft.com\/blog\/wp-json\/wp\/v2\/comments?post=1647"}],"version-history":[{"count":0,"href":"https:\/\/www.dhruvsoft.com\/blog\/wp-json\/wp\/v2\/posts\/1647\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dhruvsoft.com\/blog\/wp-json\/wp\/v2\/media?parent=1647"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dhruvsoft.com\/blog\/wp-json\/wp\/v2\/categories?post=1647"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dhruvsoft.com\/blog\/wp-json\/wp\/v2\/tags?post=1647"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}