Skip to main content

Merchant workflows

Describe the business outcome, provide known Inttegro IDs, and state whether the agent may make changes. The agent should choose the smallest sufficient tool set and preserve every authoritative result.

Review product and customer performance

Choose a period and currency explicitly. The analytics tools support 7d, 30d, and 90d periods.

Show product performance for the last 30 days in GHS. Give me exact revenue in minor units, paid orders, and units sold for the top products, including the Flint chart. Then show the top customers for the same period without exposing contact details. Do not estimate missing data.

The agent uses get_product_analytics and get_customer_analytics. It keeps exact amounts in structured results, does not combine currencies, and reports empty or partial metric buckets instead of filling gaps.

Inspect an order and current balances

Look up order <ORDER_ID>. Summarize its current order status, payment status, total, and most recent recorded timestamps. Then show current balances by currency, explain the returned categories, and include the balance chart. Do not make changes or invent unavailable amounts.

The agent uses get_order and get_balances. It keeps order status separate from payment status and labels all money as integer minor units.

Trace recent operations

Review the five most recent orders and five most recent balance transactions. Identify only the transaction IDs that explicitly refer to those orders. Summarize the supported relationships and do not infer customer details or call this a complete sales report.

This uses bounded list tools. Ask for another page explicitly when needed; one result page is never treated as an all-time or full-period total.

Give the agent exact commercial terms and an existing, consented customer ID. Do not provide a raw phone number.

Create a draft service product named “Meetup consultation” with the description “A focused 45-minute Inttegro consultation.” Add an active GHS 350.00 price, create a single-use buy link limited to one unit, and send it to customer <CUSTOMER_ID> with the prefix “Your consultation link:”. Ask me to confirm every change separately. Report the product ID, price ID, canonical buy-link URL, and SMS delivery status.

The agent performs four distinct actions:

  1. create_product creates the draft service.
  2. create_product_price sends amount_minor: 35000 for GHS 350.00.
  3. create_buy_link sets both minimum and maximum quantity to 1 and makes the link single-use.
  4. send_buy_link_sms verifies the link, constructs its hosted URL server-side, and sends the confirmed message.

Each accepted action returns its own authoritative result. Declining or canceling one confirmation prevents that step. Separating product and price creation keeps a price failure from being reported as a completed product-and-price transaction.

Create an order and send its invoice

Use existing customer, product, and price IDs. Finalizing seals the order so the invoice can be sent, but never charges the customer.

Create and finalize an order for customer <CUSTOMER_ID> containing two units of product <PRODUCT_ID> at price <PRICE_ID>. Do not execute payment. After creation, send its invoice through the customer's available channels. Confirm the order and delivery separately, then report the order ID, calculated total, and channels that succeeded or failed.

The first confirmation covers create_order; the second covers send_order_invoice. Invoice delivery can partially succeed, so the agent reports outcomes by channel instead of flattening the attempt into one success or failure.

Maintain and message a customer

Find customer <CUSTOMER_ID>, summarize their returned commerce activity and available communication channels without revealing contact details, update only the requested display field, then send the exact SMS “Your order is ready for pickup.” Confirm the update and message separately.

The agent uses get_customer, update_customer, and send_customer_sms. It never asks for the customer's number because the customer ID is the delivery boundary.

Use operation keys safely

Every action includes a printable operation key of at most 60 characters.

  • Reuse the same key only for a retry of the same logical action with identical arguments.
  • Generate a new key when the merchant changes quantity, price, recipient, message, or any other argument.
  • Never interpret a timed-out client response as proof that the action failed; retry the identical call with the same key and inspect the authoritative result.

Requests the agent should refuse

An Inttegro-connected agent should clearly explain the boundary when asked to:

  • charge a customer or retry a payment;
  • move money or change payout settings;
  • reveal customer contact or payment details;
  • send an SMS to a raw phone number;
  • broadcast or schedule outreach;
  • infer full-period analytics from a short list page; or
  • bypass a confirmation.

Review the complete tool catalog or return to the Inttegro MCP overview.