Ailyz integrates with ReAI, connecting AI-assisted customer service with a system for accounting, online sales, point of sale and inventory workflows.
For a customer, the question is rarely which system holds the answer. They want to know what happens next: whether an order has been sent, how a return is progressing, or who is checking a payment. The integration is relevant when your team needs to connect those conversations to the work behind the sale.
Start with the questions your team answers every day
| Customer question | What the team needs to establish | What a useful reply explains |
|---|---|---|
| Where is my order? | Which order and shipment the customer means | The latest confirmed step and how to follow it |
| Has my return arrived? | Whether the return is only requested or actually received | What is known and which check comes next |
| Where is my refund? | Whether a refund is requested, approved or processed | The confirmed status without claiming the money has arrived |
| Why does this amount differ? | The relevant sale, adjustment and payment references | Who is checking the difference and when the customer will hear back |
These are workflows to scope during setup, not a promise that every field or action is available in every configuration. Confirm the data and permissions needed for each selected workflow.
Keep conversation and financial actions distinct
Ailyz supports the customer-service conversation. ReAI is the place to work with the underlying business records. A drafted reply is not evidence that a refund, credit note or inventory change has happened.
Set a clear boundary between reading information, suggesting an action and executing a change. Start with review and approval for changes that affect money, orders or stock. If information is missing or inconsistent, the right next step is a named handover, not a confident guess.
A practical first rollout
Choose one frequent question, such as return follow-up. Agree on:
- How the conversation is matched to the right customer and order.
- Which information the support role is allowed to see.
- Which source determines the current status.
- Who approves changes and handles exceptions.
- How the customer is updated if another team must investigate.
Use anonymised examples of a normal case, a partial return and a disputed amount. Ask the team to explain what it can confirm at each step. Avoid copying entire financial records into a support conversation when a limited reference is sufficient.
When the connection is a good fit
The ReAI integration is especially relevant if you use ReAI for commerce and accounting and want customer service to work from the same business context. If you run a different storefront, review the Shopify integration and your wider integration setup as well.
For the commerce workflow, see ReAI’s online store and accounting system . If a support case exposes an accounting problem that needs a person to resolve it, Aiak’s webshop accounting services are a separate service to consider. An accounting engagement is not part of the Ailyz integration by default.
Discuss your support workflow
Contact Ailyz with the questions your team handles most often and the systems you use. We can review the intended workflow, access requirements and handover points. Do not include customer data or sensitive financial documents in the initial message.
For a detailed process example, see AI for returns and exchanges .