A direct conversation, from your site or app to your team.
AAZIRO Chat gives customers a clear place to ask for help and gives agents the full conversation when they answer. The website widget and reusable customer mobile SDK connect to the same support workflow.
Activity
◉ Alex started a conversation from the website widget · 2 min ago
◇ Routed to the Support queue · 2 min ago
↗ Maya picked up the conversation · just now
Hi, can you help with my order? I need to update the delivery address.
Check the order before confirming any change.
A question about an order, account or service does not have to disappear into a form. The customer can message, return and see the reply in context.
How it works.
Follow the implemented workflow from the first action to the next.
Install the channel
Use the merchant-generated widget snippet on an authorized website origin. Mobile teams integrate the Dart customer SDK into their own host app.
Receive the message
A customer starts a conversation; the thread enters the tenant's routing and agent inbox. Messages, typing and delivery/read state update through the realtime channel.
Keep the thread
The customer session restores after reload or reconnect, while agents can find the conversation and its history after resolution.
Built around the work.
More than text
Supported attachments, typing indicators and delivery/read receipts help both sides follow the exchange.
Context survives a reconnect
Persisted messages and replay restore the visible thread without duplicate events in the validated local browser flows.
A branded entry point
Merchant configuration controls the widget's public identity and authorized installation origin; announcements can appear inside the customer experience.
Make it work for your team.
- Choose an authorized website origin and copy its generated installation snippet.
- Configure the customer-facing brand and support availability in the merchant workspace.
- For mobile, supply host-app identity, secure storage, interface and push integration around the reusable SDK.
Know what to expect.
- The public installation identifier is not a private API credential.
- The SDK is not a turnkey customer mobile app; merchant host-app integration and staged UAT remain separate.
- External private storage and real push-provider delivery require their own production validation.
An order question that stays in one place
Illustrative: a visitor asks about an order in the website widget, leaves the page and returns later. The conversation and agent reply are still together. No real customer or order data is shown here.
The details matter.
Does the chat survive a page reload?＋
The validated widget restores the customer session and conversation history after reload and reconnect. The actual merchant installation still needs its own staging test.
Can I put an API secret in the widget?＋
No. The widget uses publishable workspace installation information. Scoped API and webhook secrets belong only on a server.
Is the mobile SDK a finished customer app?＋
No. It is a reusable Dart integration that a merchant places inside its own app, with the host app providing identity, secure storage and native push.
Make every conversation easier to carry forward.
Public signup, checkout and payments are not available yet.