NetSuite AI Skills — Customer Pitch & Competitive Positioning

Use this document when pitching the NetSuite integration to prospects, responding to RFPs, or handling the objection "can't I just use HTTP nodes?"

---

The core pitch in two sentences

Velaro gives your chatbot 33 pre-built NetSuite operations — order lookups, case creation, invoice history, RMAs, inventory checks — that the AI selects dynamically based on what the customer says. You paste 5 OAuth credentials once. You never touch an API spec, a workflow branch, or an HTTP node.

---

What the customer used to have to do (the problem)

Before AI Skills, connecting any chatbot to NetSuite required:

• Knowing NetSuite's REST layer — endpoint URLs per record type (leads aren't at /lead, they're /customer?searchstage=Lead), field names that vary by record (one typo = silent 400 error), response schema to parse
• Building OAuth 1.0a signing — nonce, timestamp, HMAC-SHA1 signature — inside every HTTP node, re-constructed on every call
• Writing workflow branches — an if/then routing tree for every scenario: "if customer asks about order, call order endpoint; if customer asks about invoice, call invoice endpoint; if both..."
• Installing and maintaining bundles — fixed 5–10 actions from SuiteBuilder, no AI selection, breaks when NetSuite updates its schema
• Manually passing context — asking the customer for their email or account number inside the chat because the bot didn't carry it from prechat

This was a developer task. It took days to build, weeks to test, and broke regularly.

---

What Skills replaced (one by one)

Old requirement	Replaced by
Know REST endpoint URL per record type	Skill handles routing by operation name
Construct OAuth1 signature in every node	Credentials stored once, signed at execution
Guess field names (typo = silent failure)	"Discover Properties" pulls live schema from NetSuite
Build if/then routing branch per scenario	LLM reads conversation, picks skill dynamically
Ask customer for account email in chat	Prechat email threads as implicit lookup key
Install a bundle for a fixed set of actions	33 skills active immediately on connect
Re-build when NetSuite changes a field	Velaro maintains field validation

---

All 33 skills

Customer Intelligence

• netsuite_search_customer — search by email, name, or phone
• netsuite_get_customer — full profile with balance, credit limit, payment terms
• netsuite_get_customer_contacts — contacts for B2B accounts
• netsuite_get_customer_balance — financial summary (overdue, available credit)
• netsuite_update_customer — update customer fields from conversation data
• netsuite_get_subsidiaries — list active subsidiaries (OneWorld)

Order Management

• netsuite_search_orders — search by email, status, date range
• netsuite_get_order — full order with line items, shipping, totals
• netsuite_get_order_history — all historical orders for customer
• netsuite_cancel_order — cancel pre-shipment orders
• netsuite_add_order_note — add internal memo to any order

Invoicing & Payments

• netsuite_get_invoice — invoice details with payment status
• netsuite_get_open_invoices — all outstanding unpaid invoices
• netsuite_get_payment_history — payment records applied to account
• netsuite_get_credit_memos — credit memos issued
• netsuite_get_credit_memo — specific credit memo by ID

Case Management

• netsuite_create_case — create support case from conversation
• netsuite_get_cases — open and recent cases
• netsuite_update_case — change status, priority, assignment
• netsuite_add_case_note — add note to existing case

Returns & RMA

• netsuite_get_rma — RMA status and approved items
• netsuite_create_rma — create return with line items and reason code

Inventory & Products

• netsuite_search_items — search catalog by name, SKU, or category
• netsuite_check_stock — real-time inventory levels with urgency flag
• netsuite_get_item_pricing — pricing including customer-specific tiers
• netsuite_restlet — call any custom SuiteScript RESTlet

Sales & Leads

• netsuite_search_opportunities — search by customer, stage, probability
• netsuite_get_opportunity — full opportunity with deal status
• netsuite_create_quote — create estimate/quote with line items and pricing
• netsuite_create_lead — create lead from prospect conversation (field-mapped from prechat)
• netsuite_push_transcript — push full chat transcript to customer record on close

---

Handling the "can't I just use HTTP nodes?" objection

> "HTTP nodes work — we used them before."

Acknowledge it: yes, HTTP nodes work. Then pivot to what they cost:

HTTP nodes require you to:

1. Know the NetSuite REST URL for each record type you need

2. Construct the OAuth1 HMAC-SHA1 signature in every node (wrong timestamp = auth failure)

3. Know the exact field IDs (NetSuite calls custom fields custentity_, custbody_ — not obvious)

4. Build a workflow branch for every customer scenario

5. Pass the customer's chat identity into every API call manually

6. Rebuild everything when NetSuite updates their schema

Skills eliminate all five of those. The question isn't "does it work?" — it's "who on your team is going to own it, and what happens when they leave?"

---

Handling the "we'll just use MCP" objection

> "We're evaluating MCP-based integrations."

MCP is the transport protocol, not the integration. Building NetSuite over raw MCP means:

• Building and hosting your own MCP tool server
• Implementing OAuth1 signing yourself
• Defining every NetSuite operation as a tool schema
• Handling field validation and error states
• Deploying and maintaining infrastructure

That's the same developer project HTTP nodes were, now running over a different protocol. Velaro's Skills are the application layer above MCP — pre-built, pre-authenticated, and maintained as NetSuite's API changes. You get MCP's architectural benefits without any of the build work.

---

The implicit identity advantage (use this in demos)

Every competitor integration — HTTP nodes, bundles, raw MCP, Zapier — requires you to pass the customer's identifier from the conversation into the API call explicitly. That means mapping variables, testing the flow, and handling the case where the identifier is missing.

Velaro Skills work differently: the visitor's email, name, and phone from the prechat survey are automatically threaded as the lookup key into every skill call. The bot doesn't ask "what's your email?" in chat. It already has it. From the customer's perspective, the chatbot pulled up their account the moment they clicked the chat button.

Demo script for this moment:

> "Notice that I never asked the customer for their account number or email. They entered it in the chat widget before the conversation started, and every NetSuite lookup — the order search, the invoice pull, the case creation — used that email automatically. The bot already knows who they are."

---

What to say about the patent-defensible architecture

For enterprise and analyst conversations where technical differentiation matters:

Velaro's approach combines four properties that don't exist together in any other chatbot-to-ERP integration:

1. Dynamic skill composition from natural language — the AI chains multiple ERP operations based on conversation intent, without pre-authored routing trees

2. Implicit identity threading — session-start identity attributes (email, name, phone) flow automatically into ERP lookup calls as the primary key, with no re-identification step

3. Pre-authenticated named operation registry — each skill is a server-side pre-authenticated, field-validated named operation; credentials are never serialized into workflow definitions or bot prompts

4. Session-scoped credential isolation in multi-tenant deployment — OAuth credentials scoped per integration config, encrypted at rest, never exposed across tenants

No bundle-based, HTTP-node-based, or raw-MCP-based architecture achieves all four simultaneously. This combination is the subject of ongoing intellectual property protection.

---

Credentials required (what to tell prospects about setup)

Five values, generated once in NetSuite, pasted into Velaro once:

Field	Where to get it in NetSuite
Account ID	Setup → Company → Company Information → "Account ID"
Consumer Key	Setup → Integration → Manage Integrations → New (enable TBA)
Consumer Secret	Same screen — shown once at creation
Token ID	Setup → Users/Roles → Access Tokens → New
Token Secret	Same screen — shown once at creation

After save: Velaro encrypts these server-side (AES-256). They never appear in workflow definitions, logs, or bot prompts. No rotation needed unless the customer chooses to rotate.

Optional for advanced setups:

• Field mappings — define how prechat variables map to NetSuite fields for write operations (create lead, update customer)
• Default subsidiary — for OneWorld accounts, set the default subsidiary for created records
• Custom Restlet URL — for calling custom SuiteScript via netsuite_restlet

---

Velaro NetSuite partnership credentials

• BFN (Built for NetSuite) certified since 2008 — predates Zapier (founded 2011)
• Listed on SuiteApp.com: [Velaro Chat for NetSuite](https://www.suiteapp.com/Velaro-Chat-for-NetSuite)
• Oracle press release (2008): [netsuite.com/portal/press/releases/nlpr07-22-08c.shtml](https://www.netsuite.com/portal/press/releases/nlpr07-22-08c.shtml)
• SuiteCommerce supported

---

Marketing page links

• Full integration overview: [velaro.com/netsuite.html](https://velaro.com/netsuite.html)
• AI Skills pitch page (PowerPoint-ready): [velaro.com/netsuite-ai-skills.html](https://velaro.com/netsuite-ai-skills.html)
• Security architecture: [velaro.com/netsuite-security-architecture.html](https://velaro.com/netsuite-security-architecture.html)
• Reseller program: [velaro.com/netsuite-reseller.html](https://velaro.com/netsuite-reseller.html)
• Blog: [velaro.com/blog/netsuite-ai-skills-no-http-nodes.html](https://velaro.com/blog/netsuite-ai-skills-no-http-nodes.html)