Web-to-Case In Salesforce

-

Creating a Web-to-Case form in Salesforce enables you to automatically convert customer inquiries submitted through your website into cases within your Salesforce.

Turn On and Customize Web-to-Case

Generate and Test Your Web-to-Case Form

To test the Web-to-Case form, add the line <input type="hidden" name="debug" value="1"> to the code. This line redirects you to a debugging page when you submit the form. Don’t forget to remove it before publishing the Web-to-Case page on your website.

Web-to-Case Limits

5,000 cases in a 24-hour period. When you reach the 24-hour limit, additional requests are stored in a pending request queue that contains both Web-to-Case and Web-to-Lead requests

Unsupported Content Types

Web-to-Case forms don’t support the following content types:

  • Attachments
  • Rich text area (RTA) fields—If you use these fields on your forms, any information entered in them is saved as plain text when the case is created.
  • Multipart/form-data—Cases aren’t created for forms that use this content type.
  • Script tags—When script tags are submitted in Web-to-Case forms, the tags are saved as plain text in the case details.


Here are the steps to follow 




















Here's a simple example of what the HTML code for the Web-to-Case form might look like:

<form action="https://www.salesforce.com/servlet/servlet.WebToCase?encoding=UTF-8" method="POST">
  <input type=hidden name="orgid" value="00DXXXXXXXXXXXX">
  <input type=hidden name="retURL" value="https://salesforceplayground.blogspot.com/thankyou">
  <label for="name">Name</label>
  <input id="name" maxlength="80" name="name" size="20" type="text" required /><br>
  <label for="email">Email</label>
  <input id="email" maxlength="80" name="email" size="20" type="email" required /><br>
  <label for="subject">Subject</label>
  <input id="subject" maxlength="80" name="subject" size="20" type="text" required /><br>
  <label for="description">Description</label><br>
  <textarea id="description" name="description" rows="4" cols="50" required></textarea><br>
  <input type="submit" name="submit">

</form>

Replace "00DXXXXXXXXXXXX" with your Salesforce organization ID.

Replace "https://salesforceplayground.blogspot.com/thankyou" with the URL of the page where you want to redirect users after they submit the form.

This form includes fields for Name, Email, Subject, and Description. You can customize it by adding or removing fields as needed. When a user submits the form, a new case will be created in Salesforce with the provided information.


Comments

Post a Comment

Popular posts from this blog

Introduction to Salesforce Agent Script: Build Predictable AI Agents

-
Image
Please visit here for more details - https://ayaninsights.com/guestblogs/introduction-to-agent-script/ In my latest blog, I introduce Salesforce Agent Script and explain how it helps teams build AI agents that are more predictable, controlled, and aligned with business processes. Large language models are flexible, but relying only on natural-language instructions can sometimes produce inconsistent results. Agent Script addresses this challenge by combining the conversational capabilities of an LLM with structured business logic. The blog explains how developers can use conditions, variables, actions, topics, and transitions to control how an Agentforce agent behaves. Agent Script supports familiar logic such as if/else conditions, value comparisons, sequential actions, and checks for missing data. I also cover its core structure, including system settings, configuration, global variables, languages, connections, and topic blocks. The start_agent topic acts as the entry point for each...
Read more

Anti-Patterns in Salesforce Agentforce: What to Avoid When Building AI Agents

-
Image
Salesforce Agentforce is powerful because it allows teams to build AI agents that can understand user intent, retrieve grounded information, execute actions, and support business workflows across Salesforce. But like any powerful platform, the quality of the implementation matters. A good Agentforce implementation does not start with “How many things can the agent do?" It starts with “What problem should the agent solve reliably?” That is where anti-patterns come in. Anti-patterns are common implementation habits that look useful at first but eventually create confusion, poor user experience, inconsistent answers, or hard-to-maintain agents. Below are some of the most common Agentforce anti-patterns and how to avoid them. 1. Trying to Build One Agent That Does Everything One of the biggest mistakes is designing a single agent to handle every business process, every department, and every possible customer question. At first, this feels efficient. One agent, many use cases. Bu...
Read more

MCP vs. Traditional APIs: Choosing the Right Integration Approach

-
Image
Enterprise integration has traditionally been built around APIs. Applications send structured requests, services process them, and predictable responses are returned. This model has supported everything from payment processing and customer portals to mobile applications and large-scale system integrations. The rise of AI agents introduces a different integration challenge. An AI agent does not always follow a fixed sequence designed in advance. It may need to determine which system to use, discover the operations available to it, gather relevant context, and select the appropriate action based on a user’s request. This is where the Model Context Protocol, or MCP, becomes relevant. MCP and traditional APIs are related, but they solve different problems. APIs expose system capabilities. MCP provides a standardized way for AI applications to discover and use those capabilities as tools and contextual resources. Understanding this distinction is important when designing enterprise AI solut...
Read more