Look up the right shipment
Use supported read-only store context and verify the customer before sharing private order information.
Built around your business
Remember the subscriber, not just the shipment.
Bring recurring delivery questions, account requests and product conversations together. Help your team understand the current issue and the customer’s earlier experience.
A connected support dayThe next person
The next person
gets the whole story.
A subscriber had an issue last month and asks about this month’s shipment. The next reply should acknowledge the previous conversation without assuming the same outcome applies.
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 Subscription boxesUseful 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 current schedule
Publish cutoff dates, shipping policies and the available ways to update a subscription. Keep the knowledge current as the schedule changes.
Route subscription changes
Assign cancellation, skip and billing requests to the person or system authorized to make them. Do not promise a change from a read-only lookup.
Follow through on exceptions
Keep the earlier resolution and current request together. Use an internal task for the colleague who needs to confirm the next step.
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 →“When does this month’s box ship?”
“How do I request a subscription change?”
“Can someone check the issue I reported last month?”
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 subscription boxes 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.