NetSuite support after go-live: what good L2/L3 support looks like

Good NetSuite support after go-live is not a help desk that closes tickets. It is a clear split of who answers what, a quick route to a fix when something breaks, and someone who finds out why it broke so it doesn't happen again. Most businesses handle simple questions in-house. What they lack is the second and third levels: someone senior who can read a script log, trace a failed integration record, or work out why a journal posted to the wrong period.

I've provided L2/L3 support and administration to NetSuite customers for years. Most of them came to me after going live with someone else. This is what I think good support looks like, and how to tell whether you have it.

What L1, L2 and L3 NetSuite support mean

Oracle doesn't define these levels for you. They are a common way to divide the work, and this is how I use them:

• L1: how-to and access. Password resets, "where do I find this report", a user who can't see a field. Usually handled by a key user or your NetSuite administrator.
• L2: diagnosis and configuration. Something is wrong and needs investigating. A saved search returns the wrong totals, an approval workflow stalls, a tax code posts to the wrong account, a CSV import fails. L2 fixes configuration, roles, forms, searches and data.
• L3: technical and design. The cause sits in SuiteScript, a workflow, an integration or the way the account was designed. L3 reads code and logs, fixes or rewrites scripts, and changes the design where it's wrong.

The test of a good set-up is that each request reaches the right level quickly. An L3 problem that sits with L1 for two weeks costs more than the fix.

Where Oracle NetSuite Customer Support fits

Oracle's own support is part of the picture, but it covers the product, not your configuration. The defects it tracks are cases "when a feature doesn't work as intended" (Oracle: NetSuite issue resolution). Your custom scripts, workflows, saved searches and third-party integrations are yours to support, or your partner's.

What you can do through Oracle depends on your support level. Oracle's help on creating support cases says:

• On Basic Support, you go to the Support tab, select Go to SuiteAnswers, then Contact Support. You start with the Virtual Support Assistant, and you can submit only critical problems that affect business operations. Other questions go to the NetSuite Support Community.
• On Premium Support, you go to Contact Support > Create Support Case, choose a case type and set a severity. For a C1 case you tick the 24 x 7 availability box.

Only authorised support contacts can report problems and manage cases with Oracle on your behalf. The limit is two contacts on Basic Support and four on Premium. You manage them from the Support tab, in NetSuite 360 > Authorized Support Contacts (Oracle: adding authorised support contacts). When an administrator leaves, check this list straight away, so you aren't left without a valid contact when you need to raise an urgent case.

A good L2/L3 partner knows when an issue is a genuine product defect and writes the case for you: steps to reproduce, the record IDs, the role used, screenshots and the business impact. Oracle says the more case questions you answer, the faster the response. If you have access to NetSuite 360, you can follow defects linked to your cases under See Support Issues.

What good L2/L3 NetSuite support looks like

1. A clear way in, and agreed response times

One channel for requests, whether that's email, Teams or Slack, and a written response time. Everyone should know what counts as urgent. A blocked payment run or failed month-end close is urgent. A new column on a report is not.

2. Triage that starts with evidence

Good support asks for the record, the user, the role and the time, and then looks at the evidence NetSuite already keeps:

• System notes on the record show who changed what and when, with the old and new values (Oracle: system notes).
• Script execution logs, at Customization > Scripting > Script Execution Logs, show script errors across all scripts. Oracle purges user-generated logs after 30 days and system error logs after 60 days, and the log subtab on a script can lose entries sooner when log volume is high (Oracle: governance on script logging). If an error happened six weeks ago, the log may be gone, so act on errors promptly.
• Application Performance Management (APM), a SuiteApp from Oracle, shows which scripts and workflows slow down pages and processes (Oracle: APM for the SuiteCloud platform).
• Integration error queues in Celigo, Boomi or your own logs.

This is the difference between L2 and guesswork. Many "NetSuite is broken" reports come down to a changed role, an edited form or a closed period, and the system notes show that quickly.

3. Fix the cause, not the symptom

Re-running a failed integration record clears today's error. Fixing the missing mapping stops tomorrow's. When the same ticket comes back each month, treat it as a design problem, not a support problem. On the Jockey Club's Coupa integration, finance and support see every flow's health and every error, with a suggested fix, in a control centre built inside NetSuite (case study).

4. Changes made safely

Even small changes should be made in a sandbox first, where you have one, then moved to production with a note of what changed and why. Script and workflow changes need a quick regression test of the process they touch. This is where many support arrangements fall down: a quick fix in production that breaks a scheduled script nobody remembered.

5. A log of every request

Each request should be recorded: what was asked, what was found, what was done and how long it took. The log is how you spot patterns, such as one integration that causes half the tickets. It also means the next person who supports your account doesn't start from nothing.

6. Release readiness twice a year

NetSuite is upgraded twice a year. Before each release, you can request a Release Preview account, which lets you test your daily business processes against the new version (Oracle: the Release Preview account). Good support uses that window to test scripts, workflows, integrations and key reports, and fixes problems before they reach production. I cover this as part of support, or as a fixed NetSuite Release Readiness check.

7. Steady improvement

Support should leave the account better each month: a saved search tidied up, a manual step automated, a role tightened, a user trained. If your support provider only ever reacts, you are paying for the same problems twice.

Warning signs your NetSuite support isn't working

• The same errors appear every month-end.
• Nobody can say which scripts or integrations run in your account, or who owns them.
• Small changes wait weeks because the implementation partner is busy or expensive.
• Fixes are made directly in production with no record.
• Your only NetSuite expert has left, and the authorised support contact list still has their name on it.

If several of these sound familiar, start with a review of the account. My NetSuite health check checklist covers the areas I look at first.

In-house, partner or independent support

There's no single right model. A strong in-house administrator handles L1 and much of L2, and brings in senior help for L3 and design questions. Smaller teams often have no administrator at all, and need someone to cover all three levels for a set number of hours a month. Either way, the person helping should know your account before something breaks, not learn it during an outage.

My NetSuite support and administration service covers L2/L3 support, administration, performance tuning and release reviews, for accounts I implemented and accounts set up by other partners. If you want a set number of hours each month with agreed response times, a support log and a monthly summary, see the NetSuite Support Retainer. If your integrations generate most of your tickets, read how I plan and test NetSuite integration projects so errors are designed out from the start.

Need senior NetSuite support after go-live, or a second pair of hands for your administrator? Book a call and we can talk through what you need.