Web-to-Case Overview. Best Practices. Tom Muskatevc Success Account Manager

Similar documents
Set Up and Maintain Customer Support Tools

Chatter Answers Implementation Guide

Chatter Answers Implementation Guide

Salesforce Lead Management Implementation Guide

Salesforce Customer Portal Implementation Guide

Case Management Implementation Guide

Case Management Implementation Guide

Identity Implementation Guide

Self-Service Portal Implementation Guide

Complete Guide to Salesforce Knowledge

Veeam MarketReach User Guide. Automate Your Marketing. Grow Your Business.

Salesforce Knowledge Implementation Guide

Force.com Sites Implementation Guide

Salesforce Winter 15 Release Notes

Using Form Tools (admin)

Answers Implementation Guide

ISVforce Guide. Version 35.0, Winter

Okta Identity Management for Portals Built on Salesforce.com. An Architecture Review. Okta Inc. 301 Brannan Street San Francisco, CA 94107

License Management and Support Guide

SpringCM Troubleshooting Guide for Salesforce

Software Version 1.0 ConnectKey TM Share to Cloud April Xerox ConnectKey Share to Cloud User / Administrator s Guide

Mojo Surveys 2.6 Getting Started Guide

Sage Integration Cloud Technology Whitepaper

SpringCM Integration Guide. for Salesforce

How To Use Salesforce Identity Features

Nintex Workflow 2013 & InfoPath Form Design workshop

Creating a Public Knowledge Base with Salesforce Knowledge

List Service Customizing a List. Introduction. Adding an Owner or Moderator. Process Summary Introduction. Adding an Owner or Moderator

Jive Case Escalation for Salesforce

Microsoft Exchange ActiveSync Administrator s Guide

Salesforce Opportunities Portlet Documentation v2

Microsoft SharePoint Products & Technologies

Setting Up Person Accounts

Chapter 15: Forms. User Guide. 1 P a g e

SpringCM Integration Guide. for Salesforce

ServiceDesk Plus On-Demand QUICK START GUIDE

3dCart Shopping Cart Software Release Notes Version 3.0

Brock University Content Management System Training Guide

For details about using automatic user provisioning with Salesforce, see Configuring user provisioning for Salesforce.

License Management App 2.1 Administration and User Guide

Configuring Salesforce

The Cloud ERP. Case Study JAAS

Successful Platform-as-a-Service Requires a Supporting Ecosystem for HR Applications

ServiceDesk Plus On-Demand Comparison Document ServiceDesk Plus v8 vs ServiceDesk Plus On- Demand ENTERPRISE VERSIONS

TABLE OF CONTENTS. avaya.com

Microsoft PPM for Application Administrators using Microsoft Project Online

Salesforce Bootcamp for Nonprofits Workbook

ReadyTalk for Salesforce User Guide

ONCONTACT MARKETING AND CAMPAIGN USER GUIDE V8.1

Using the ABB Supplier Inquiry Form

ONCONTACT MARKETING AND CAMPAIGN USER GUIDE V8.1

Nintex Forms 2013 Help

Rich Web Mail Quick Guide

WatchGuard QMS End User Guide

Integrating LivePerson with Salesforce

Setting Up Person Accounts

Customer Support Services

Salesforce Admin Course Content: Chapter 1 CRM Introduction Introduction to CRM? Why CRM?

What s New Guide. Help Desk Authority 9.1

Volunteers for Salesforce Installation & Configuration Guide Version 3.76

Integration Guide. SafeNet Authentication Service. Using SAS as an Identity Provider for Salesforce

Eloqua Discover Frequently Asked Questions

Security Implementation Guide

Invoice Approval - Paying Invoices

UOFL SHAREPOINT ADMINISTRATORS GUIDE

The document may be freely distributed in its entirety, either digitally or in printed format, to all EPiServer Mail users.

Kaseya 2. User Guide. Version 1.1

10 principles of Not-for-profit Branding. branding marketing public relations graphic design websites advertising ecomms copywriting social media

How To Use The Intergage Bulk Facility

Volunteers for Salesforce User s Guide Version 3.5

Salesforce Classic Guide for iphone

DreamFactory Security Whitepaper Customer Information about Privacy and Security

Shasta College SharePoint Tutorial. Create an HTML Form

Report: Salesforce and Microsoft Dynamics CRM Outlook Integration Compared

Web Forms for Marketers 2.3 for Sitecore CMS 6.5 and

FastNetSecurity SpamGuard Spam Filter How-To

Getting Started With Communities

elivering CRM Success in the Cloud

WebSpy Vantage Ultimate 2.2 Web Module Administrators Guide

Form And List. SuperUsers. Configuring Moderation & Feedback Management Setti. Troubleshooting: Feedback Doesn't Send

Live Agent for Support Agents

Version /10. Xerox ColorQube 9301/9302/9303 Internet Services

Getting Started with SurveyGizmo Stage 1: Creating Your First Survey

Introduction to Ingeniux Forms Builder. 90 minute Course CMSFB-V6 P

MONITORING RED HAT GLUSTER SERVER DEPLOYMENTS With the Nagios IT infrastructure monitoring tool

SHAREPOINT COLLABORATIVE WORKSPACE

Your guide to marketing

Egnyte for Salesforce v2.1 Administrator s Guide

CB Advanced: Innovative Document Templates

OpenIMS 4.2. Document Management Server. User manual

Richmond Systems. SupportDesk Web Interface User Guide

Bulk . What s Inside this Guide. Bulk and How To Get There 2. Bulk Setup 4. Bulk Details 7

Transcription:

Overview Best Practices Tom Muskatevc Success Account Manager

Basics Gather customer support requests directly from your company s website and automatically generate up to 5,000 new cases a day with Web-to-Case. This can help your organization respond to customers faster, improving your support team s productivity. Web To Case is a means by which you can post a simple, unauthenticated web page that allows your customers to submit cases directly to your Salesforce.com instance. This means that you can post a public case submission page on your own website with your own branding and styling. Web To Case works by generating a snippet of HTML for you. This HTML is an HTML form that you can put on any page. When your customer presses Submit, the information on this form is posted directly to a Salesforce.com server, which handles the information, converts it to a case, and redirects the customer's browser back to a page of your choosing.

Basics When your customer posts a case via Web To Case, a few fields are generally required, most importantly the name and the email address. These values will be stored in the newly created Case in the Web Name and Web Email fields. If that email address happens to be associated with a Contact in your system, then Web To Case will automatically associate that case with the contact who has that email address, and with the account associated to that contact. If that email address is not found, or Web To Case discovers more than one contact with that email address, then Web To Case will not know which contact to associate to the case. In that instance, it will leave the Contact and Account fields on the case blank and allow you to fill them (which you can generally find using those Web Name and Web Email fields).

What is it useful for? Let's say that you're doing a lot of support by email. Emails are an unstructured medium, so even if you're automating the process with Email to Case, someone generally still has to look at the cases to classify them -- it's not easy to perform workflow on plain text. Web To Case allows your customers to submit the information directly into the individual fields on your case, so you can perform a great deal of automation, like workflow, assignment, and auto-response rules, immediately. That can save you a lot of man hours. Web To Case is a very quick way to put up a web form to accept cases. You can generally have a quick-and-simple page up in minutes, and because it's standard HTML, it's easy to embed into an existing page.

Prerequisites Before you set up Web-to-Case: Create custom case fields, if needed. Create a default email template for the automated notification that will be sent to your customers when they submit a case. Create case queues if you wish to assign incoming cases to queues as well as to individual users. Customize Support settings to select the default owner of cases that don t meet the criteria in your assignment rule. Create an active case assignment rule to determine how web-generated cases are assigned to users or put into queues. If you do not set an active assignment rule, all web-generated cases are assigned to the default owner you specify in the Support Settings.

Web-to-Case Notes and Limitations Keep these considerations in mind as you decide how to set up Web-to-Case. Web To Case is limited to receiving 5000 cases per day. This is to keep things like spambots from beating up your org (and our servers). Web To Case does not perform any spam filtering. To avoid receiving spam in your Web-to-Case forms you may use the following solutions: Creating validation rules. Utilizing CAPTCHA. Using Web services. to filter out cases that appear to be spam Whenever possible, Web-generated cases are automatically linked to the relevant contact and account based on the customer s email address. Salesforce runs field validation rules before creating records submitted via Web-to-Case and only creates records that have valid values. All universally required fields must have a value before a record can be created via Web-to- Case.

Web-to-Case Notes and Limitations (continued) The format for date and currency fields captured online is taken from your organization s default settings - Default Locale and Currency Locale. Salesforce doesn t support rich text area (RTA) fields on Web-to-Case forms. If you use RTA fields on your forms, any information entered in them is saved as plain text when the case is created. If your organization exceeds its daily Web-to-Case limit, the default case owner (specified in your Support Settings page) will receive an email containing the additional case information. Web To Case cannot handle attachments. This is an aspect of the simplicity of its setup, and of the simple transactional nature of HTTP. Web To Case is a simple form with a single post that you can embed anywhere. There is an idea posted on our Idea exchange and is being reviewed by our product team. Allow Web-to-Case to support Case Attachments

Web-toCase Workarounds Web To Case is solely a tool for the initial submission of cases. If your customers need to be able to track their cases, or add information to them after initial submission, then you'll want to look into the Self Service Portal or the Customer Community-- those are authenticated products that allow your customers to file cases, but also to follow up on them, browse the knowledge base, and share information in a collaborative community based upon Chatter. If you need to take more than 5000 cases per day, or you want to be able to take attachments, you can now do so using Force.com Sites. Here s a quick start on how to create Custom Web to Case Forms using VisualForce: http://wiki.developerforce.com/index.php/creating_custom_web-to-case_forms_using_visualforce_and_sites

Setup Resources and FAQs Set Up Web-to-Case What is the maximum number of web cases we can capture? Who owns new web-generated cases? How do I specify which information to capture? Can I capture cases from multiple web pages? How can our webmaster test the Web-to-Case page? What status and origin are assigned to Web-generated cases? How can I be sure that cases won't be lost? How do I avoid Web-to-Case spam?

Thank you