Keep exceptions bounded
Record why a decision applied without making it everyone else's default.
Them AI for Marketplaces
Keep both sides working from a clearer shared reference.
Marketplace operations involve exceptions, competing needs, and decisions that outlive the original discussion. Them AI helps teams keep the reasoning behind seller guidance, support practices, and operating changes available for people to check before reuse.
Mac-only for now. Free during the beta (invite-only).
Seller operations reviewShared room
You with your team
Should we reuse this earlier exception?
Them AI with company contextThe extension covered a delayed catalog submission, not an ongoing waiver of seller requirements. Check the reason, supporting evidence, and operations owner's approval before treating it as a precedent for another seller.
↗ Illustrative exception reviewReview with Marketplace operations lead
After human approvalException and its limits
A useful record for the next person.
Illustrative workflow. Not a live conversation.
The work gets better when the context stays.
Good judgment belongs
with the whole team.
Align operating explanations
Give seller and support teams the same reviewed reference to check.
Carry lessons forward
Preserve the conditions behind an incident response or operating change.
In the day-to-day
Work your team can bring to Them AI.
Start with the question. Keep the source. Make a person responsible for what comes next.
Marketplaces room Example 01
Does that exception apply here?
Compare the submission delay, supporting evidence, and affected requirements with the earlier decision. Ask the operations owner to review differences before communicating an exception to this seller.
↗ Illustrative seller guidanceClarify seller guidance
Review an operating question against the current approved guidance. Keep the evidence and exception conditions together so the next response does not depend on somebody remembering an old conversation.
See how the workflow fits
- Bring
- Approved seller guidance
- Review
- Operations owner checks applicability
- Keep
- Sourced guidance explanation
Marketplaces room Example 02
Why did these teams answer differently?
One response used an earlier seller guide; the other used the current reviewed cutoff. Confirm the applicable guidance with its owner before drafting a corrected explanation.
↗ Illustrative support alignmentResolve inconsistent support explanations
Bring conflicting explanations to the policy owner before drafting a response. Keep the approved interpretation available to both operating teams, with a clear path for unresolved questions and exceptions.
See how the workflow fits
- Bring
- Authorized, redacted support examples
- Review
- Policy owner resolves conflicts
- Keep
- Reviewed response method
Marketplaces room Example 03
What would make us reconsider this approach?
Manual seller onboarding was retained while category requirements were unsettled. Revisit the approach once those requirements are approved and the operations team can evaluate a consistent review method.
↗ Illustrative operating decisionExplain an operating tradeoff
Keep the alternatives and constraints behind an operating change. Ask the decision owner which conditions should trigger another review instead of teaching the chosen approach as a permanent rule.
See how the workflow fits
- Bring
- Authorized operating decision notes
- Review
- Decision owner checks assumptions
- Keep
- Owned tradeoff record
Marketplaces room Example 04
What should we check before trying the fix?
Confirm whether listing imports failed before or after validation, which records were affected, and who owns recovery. Those checks determine whether the earlier fix is relevant.
↗ Illustrative incident reviewKeep a marketplace incident lesson
Review a non-sensitive incident summary with operations and support. Distinguish confirmed causes from theories, then decide which diagnostic questions should become part of the next team's method.
See how the workflow fits
- Bring
- Approved non-sensitive incident summary
- Review
- Incident owner checks evidence
- Keep
- Reviewed diagnostic checklist
These are example workflows to evaluate, not customer results. Connected agents use their own tools; Them AI is the shared context and review workspace.
From useful work to reusable knowledge
The conversation is
only the beginning.
Memory keeps the facts and decisions. Skills keep a way of working. People decide what deserves to become a shared reference.
Meet Rooms and the Collective- 01
Bring the context
Illustrative exception review
- 02
Make the human call
Marketplace operations lead reviews the sources and proposed record.
- 03
Keep the method
Operating exception review
Make it real
Start with one repeated seller question
Use approved general guidance and a synthetic case. Check whether a second operator reaches the right reviewer with the right evidence. Mac-only for now. Free during the beta (invite-only).
Discuss a design partnership
Before you begin
A few things
worth knowing.
Does Them AI make seller enforcement decisions?
No such automation is promised. Use these workflows to prepare reviewed context; your authorized team remains responsible for decisions and external actions.
What should stay outside the pilot?
Material not authorized for all workspace members. Human access is organization-wide; client-scoped MCP includes own-client and firm-wide approved records. Start with redacted or synthetic examples.
How do we keep old exceptions from spreading?
Give each explanation an owner and explicit conditions. Review a general method separately instead of copying the exception into it.
What does the current beta include?
Shared rooms, memory with sources and review status, reusable skills, and MCP access for connected agents. Mac-only for now. Free during the beta (invite-only). Human room and memory access is organization-wide. Client-scoped MCP feeds restrict agent retrieval to that client's approved records plus approved firm-wide material. Do not treat a room as a private boundary for individual members. Read the access boundaries.
Bring one real workflow
Make the next project
better informed than the last.
Start with a question your team keeps answering. Bring the sources, the people who know, and the decisions worth keeping.
Mac-only for now. Free during the beta (invite-only).