The local example provides a shared inbox for provider replies. A host service maps its seller/provider accounts and team membership to the backend identity contract; the example chooser does not configure production teams.
Reply to a customer#
- Sign in with your assigned email and password; the server determines your seller/provider role and service. Local development also offers Local demo, your service and Seller / provider, then Open workspace.
- Select Refresh to fetch the current inbox, then select a conversation.
- Review the customer's messages. Use Load earlier messages for history.
- Type a reply in Message and select Send.
Draft edits made while a reply is sending are preserved. Selected files upload one at a time; switching conversations stops the remaining selection. For file limits, abandoned-upload capacity and uncertain-send recovery, use the same message and attachment guidance.
The inbox list is customer-wise: each conversation title is the customer you are chatting with, while its subject remains available as supporting context. When an admin or another provider is also involved, the row keeps the same-sized avatar — a second face, or a +N badge for three or more people — and the opened thread names the other participants. Use the conversation's unread badge and subject to tell grouped threads apart.
Only your authorized provider's conversations are available. Another shop's or service's conversations must remain inaccessible even if you know their ID. Your own replies are displayed under your identity and the seller role, including when your host service calls you a provider.
Unread counts indicate saved messages not yet read by your identity. Opening a thread marks the latest loaded message as read. Inbox refresh is explicit; there is no background push/email notification system in this release.
Working with admins#
An authorized service admin can join the same conversation and respond using their own admin identity. The conversation retains customer and provider history. Team assignment/transfer screens, seller escalation buttons and status controls are not implemented in this example. Use the host's existing support process when intervention is needed. Status labels do not assign an agent automatically.
Problems#
An access error means the server did not authorize the requested action; do not retry using someone else's account. If messages stop updating, select Refresh and reopen the conversation. A failed send retains the draft for retry. Do not share your session token. Sign out revokes the current session. Reloading requires sign-in again. Contact your service admin for account access/password changes; there is no self-registration or password-reset screen. The production form has no role or service chooser. Use the distinct email assigned to your account; ask the operator to separate legacy account emails if multiple roles sharing an email prevent normal website sign-in.
Sellers can send and receive image and PDF attachments (with or without a text reply) and use the built-in emoji picker in the inbox. Provider-management screens, automated routing, notification preferences and retention/deletion controls remain outside the current UI.
বাংলা নির্দেশনা#
নিজের email ও password দিয়ে Sign in করুন। Server আপনার account থেকে role ও service নির্ধারণ করবে; login-এ এগুলো বাছাই করতে হবে না। শুধু local demo-তে service ও Seller / provider নির্বাচন করুন। Refresh চাপলে inbox আপডেট হবে। Conversation খুলে Message-এ উত্তর লিখে Send চাপুন। নিজের দোকানের বাইরের chat দেখা বা উত্তর দেওয়া অনুমোদিত নয়। প্রয়োজন হলে বর্তমান support প্রক্রিয়ায় admin সাহায্য নিন; admin নিজের পরিচয়ে reply করবে।