Does Faboxi replace a WMS?
No. Faboxi shows WMS or commerce data inside the support workflow when an operator needs it.
An ecommerce helpdesk built for the new era of customer service.
Faboxi is an ecommerce support workspace for teams that handle customer questions across email, Messenger, webchat, SMS, and phone.
Faboxi brings conversations, orders, tracking, and AI-assisted drafts into one workspace where operators see context before replying and keep control over what reaches the customer.
Faboxi shows conversation, order, delivery, tracking, and customer-history context next to the thread before the operator replies.
AI prepares suggestions and reply drafts, but operators approve, edit, or reject what is sent to the customer.
Commerce data flows through integrations. Faboxi does not connect directly to WMS or CMS databases.
Implementation can start with one process, such as parcel-status questions, returns, data changes, or phone follow-up after email.
Product: one customer case before the reply
Operators see the conversation, order status, delivery, tracking, contact history, and AI-assisted draft in one context.
Typical scenario: the customer asks where the parcel is; Faboxi combines facts from conversations, the store, and fulfillment; the operator approves a safe reply.
Problem: old helpdesks see a message, while ecommerce teams need the whole customer case
The problem is not just message volume. A useful reply depends on facts from several places at once: the conversation channel, order, delivery, customer history, and the limits of what the store should promise.
Conversations split across channels, the order sits outside the conversation, and uncontrolled AI can promise something the store cannot deliver.
Workflow: full case context before the reply
The customer asks about a parcel while facts sit across email, phone, the store, and fulfillment. Faboxi turns them into one context, shows what not to promise, and prepares a reply for approval.
The operator sees channel signals, organized facts, a recommendation, a reply draft, and an internal note.
Solution: conversation, order, and tracking in one workspace
Faboxi reduces panel switching, shows order context beside the customer question, and helps the operator answer without switching panels or guessing parcel status.
Daily-work value: one customer case, order context first, phone without lost context, and AI drafts approved by the operator.
Who it is for: stores with repeated parcel, return, and customer-data questions
Faboxi is for Polish and EU ecommerce stores where the support team is usually 1 to 10 people.
The strongest fit is a team that often handles WISMO, returns, customer-data changes, phone follow-up after email, and cases that require checking a WMS, ERP, store platform, or fulfillment partner.
Typical customer channels are email, phone, Messenger, SMS, and webchat.
Which plan fits your store best?
Calculator recommends Starter, Growth, or Enterprise based on team size, monthly cases, and communication channels.
Recommended plan: Growth. Most often selected by stores at a similar scale.
Estimated benefit: about 42 hours per month, over 504 hours per year, and about 5 work days per month.
Trust and control: AI prepares, operators approve
Faboxi helps the team find facts faster and prepare a reply draft, but replies do not send themselves. The operator sees the suggestion, edits or rejects it, and only then answers the customer.
Order, delivery, and customer data flows through integrations. Faboxi does not require direct WMS/CMS database access, and the history shows what was approved and sent.
Integrations: customer channels, orders, and delivery
Faboxi gathers context through integrations with customer channels, store platforms, ERP/WMS, fulfillment, and delivery. It does not require direct database access to WMS or CMS systems.
- Customer channels: Allegro (Active), Gmail (In preparation), Outlook (Active), Messenger (Active), webchat (Active), phone (Active), SMS (Active).
- Orders and delivery: IdoSell (Active), Shoper (Active), WooCommerce (In preparation), Shopify (In preparation), BaseLinker (Active), InPost (In preparation).
- Operator workflow: recommendation, reply draft, approval, and customer history.
During implementation, we prioritize the data sources that matter first and can start with a safe simulation before you change team operations.
Start without risk: see the workflow before changing the process
Faboxi should first prove value on a real customer case. Broader rollout comes only after you see how much support work disappears.
The start covers a demo before commitment, no system replacement, and AI drafts kept under team control.
Pricing: Starter, Growth, and Enterprise
Starter includes one workspace, up to 2 seats, and one support process such as parcel-status questions or returns.
Growth includes a larger team, several support channels, broader case context, and AI usage reporting.
Enterprise includes high volume, multiple processes, phone/SMS, customer history, and broader integration support.
Subscription prices are net monthly prices for annual billing. Monthly billing is 10% higher.
AI drafts are a subscription add-on. Showing order data does not trigger AI billing. Before launch, we agree on the draft usage range or cap, and reporting shows when a larger range is needed.
Common questions before a demo
Does AI send replies automatically?
No by default. AI drafts suggested replies and a human operator approves, edits, or rejects them.
Can we start without moving production channels?
Yes. Implementation can start with one process, such as parcel-status questions, before a broader rollout.
Which integrations matter first?
We prioritize what shortens replies fastest: email, Messenger, webchat, store or WMS data, phone/SMS, delivery context, and approved replies.
What do Starter, Growth, and Enterprise include?
Starter covers the first support process. Growth expands work across a larger team and more channels. Enterprise is for high-volume teams with multiple processes and broader integration needs.
How are AI drafts billed?
AI drafts are a subscription add-on. Showing order data does not trigger AI billing. Before launch, we agree on the draft usage range or cap, and reporting shows usage before a larger range is needed.
Is operator approval required?
Yes in the default workflow. The draft waits inside the customer case, and an operator decides whether to send, edit, or reject it.
Does Faboxi connect directly to WMS or store databases?
No. Order, delivery, and customer data flows through integrations, without direct Faboxi access to WMS/CMS databases.
What data does the operator see in Faboxi?
The operator sees channel conversations, order status, delivery status, tracking number, contact history, what not to promise, and a reply draft.
What happens after booking implementation?
We choose one first process, review the required channels and data sources, then launch the workspace so operators see the conversation, order, tracking, and AI draft in one place.
NEXT STEP
See how much time your team can regain.
We will show you a real customer support process from message to ready-to-send reply. You will see exactly how Faboxi brings conversations, orders, shipments, and AI into one customer case.
Most stores start with one process, such as parcel-status questions or returns.
The demo does not require an account, login, or payment card.
Service operator
BMG Gilbert Przybylowski, Zagorzyce 617B, 39-126 Zagorzyce, Poland.
Support: support@faboxi.com. Privacy: privacy@faboxi.com.