NetSuite
Oracle NetSuite is the cloud ERP of choice for fast-growing companies that outgrew spreadsheets and did not want to run their own servers. It holds the whole commercial record in one place.
Oracle NetSuite is the cloud ERP of choice for fast-growing companies that outgrew spreadsheets and did not want to run their own servers. It holds the whole commercial record in one place.
What NetSuite holds, and why that matters here
NetSuite covers financials, order management, inventory, CRM and often ecommerce in a single instance. Companies choose it precisely because it consolidates — one record of the customer, the order and the money — which makes it an unusually good source for an assistant, because a single connection answers questions that elsewhere would need three.
The organisations running it tend to be growing quickly, which is the relevant fact: contact volume grows faster than headcount, and the questions being asked are overwhelmingly repetitive.
- Order to cash — sales orders, fulfilments, invoices and payments as one flow.
- Inventory — quantity on hand, committed, available and on order, by location.
- Customers — account records, terms, credit and transaction history.
- Procurement — purchase orders and vendor bills.
- Subscriptions — recurring billing state, where that module is used.
Questions Elbi can answer from NetSuite
Where is my order?
Fulfilment status and shipping detail from the live record.
What is available to promise?
Available quantity by location, which is the number that should be quoted and frequently is not.
What is my balance?
Customer balance and open invoices, answered to the customer directly.
When does my subscription renew?
Renewal date and terms, which removes a large share of billing contact.
Has the vendor bill been entered?
Purchase-to-pay state for internal users chasing suppliers.
What did we ship last time?
Transaction history on the account, which answers most repeat-order questions.
How Elbi reads NetSuite
- A dedicated role with view permissionsYour administrator creates a role for the assistant with view-level permissions on the record types in scope — sales orders, item fulfilments, invoices, customers, items — and nothing else. In a OneWorld account, role restrictions can narrow it further by subsidiary, location or department.
- Token-based or OAuth sign-inThe connection is registered as an integration record in your account and signs in with token-based authentication or OAuth, both of which NetSuite supports. The tokens are tied to a user and that role, and can be revoked from your account at any time.
- Reads through SuiteTalk REST web servicesRecords are read through NetSuite's REST web services, with SuiteQL for questions such as "which invoices are still open for this customer". Where a RESTlet or saved search you already maintain answers a question well, that can be the source instead.
- Customers are matched to their own recordA customer asking about "my order" is identified through your sign-in and matched to their customer record, so only transactions under that record are read. Staff are answered within what their own role would show them.
- Available, not on handFor stock questions the assistant reads the available quantity by location — on hand, less what is already committed to other orders — which is the figure a salesperson should actually quote.
- Statuses become plain answers"Pending Fulfillment" or "Partially Fulfilled" becomes a sentence, in Arabic or English, about what has shipped and what has not. Creating a sales order or a support case is possible where you enable it, one action at a time, and can wait for a person to confirm.
NetSuite roles, permissions and what stays yours
| Direction of access | View permissions by default. Create or edit permissions are added deliberately, per record type, and the action itself can be held for a person to confirm. |
|---|---|
| Who can see what | The assistant's role limits which record types it can read; role restrictions limit subsidiaries, locations or departments. Customers only ever see transactions on their own customer record. |
| Credentials | The integration record and access tokens live in your account. Revoking a token or disabling the integration record stops the connection at once, with no involvement from us. |
| Where data goes | Order and balance details read from NetSuite are used for that one answer. The messages holding them are destroyed within 24 hours, typically as the conversation ends, and no external AI service ever handles them. |
| Audit | Each lookup can be recorded — the question, the record read, the agent, the conversation — and NetSuite's own login audit trail shows the integration's sign-ins from your side as well. |
| If it is unavailable | During NetSuite's scheduled maintenance, or an outage, the assistant says it cannot reach NetSuite and offers a person. It does not present yesterday's stock as today's. |
What this replaces as a NetSuite company grows
Growing companies hit a specific wall: the number of routine questions scales with revenue, but the people able to answer them do not. NetSuite is usually accessible to finance and operations and to almost nobody else, so every question from sales, support or a customer becomes an internal request.
The assistant changes the shape of that. Order status, availability and balance are the three highest-volume questions in almost every NetSuite shop, and all three are single lookups. Removing them removes most of the interruption without touching anything that requires judgement.
It also helps at the point of sale. A salesperson who can ask for available-to-promise mid-conversation quotes accurately; one who cannot either guesses or promises to come back, and both cost money in different ways.
How NetSuite companies in different sectors use it
Ecommerce and D2C
Order and delivery status at high volume, most of it outside office hours.
Wholesale
Availability and pricing questions that decide whether an order is placed at all.
Subscription businesses
Renewal, billing and entitlement questions, which dominate support contact.
Professional services
Project billing and invoice state for clients.
Getting value from NetSuite
In most NetSuite companies the first questions choose themselves: where is my order, is it available, what do I owe. They arrive from customers, sales staff and support alike, and each is a single read against records NetSuite already keeps.
If you bill subscriptions, renewal dates and billing terms are the next obvious candidate, because they generate steady contact and have exact answers. Purchase-to-pay questions from internal users can follow once the customer-facing side has settled.
Mind concurrency. NetSuite limits how many web service requests an account can run at the same time, and your other integrations draw on that same allowance. A narrow scope, and reads that fetch only the fields a question needs, keep the assistant from competing with them.
What connecting NetSuite involves
- Start from the questions and their record typesOrder status means sales orders and item fulfilments; balances mean invoices and customer payments; availability means items by location. That list becomes the role's permissions.
- Involve your administrator or NetSuite partnerWhoever manages your account knows the custom records, scripts and workflows in it, and owns the role, the integration record and the tokens. Much of this step is their sign-off rather than new building.
- Create the role, integration record and tokensView permissions on the record types in scope, restrictions by subsidiary or location where relevant, and REST web services allowed for that role. This is also the moment to confirm how the user holding the tokens is licensed.
- Map custom records, fields and listsCustom records, custom fields and custom lists are mapped, so the assistant uses the names your team uses and reads the field that actually carries the answer.
- Rehearse in a sandbox if you have onePartial fulfilments, backorders, a part-paid invoice, a customer with several ship-to addresses, someone asking about another customer's order. These are tried outside production first wherever a sandbox account exists.
- Launch on one set of questions, then widenOrder status first, then availability and balances once a month of real traffic has been reviewed.
Personal and financial data in NetSuite
Because NetSuite puts CRM and finance in one place, a single customer record can carry contacts, email addresses, phone numbers, addresses, credit limits and payment history together. Under the Saudi Personal Data Protection Law, reading any of it during a conversation needs a purpose, and most questions need only a fraction of it.
Keep contact and address fields out of the role unless a question genuinely needs them, keep credit limits and stored payment instruments out entirely, and identify a customer before any balance is disclosed. If customers will have their account read during a chat, tell them so in the language they are using, from the first release.
What NetSuite companies typically see
Other ways NetSuite companies handle this
NetSuite has its own self-service routes. The Customer Center role gives customers a login to see their orders and invoices, and web stores built on SuiteCommerce include a My Account area for the same purpose. Oracle has also been adding generative AI features inside NetSuite for its own users. Where customers already use those, they should carry on.
The route many growing companies drift into is adding NetSuite users so more staff can look things up. That helps internally, but it costs a licence per person and does nothing for the customer who will not log in to a portal to ask one question.
Where assistant projects go wrong in NetSuite is reusing a broad role — sometimes Administrator — for the integration because it is quicker. It works on the first day and fails the first security review. The other mistake is reporting: saved searches and SuiteAnalytics are the place for period totals, not a chat.
And design for the unhappy path: a maintenance window, a mistyped order number, a customer who cannot be matched to a record. "I could not find that in NetSuite", with a hand-off to a person, is the correct answer.
Common questions about NetSuite
The people it answers do not need NetSuite access — that is the point. The connection itself runs under a dedicated role, with tokens tied to a user, so confirm with your NetSuite account manager how that user should be licensed.
Normal. Custom records and fields are mapped during deployment.
Where you enable it. Reads are the default; order creation is deliberate and can require a person to confirm.
No. The assistant signs in with tokens issued from your account, under a role your administrator defined. You can revoke those tokens, or disable the integration record, whenever you choose and without going through us.
Role restrictions can limit the assistant to the subsidiaries in scope, and each customer has a primary subsidiary, so answers stay within the right entity. Starting with one subsidiary is usually simpler.
NetSuite upgrades accounts on a published schedule, with a release preview beforehand for testing. Re-checking the scoped reads there is sensible, since custom scripts and workflows are where problems tend to show.
Connect it to your own systems
A working assistant against your own records, in both languages.