Learn & discover / Learn
Choose a question worth answering first.
You do not need to read everything before understanding the product. Start from the decision in front of you: how a customer request becomes work, what the team must approve, or what a responsible implementation should prove.
Learn
Examples show the behavior. Docs explain the reference. Practice establishes whether your setup works.
I want to understand the business flow
Start with a product example, then identify the customer request, the context used and the resulting record. Ask whether the result is prepared, awaiting approval or actually recorded. This gives you a concrete question to take into the platform reference instead of a list of feature names.
I want to judge fit before a conversation
Pick the industry or solution page closest to your business and compare its stated conditions with how you work today: which requests arrive, who decides, and what a person must still confirm. Bring that comparison to a conversation; examples describe the product and do not promise availability for a specific account.
I need to configure the operation safely
Read the guides with the product reference alongside them. Identify who owns the information, what the Agent may do and who handles exceptions. A configuration decision should have a testable consequence, especially when it affects a customer's order, booking or payment expectation.
Availability and responsibility
Educational material and product examples are available to inspect.
Before you decide
Should I begin with the guides or Docs?
Use the practical guides for workflow questions, the product reference in Docs for exact behavior, and the product examples to see how a request moves from message to record.
Are the public examples real customer case studies?
No. They are labeled product illustrations. Verified customer outcomes require separate evidence and permission.