How can we help you?

Create a NetSuite Support Case From an After-Hours Form or a Follow-Up Choice

When no agent is available, or when a visitor picks Needs follow-up from a menu, the workflow can ask a few questions and then create a support case in NetSuite. No AI is involved. This article shows the steps and what the request needs.

This article is for Velaro Messaging (V27) with the NetSuite integration connected. To build the menu, see Build a Menu That Visitors Can Return To With Jump To: https://help.velaro.com/kb/article/1228/build-a-menu-visitors-can-return-to-with-jump-to

Before you start

  • NetSuite is connected to your Velaro site.
  • The NetSuite field mapping has a Support Case mapping. Open the mapping page and make sure the fields you want on the case have the Create card turned on.
  • Optional: the Support Case mapping can have a Default value for company, which is the NetSuite customer the case belongs to. A visitor with no customer record still gets a case without it, unless your NetSuite account makes company mandatory. See "What the request needs" below.

Steps

  1. Open the workflow and find the place where the visitor has no agent.
  • For after hours or no agent: add a Route to Team step, turn on Check availability, and use its Unavailable and After Hours branches.
  • For a menu choice: use the steps under your Needs follow-up choice.
  1. Add Ask Question steps for what you want to capture, for example the visitor's name, email and a short description of the problem. For each one, save the answer as a workflow variable, and note the variable name.
  2. Add an HTTP Request step after the questions.
  • Method: POST.
  • Url: your Velaro Messaging API address followed by /NetSuite/CreateSupportCaseFromWorkflow.
  • Headers: add Content-Type with the value application/json.
  • Body: JSON that uses your variables. The example below sends only a title.
  • Turn on Wait for response, and connect the error branch to a message such as "We could not log your request".
  1. Add a Send Message step that tells the visitor the request is logged, then a Jump to step back to the menu.
  2. Publish the workflow.

Example body, where issueSummary is the variable saved by the question about the problem:

{ "title": "<<issueSummary>>" }

Velaro adds the required jobId to the request for you. It identifies the conversation, so Velaro knows which site and which NetSuite connection to use. You do not type it.

What the request needs

The case is made from the fields marked Create in your Support Case mapping. For each of those fields, Velaro takes the value from:

  1. The request body, where the name matches the NetSuite field name.
  2. A conversation property with the same name.
  3. The Default value in the mapping.

One field is required: title, the case subject, which comes from your body. Company is the NetSuite customer record. It is optional, so a visitor who is not a NetSuite customer still gets a case. If you want every such case to land on one general customer, set a Default value for company in the mapping. If your NetSuite account requires company, NetSuite refuses the case without it, and the request answers with an error so your workflow can take its error branch.

Add any other field in the body only if it is in the Support Case mapping with Create on. Fields that are not in the mapping are ignored.

Check that it worked

The request answers success even when NetSuite or the mapping refuses the case. After a test:

  1. Check whether the HTTP Request step took its error branch. A refused or failed case answers with an error status, not success.
  2. Open the NetSuite Activity Log in Velaro and look for an entry such as "Missing or empty required field(s)".
  3. Open the case in NetSuite and check the title and company.

Test with a site you use for testing, not a customer site.

Related articles

  • Build a Menu That Visitors Can Return To With Jump To: https://help.velaro.com/kb/article/1228/build-a-menu-visitors-can-return-to-with-jump-to
  • AI-Free Menu Workflows Compared With AI Routing: https://help.velaro.com/kb/article/1237/ai-free-menu-workflows-compared-with-ai-routing
Share: Email

Was this article helpful?