Oxyok Logo
Oxyok

Oxyok

RFQs, quotes, and follow-ups
checked before your team replies.

Oxyok turns messy customer emails into checked next steps across ERP, CRM, product data, pricing, stock, lead time, documents, and approvals.

See the workflow

Start with one painful workflow

before a broad platform.

The first workflow should be narrow enough to build quickly and painful enough that the team immediately knows whether it saves work.

Workflow 01

RFQs and quote requests

Oxyok extracts requirements, finds missing specs, checks product fit, pricing, lead time, and prepares the next customer or internal message.

Workflow 02

Customer follow-ups and open loops

Oxyok tracks unanswered questions to engineering, pricing, logistics, customers, or suppliers, then prepares the next reminder or reply.

Workflow 03

Orders and availability exceptions

For distributors, Oxyok checks stock, substitutions, customer rules, pricing, delivery timing, and whether a promise is safe before the team replies.

Example workflow

A messy RFQ becomes a quote-ready work package.

The first demo should show the real work: what the customer asked for, what is missing, which systems were checked, and what your team can approve.

Incoming RFQ

Can you quote this configuration for delivery to Germany, include lead time, and suggest an alternative if the standard model is not available?

Requirements

Extract requested product, configuration, quantity, destination, target date, attachments, and missing specs.

Customer context

Check account history, language, market, previous quotes, commercial terms, and open follow-ups.

Product fit

Match catalogue data, variants, drawings, datasheets, alternatives, and technical constraints.

Price and margin

Check customer pricing, discounts, quote rules, approval thresholds, and margin risk.

Lead time and documents

Check stock, production plan, shipment options, certificates, export docs, and realistic promise dates.

Approval-ready draft

Prepare a reply, quote summary, missing-info request, or internal task. The employee approves before anything is sent.

Replay demo

Show the work the assistant removes, not just the final answer.

A good pilot demo should replay the checks, handoffs, and draft decisions that normally sit between the inbox and the customer reply.

Incoming customer emailRFQ / quote desk

We need a quote for a hydraulic press configuration for a customer in Germany. Please include lead time, delivery terms, and an alternative if the standard model is unavailable.

Tool call

Read the request

Extracts product family, destination, timing, missing specs, attachments, and decision owner.

Tool call

Check systems

Looks up ERP, CRM, product data, pricing rules, inventory or planning, and document sources.

Risk check

Flag gaps

Finds missing technical details, price approvals, lead-time uncertainty, and documents needed for export.

Human step

Prepare for approval

Creates the customer reply, quote summary, internal task, and follow-up reminders.

Customer draft

A ready reply asking for missing specs and offering a realistic next step.

Internal task

Engineering or planning question with the exact context needed to answer quickly.

Follow-up

Reminder if the quote, approval, or customer clarification gets stuck.

What Oxyok connects

The value is in the work between email, ERP, CRM, product data, and approvals.

Oxyok is not another ERP, CRM, WMS, or portal. It prepares checked work across the systems that already hold the answer.

Email and customer channels

Email, portals, forms, PDFs, spreadsheets, attachments, call notes, and customer messages.

ERP and CRM

Customers, quotes, orders, invoices, prices, terms, limits, history, opportunities, and account notes.

Product and technical data

Catalogues, SKUs, variants, drawings, datasheets, compatibility, substitutions, and requirements.

Inventory, planning, and lead time

Stock, reservations, production slots, lead times, shipment options, cut-offs, and delivery constraints.

Pricing and approvals

Discounts, margin rules, engineering input, pricing approvals, risk flags, promises, and ownership.

Documents and audit trail

Quote packs, certificates, export documents, approvals, reasoning, edits, and decision history.

How a pilot works.

01

Map one workflow

We identify messages, roles, systems, data fields, rules, approvals, edge cases, and handoffs behind one repeated customer request.

02

Build the work layer

We connect the needed context, prepare drafts and actions, show the reasoning, and keep approval with the responsible employee.

03

Pilot, measure, expand

We measure response time, manual checks removed, mistakes, stale follow-ups, adoption, and whether the team wants to keep using it.

Pilot outcomes

The first pilot should be measured like operational work, not a chatbot demo.

We pick one high-friction workflow and define success before building. If it works, it becomes the base for more workflows.

Speed

Quote faster

Fewer manual checks before the first useful customer reply or quote-ready summary.

Control

Fewer unsafe promises

Missing specs, price risk, lead-time conflicts, document gaps, and approvals are visible before replying.

Follow-up

Stop losing open loops

Engineering, pricing, logistics, supplier, and customer questions stay visible until they are resolved.

Expansion

The next workflow is easier

After the first workflow, the same layer can support orders, claims, procurement, finance, or outbound sales.

Bring one messy RFQ, quote, or follow-up workflow.

Oxyok - RFQ and workflow AI for manufacturers and distributors