Putting three marketplace names on one dashboard does not automatically give a seller one dependable service operation. Messages can still arrive without the correct product, remain assigned to an offline agent or receive conflicting answers from a bot and a person.

A useful shared inbox should reduce those failures. Build it around actual stores, visible ownership and a clear route for unresolved work. The workflow below is a configuration and acceptance plan; the exact available settings depend on your product, marketplace site and permissions.
1. Map the stores before connecting them
Create a register containing the marketplace, country site, store name, account owner, primary language and person authorised to manage the connection. Include a contact for recovering access if the authorisation expires. Do not rely on a staff member's personal memory of which login belongs to which shop.

Stores with similar names deserve particular attention. If two shops sell different bundles under the same brand, the inbox must preserve the distinction. A reply that is correct for one store can be wrong for another.


	

		

			
Register field
			
Why it matters
		
		

			
Platform and country site
			
Features and service rules may differ by market
		
		

			
Store identity
			
Agents must answer under the correct shop
		
		

			
Authorising account
			
Access should be granted by someone with appropriate rights
		
		

			
Knowledge scope
			
Product and policy answers must match the relevant store
		
		

			
Responsible person
			
Connection problems and policy questions need an owner
		
		

			
Manual fallback
			
Staff need a way to serve buyers if the shared connection fails
		
	



Keep access credentials in the business's approved credential-management process, not in the store register or an AI knowledge document. The register should identify responsibility without exposing passwords or verification codes.

2. Test the connection in both directions
Use a controlled test conversation for each store. Confirm receipt of supported text and any message types important to your operation, such as product or order cards. Check that the source store remains obvious while viewing the message and composing a reply.

Where supported, send a test reply and confirm it appears in the native marketplace conversation. Check the same exchange from the shared workspace and the platform side. A connection that receives messages but cannot reliably send the relevant reply is not ready for normal handling.

Also test what is unavailable. Missing attachments, unsupported cards or limited historical messages need a documented workaround. Do not let agents invent the missing context. A product name in a buyer's message may not uniquely identify the SKU.

Create an acceptance record for every store. The record should show the test date, result, limitation and person responsible for follow-up. Do not approve all stores because one connection worked.

3. Establish one owner per active conversation
Decide whether new messages are assigned manually, by a product's automatic distribution rules or through a combination. Use only the modes the actual system supports. A small team can start with a visible unassigned queue and a named person checking it.

Automatic distribution needs an offline-agent rule. If an agent's shift ends, new work should not silently accumulate under their name. Existing work also needs a handover rather than a bulk reassignment without context.

In Duoke, users may encounter automatic and non-automatic allocation modes. Confirm the current behaviour in your account during setup. The useful distinction is who must take the next ownership step: the system through its configured allocation, or a person reviewing and assigning the queue. Neither mode removes the need to inspect unowned and overdue work.

4. Keep marketplace facts separate
A shared inbox should not become a single indiscriminate answer bank. Bind product information, promotion terms and after-sales rules to the correct store or market where the system supports that scope.

Keep a record of policy sources and effective dates. Do not copy a TikTok Shop US response rule into a Philippine process. Do not assume a Shopee automatic acknowledgement has the same metric treatment as a manually sent answer. Use the current documentation for the relevant site.

A standard reply can still share a useful structure across platforms: identify the product or order, answer using verified facts, explain the next step and transfer the exception when needed. The business facts inside that structure must remain specific.

5. Separate receipt, progress and completion


	

		

			
State of the work
			
What staff should be able to see
			
What should not happen
		
		

			
Newly received
			
Store, buyer request and ownership status
			
A greeting hides the enquiry from the queue
		
		

			
Waiting for clarification
			
Exactly what information is missing
			
Repeated generic requests without reading the buyer's reply
		
		

			
Waiting for another team
			
Responsible internal owner and next check
			
The case is closed merely because a task was created
		
		

			
Human-owned
			
Who accepted the handoff and what AI already did
			
AI continues to issue competing answers
		
		

			
Completed
			
Evidence that the actual service need was handled
			
Silence alone is treated as proof of success
		
	



Your product may use different status names. Map them to the operating meaning instead of creating a parallel status system that nobody maintains.

Review the oldest unfinished commitments daily. Unread-message counts do not reveal every problem: an agent can read a message and still fail to arrange the promised update.

6. Add AI only where the evidence is dependable
Start with routine product and store questions. Prepare a representative set of correct answers and escalation decisions. Test ambiguous product references, wrong variants, missing facts and requests outside the assistant's authority.

Do not treat current stock, tracking or payment information as static FAQ content. Use an available current source, or let the assistant collect the essential reference and hand the lookup to a person. A convincing order update about the wrong parcel is worse than a clear explanation that a check is still needed.

For Duoke Lite, evaluate the supported product-answer and basic guidance scope first. Keep exceptions assigned to a person. Verify the active features and permissions in your version rather than treating another vendor's demonstration as proof of what Duoke can do.

7. Rehearse the busy-day failure
Imagine one store connection expires during a sale while an agent is offline and a buyer returns about an unresolved refund. A useful operating plan answers four separate questions: how the team notices the missing messages, who handles the native inbox, who accepts the agent's open work and who updates the buyer.

Run a small rehearsal before a major campaign. It need not involve live customer traffic. Use controlled messages and a documented scenario. The purpose is to expose ownership gaps while they are inexpensive to fix.

Keep the fallback simple. Staff should know which native Seller Center to check, how to avoid duplicate replies and where to record a conversation handled outside the shared workspace. Reconcile the records after normal service returns.

8. Review a manageable set of measures
Track message reception problems, unassigned conversations, overdue commitments, factual errors and reopened issues. Inspect AI independent completion separately from automatic replies. Keep platform performance metrics separate when their definitions differ.

Compare the workload before and after the change using a similar period and conversation mix. A quieter week can make a new inbox look faster even if nothing has improved. A sale can increase handling time because the questions have become more complex.

The goal is a shared operation the team can explain: which stores are connected, who owns each issue, what AI is permitted to answer and how unfinished work returns to attention. Once that is dependable, expand the scope store by store.