The Sales Engine

The Sales Engine Behind Every Conversation

Built deterministic from the ground up — not a chatbot wrapped in a sales skin. Every message follows the same pipeline. Every action is auditable.

Deterministic by Design

11 Steps. Every Message. No Exceptions.

Sellatrix runs a fixed, ordered pipeline on every incoming message — not an LLM free-for-all. Guards short-circuit early; tools execute only when needed.

8 Purpose-Built Tools

AI That Executes, Not Just Chats

Every action a customer can take — from browsing to ordering to escalating — has a dedicated, deterministic tool grounded in the running codebase.

Smart Catalog Search

Filters the product catalog by budget, category, and availability. Returns ranked results.

Product Detail Lookup

Exact product lookup with variant disambiguation. Remembers unresolved choices for seamless follow-up.

Side-by-Side Comparison

Side-by-side comparison of up to 3 products across specs, price, and availability.

In-Chat Order Placement

Two-turn confirmation gate. Customer must affirm before the order document is created.

Order Cancellation

Cancels an existing order after confirming ownership and current status.

Real-Time Order Tracking

Retrieves real-time order status, shipping info, and estimated delivery.

Human Handoff

Creates a structured handoff record and pauses the bot. Agents claim, reply, and resolve handoffs from the dashboard — bot re-enables automatically.

Repeat Order Intelligence

Returning customers get a pre-filled checkout. Sellatrix remembers delivery address and payment preference — turning a 4-turn order flow into a single confirmation.

Multi-Channel

One Engine, Every Channel

WhatsApp Meta Cloud API, Twilio, and Telegram — all funnelled through the same deterministic pipeline. HMAC signature verification on every incoming webhook.

Multi-Tenant Architecture

One Platform, Every Branch

The Client → Branch → Channel hierarchy lets enterprise teams run independent bots — each with its own tone, language, catalog, and LLM — without shared state.

Client

Root

Top-level tenant. Owns branches and billing.

Branch

Isolated

A store location or business unit. Has its own bot config, tone, and catalog.

Channel

Endpoints

WhatsApp, Twilio, or Telegram endpoint tied to a specific branch.

WhatsAppTwilioTelegram

What isolation means in practice

Own LLM per Branch

Each branch picks its own provider — OpenAI, Gemini, or Groq. No cross-tenant model sharing.

Own Catalog & Tone

Products, prices, and conversation style are scoped to the branch — changes in one never bleed into another.

No Shared State

Session memory, conversation history, and order data stay within branch boundaries at the database level.

Team Intelligence

Your Team Gets an AI Assistant Too

Every internal role gets a natural-language assistant scoped to what they actually need. No new dashboards to learn — just ask.

Owner / Admin

asks

"How are my sales this week?"

  • Revenue snapshot and confirmed orders
  • Lead pipeline by status
  • Week-over-week trends
Branch Manager

asks

"Show me pending handoffs"

  • Branch-scoped lead counts
  • Open handoffs queue
  • Leads by status for this branch
Agent

asks

"What's assigned to me?"

  • Own leads list only
  • Own pending handoffs
  • Nothing outside their scope

Role enforced by the system, not the AI — every permission boundary is deterministic code. The AI never decides what a user is allowed to see.

LLM Agnostic

OpenAI, Gemini, or Groq — Per Tenant

Sellatrix orchestrates; you choose the model. Each branch gets its own provider config and API key. Switch providers without touching the pipeline.

OpenAI

GPT-4o and variants

Google Gemini

Gemini Pro and Flash

Groq

Llama & Mixtral at speed

+
Coming Soon

More providers

Switch providers without touching the pipeline

Each branch holds its own API key and provider config. Changing one branch never affects others.

Confirmation Gates

Two Turns for Every Destructive Action

Order placement and human escalation both require an explicit customer confirmation before anything is committed. No accidental purchases, no surprise handoffs.

Order Confirmation

Customer places order → bot collects address and payment in-chat → presents full order summary → customer replies Yes → order document created.

Customer: "Place my order"

Bot: "Confirm: iPhone 15, $899 — Yes/No?"

Customer: "Yes"

✓ Order created

Escalation Confirmation

Customer requests human → bot confirms transfer → customer affirms → handoff record created, bot pauses.

Customer: "I need a human"

Bot: "Transfer to support team — confirm?"

Customer: "Yes"

✓ Handoff created, bot paused

Discount Engine

Deterministic discounts — shown at every step

Discounts are resolved from your rules database — not from AI memory. The customer sees the same savings from product lookup through final confirmation.

1

Rule Resolution

At product lookup, the engine deterministically matches active rules — percentage, flat amount, or quantity-based.

2

Savings Highlighted

The immediate reply shows original price, discount, and final price — nudging the customer toward placing the order.

3

Reinforced at Checkout

Address and payment steps re-display the discount breakdown. The customer never wonders what they will actually pay.

4

Stamped on the Order

discountAmount and discountLabel are stored on every order line — visible in the dashboard and exportable for accounting.

Without discount

SAR 4,399

Price shown only

With 10% loyalty discount

SAR 3,959

4,399

← shown at every step through confirmation

The Live Dashboard

Track conversations, orders, and handoffs in one place.

Sellatrix dashboard

Ready to see Sellatrix close a WhatsApp sale?

Book a 30-minute live demo with your own catalog data.