Find the order safely
Connect a supported store for read-only order and product context. Verify the customer before disclosing private details; an email address alone is not proof of ownership.
Built around your business
Know the order. Remember the customer.
Bring store questions, social messages, email and calls into one support workspace. Give your team the order context and approved policies to answer with confidence.
A connected support dayThe next person
The next person
gets the whole story.
A shopper asks about a delivery in chat, emails a photo and calls the next day. Keep the request connected so the next person can see what was already promised.
Related history and a shared working Inbox help the team pick up the request with context. Internal Team conversations keep colleagues close to the answer.
Explore this part of Message →For EcommerceUseful work.
Useful work.
Clear next steps.
Build around the requests your team already handles. Start with the knowledge, channels and handoffs that make those conversations easier.
Explain the return policy
Publish the actual return window, conditions and process. AI can use the approved answer while unusual returns and refund decisions go to your team.
Handle messages where shoppers are
Connected WhatsApp, Messenger and Instagram messages join website chats in the Inbox. Filter by channel when needed without leaving the support workspace.
Keep the next step visible
Assign a request to the colleague who can resolve it. Use internal Team chat to ask about an exception and give that person the conversation link.
Teach it your businessGood answers start
Good answers start
with your knowledge.
Scan your website or answer the onboarding interview. Review the drafts, publish approved answers and set company-specific guidance for AI. Connect only the sources that belong in this workspace.
See how Message AI learns →“What is your return window?”
“Where is my order?”
“Can someone help with an item that arrived damaged?”
Connected context
Bring the relevant tools.
Choose connections for your workflow. Open each guide to see its actual capabilities, required permissions and setup.
Start with one real requestMake the trial
Make the trial
look like your workday.
Connect one channel, publish a small set of approved answers and invite the people who will use the workspace. Test the experience from both sides of the conversation.
- Ask a routine question your team answers every day
- Try a request that needs customer verification
- Ask for a person and review the handoff
- Continue the request through a second channel
Before you start
A few useful answers.
Does AI arrive knowing our ecommerce business?
No. Build its knowledge from your approved information and connected sources. Review generated articles, configure company guidance and test your actual questions before enabling customer-facing replies.
Can a person take over?
Yes. Your team can handle requests that need judgment, authorization or information AI does not have. Use assignments, internal discussion and customer history to give the next person the context.
Does every connected system allow AI to make changes?
No. Read-only connections provide permitted information; they do not authorize refunds, cancellations, account changes or other actions. Check each connector’s capabilities and keep decisions with the appropriate person or system.
What does a workspace cost?
Chat, Tickets or Phones start at $5/month each with five human support agents included. Support is $10 and Business is $15. Additional services, AI add-ons and usage can be charged separately. The pricing page explains the starting costs.