Skip to content
Tessolva
Get started
Tessolva Get started
← All use cases

Industry guide / Ecommerce

Turn order questions into completed next steps.

Customers ask where their order is, whether they can change it and how to return one item. A useful answer connects the order, each shipment, the store’s policy and the customer’s choice.

Resolve order-level questions and complete allowed service actions without losing the details.

01 / EcommerceIllustrative example

Explain a split delivery and start an exchange.

The request

“Only one item arrived, and it is the wrong size. Is the rest missing? Can I exchange this one?”

The result / Example reply

Your order was split into two shipments. The second parcel is still in transit, and I’ve linked its tracking. For the delivered item, your selected replacement size is available and the store’s policy permits an exchange. After you confirmed the size, I created the return request and sent the instructions. The remaining parcel is unchanged.

One conversation for the missing parcel and the size exchange.

See the work behind the reply

  1. Verify order ownership, line items and shipment-level tracking rather than relying on one order status.

  2. Check the delivered item’s return window, exclusions, replacement stock and any price difference.

  3. Confirm the customer’s choice, create the permitted exchange request and verify that instructions were issued.

What this workflow needs

Connected context

Order lines, fulfillment records, carrier events, stock, return policy and returns tool.

Where the boundary sits

An exchange request is not a shipped replacement. Refunds, fees and replacements follow the store’s configured limits and confirmed customer choice.

02 / EcommerceIllustrative example

Change an order before the fulfillment cut-off.

The request

“I used my old address. Can you change it before the order ships?”

The result / Example reply

The order has not reached the warehouse’s change cut-off. After you confirmed the new address in the secure form, I updated the permitted delivery details and checked that the fulfillment system accepted the update.

A verified correction before the parcel goes to the wrong address.

See the work behind the reply

  1. Verify the customer and read both order and warehouse status.

  2. Validate the confirmed address and check fulfillment locks, fraud holds and shipping-zone rules.

  3. Apply the allowed change and confirm the warehouse acknowledgement; stop if dispatch has already begun.

What this workflow needs

Connected context

Order management, fulfillment lock, address validation and warehouse update acknowledgement.

Where the boundary sits

A delivered or already dispatched parcel follows a different procedure. Failed acknowledgement is not reported as a successful address change.

03 / EcommerceIllustrative example

Investigate “delivered” when nothing arrived.

The request

“Tracking says delivered, but I cannot find my parcel. Do I need to reorder?”

The result / Example reply

I checked the carrier’s delivery event and the delivery instructions on your order. I’ve started the store’s missing-parcel process and attached the relevant tracking details. If the configured replacement conditions are met after the checks, I can help complete that next step here.

The investigation starts with the relevant evidence already attached.

See the work behind the reply

  1. Check delivery scan, parcel reference, address and available delivery proof for the verified order.

  2. Follow the store’s waiting period and missing-parcel checklist without exposing another customer’s details.

  3. Create a carrier investigation or permitted replacement request and verify its reference.

What this workflow needs

Connected context

Carrier events/proof, order address, store claims policy, case and replacement tools.

Where the boundary sits

Do not promise a refund or replacement before eligibility is established. Suspicious or conflicting evidence goes to the appropriate review.

04 / EcommerceIllustrative example

Resolve a subscription delivery question.

The request

“I skipped this month. Why is a box still coming, and what happens to my next renewal?”

The result / Example reply

The subscription record shows the skip was saved after this box’s processing cut-off. I’ve explained which shipment is already committed and confirmed the next scheduled renewal from your account. If you want to change the following delivery, I can apply the permitted preference after you confirm it.

Clear expectations for this delivery and the next renewal.

See the work behind the reply

  1. Compare skip/cancellation timestamps with billing and fulfillment cut-offs.

  2. Check the next renewal, product selection and applicable subscription policy.

  3. Confirm the requested future change, save it through the allowed tool and verify the new schedule.

What this workflow needs

Connected context

Subscription history, renewal schedule, fulfillment timestamps and preference-change tool.

Where the boundary sits

An account cancellation and a shipment cancellation are separate actions. Existing charges are handled under the store’s refund policy.

One system, improving over time

Resolve the exception.
Keep the useful procedure.

Tessolva’s proposed improvement loop turns verified resolutions into reusable guidance. Private details are removed, the procedure is validated and tested, and approved guidance can help the AI handle a similar request next time.

Investigate → Resolve → Remove private details → Validate & test → Reuse

Your team handles critical decisions, missing permissions and genuine exceptions. Complexity alone does not mean the request needs a person.

Reference topics

Public documentation helped inform these support topics. Examples use fictional data and your own policies would apply. These references do not indicate partnerships or available Tessolva integrations.

Built around your business

What should your support agent resolve?

Bring us a recurring request and the tools behind it. We can explore the right workflow, connections and boundaries.

Discuss your workflow