跳到主要内容
Docs/Features/Ai Employee Lisa

Lisa — Order Operations AI Employee

Lisa is your order-operations specialist. Per the seed persona: "you communicate in clear, polite English with calm authority. You drive orders forward through the trade lifecycle (PI → deposit → production → shipment → balance → delivery), chase missing documents and payments without ever sounding pushy."

![Lisa AI Employee](/docs-img/ai-employee-lisa.png)

Persona

  • Role: ORDER
  • Default name: Lisa
  • Style: every message names the PO number, the next concrete action, and the date.
  • Anti-pattern: never guesses; uncertain facts written as "to be confirmed".

    • Supported Tasks

  • `FOLLOWUP_ORDER` — chase a missing doc / payment / signoff.
  • `CHASE_PAYMENT` — payment-specific reminder ladders.
  • `LOGISTICS_UPDATE` — translate a 17track event into a buyer-friendly message.
  • `GENERIC_NL` — anything else.

    • When to Use

    Lisa shines once a quote is accepted. She drives the order through the trade lifecycle so your ops team only intervenes for genuine exceptions.

    Customising Lisa

    Same persona-override surface as the others. Most tenants don't customise Lisa — the default tone is already calibrated for international trade.

    API Endpoints

  • `POST /api/v1/ai-employees/lisa/dispatch`.
  • Lisa auto-fires on `order.deposit_overdue`, `order.production_complete`, `shipment.event_added`.

    • Pricing & Limits

    PlanLisa tasks / month
    Starter100
    Pro5,000
    Enterpriseunlimited

    Gotchas

  • Lisa runs on the flash tier — output is fast but doesn't reason as deeply as Sarah / Emma. Don't ask her to write strategy docs.
  • She'll refuse to auto-send anything that contains an unconfirmed fact. The message goes to drafts with the unconfirmed fields highlighted.
  • For complex multi-PO situations, tag the PO numbers explicitly — Lisa can't always infer which PO from a vague reference.
    • ← Back to Docs