Choose your first outcome
Answer a customer question
Start in ResponseCX with one policy. Finish with an answer checked against your source.
Trial helpdesk automation
Connect Gorgias and replay a ticket. Inspect its draft and review or escalation decision.
Connect your AI assistant
Verify the workspace through MCP, then authorize one bounded task.
Build commerce locally
Create an order and check stock with the embedded engine. No hosted credentials needed.
What to have ready
Keep your IDs and results in the copyable onboarding record if you plan to continue across sessions or hand the task to an AI assistant. For the first agent, bring a work email, your company name, and one authoritative source such as your shipping FAQ or returns policy. Pick a colleague who can judge whether its answers are correct. For a helpdesk workflow, also have permission to connect your helpdesk and store. The accelerated trial below uses Gorgias, with Shopify when store context is needed. Without connector access, start with the agent walkthrough while your administrator connects the systems. For MCP, you need an MCP-capable assistant, its own model access, and an authorized connection to each StateSet server you plan to use. A browser login alone does not configure that connection.Signup to first answer
1
Open the right workspace
Open signup and complete the work-email sign-in flow.
The default signup route leads into trial onboarding. Review the plan and terms shown;
use your existing organization if your team has already joined.Check: you can open the intended organization, not just the sign-in screen.
2
Create one support agent
Continue to Setup. In Choose agent, select a use
case and choose Create my agent.Check: the agent exists in your workspace. Keep its ID for tests and later handoffs.
3
Add your policy source
In Test & launch, choose Add sources first if the agent has no knowledge. Import one
relevant policy and wait for processing before testing an answer.Check: the processed source contains the policy you want the agent to use.
4
Verify three answers
Run the three-question walkthrough.
Test a known policy, missing context, and a policy boundary. Keep the conversation or
evaluation result so your team can inspect it.Check: a reviewer can explain why each answer is acceptable or what needs correcting.
5
Decide where to launch
Install the widget or connect a customer-facing channel only when the answers and escalation
behavior match your policy. Follow the channel setup
and verify the installed or connected surface independently.Check: distinguish a successful test from a channel that customers can actually reach.
Test & launch uses a real chat runtime. Treat its test messages as real generations, not
a static mock. Workflow shadow mode is a separate setting in the automation engine;
it does not make the Response widget a shadow-only experience.
Measure time to value with outcomes
Use these as milestones, not a guaranteed deployment schedule:
For connected workflow onboarding, aim for a first real draft within a 30-minute onboarding
session when credentials and source material are ready. This is the engine team’s onboarding
target, not a service guarantee; imports, access approvals, and connector health can extend it.
The workflow funnel reports actual progress through
first_event_received, first_draft, and
first_reply_sent. Use the workflow trial
to find the next incomplete step rather than restarting setup.
Keep a record you can resume
Copy this worksheet into your project notes before starting. It is a suggested team record, not an API payload or a file the platform imports. Complete only the fields for your chosen path; leave unverified results asunknown and unused services as not used.