---
title: "Discussion on \"Web-to-Case and the customer self-service portal\" | Hashnode"
description: "Discussion on \"Web-to-Case and the customer self-service portal\". Web-to-Case is the cheapest way to start taking cases from a public site, but it quietly invites spam and breaks the moment customers want to track their own tickets. Here's how I decide between a Web-to-Case form, a direct API, and a full"
url: "https://hashnode.com/posts/web-to-case-and-the-customer-self-service-portal/6a53c4461946f24922609686"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Web-to-Case and the customer self-service portal](https://sapotacorpvn.hashnode.dev/web-to-case-and-the-customer-self-service-portal?utm_source=hashnode&utm_medium=feed)

Web-to-Case is the cheapest way to start taking cases from a public site, but it quietly invites spam and breaks the moment customers want to track their own tickets. Here's how I decide between a Web-to-Case form, a direct API, and a full

Jul 12 · 10 min read · sapotacorpvn.hashnode.dev  
Read the article

-   [#salesforce](https://hashnode.com/tag/salesforce)
-   [#service-cloud](https://hashnode.com/tag/service-cloud)
-   [#crm](https://hashnode.com/tag/crm)
-   [#web-to-case](https://hashnode.com/tag/web-to-case)
-   [#experience-cloud](https://hashnode.com/tag/experience-cloud)

## Written by

[SapotaCorp](https://hashnode.com/@sapotacorpvn)

@sapotacorpvn · Hanoi, Vietnam

  
[View profile](https://hashnode.com/@sapotacorpvn)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
