Support

Follow the evidence to the exact issue.

Choose help for product understanding, implementation, or live application work. Include the relevant product, inspection, NCR, RCA, CAPA, or review reference.

Choose the closest route

Product, implementation, or application help.

Sending the right evidence reference first makes a quality issue easier to follow without exposing unrelated data.

Route 01 · Understand

Product questions

Review the eight linked operating areas, role boundaries, workflows, and closure rule.

Read product overview →
Route 02 · Configure

Implementation help

Prepare products, suppliers, released plans, roles, CAPA policy, and effectiveness rules.

See implementation →
Route 03 · Resolve

Application support

For access or operating issues in ERP.ai, include the affected reference and expected next state.

Email support@erp.ai →

Useful context

Name the controlled object, not the screen position.

A durable reference allows support to follow the same evidence chain used by the quality process.

Product or supplierProvide the product or supplier code and the relevant approval or risk state.
InspectionProvide the released plan revision, inspection reference, type, result, and date.
NonconformanceProvide the NCR reference, severity, state, and the transition that did not occur.
CAPA or reviewProvide the action or effectiveness-review reference, current state, and expected next control.
Website navigation

Information lives here

  • Product explanation
  • Nonconformance and CAPA process
  • Implementation and start guidance
Separate surfaces
ERP.ai support context

Application work lives there

  • Account and access state
  • Live quality records and workflow
  • Saved evidence references

Include the reference. Preserve the evidence trail.

For application help, tell us the exact controlled object and expected next state.

Email support
Made with Proto