> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/developer-guide/guides/first-console-conversation.md). # First Console Conversation Sign in to the Console, choose a configured test service, start a text conversation, inspect its answer and tool evidence, and end the session. Test a configured agent service in your browser. You will send a synthetic question, inspect the answer and available execution details, and end the conversation. You do not need to install an SDK or create an API key for this walkthrough. If you are still arranging workspace access, use the credential-free local walkthrough in [First Verified Conversation](/developer-guide/guides/first-verified-conversation.md). ## Before You Start Ask your workspace administrator or implementation contact for: * The Console address and account with access to the intended test workspace. * An active test service that supports the Playground's text mode, with published versions of its linked agent and Context Graph. * Confirmation that the service can answer an ordinary text question without patient context, production write tools, or outbound messaging actions. The Playground uses the service's configured data and tools. A synthetic question alone does not isolate those resources. Use a service reviewed for this exercise. ## 1. Sign In and Choose Your Workspace Open the Console address supplied for your deployment. The US entry point is [console.platform.amigo.ai](https://console.platform.amigo.ai). Choose **Sign in with Google**, or enter your email address and choose **Email me a sign-in link**. Use the account granted access to your workspace. On the workspace selection screen, select the agreed test workspace; check its name, ID, and region when shown. **Check:** You can enter the intended workspace. If it is missing, ask the administrator to check your membership and Console address. ## 2. Open Your Test Service Open **Prove > Playground**. Find the agreed service and choose **Text** on its card. Use **Load more services** if the service is not in the first group. Only active services appear in this list. The service's **Details** link opens its configuration. Check the service and selected versions with your implementation contact if they differ from the test setup. A card marked **Active** still needs usable agent and Context Graph versions. **Check:** The text Playground opens for the intended service. Resolve a **Service is not ready for testing** banner before continuing. ## 3. Start a Text Conversation Choose **User first**. Open the arrow beside **Start text** to inspect **Entity ID**, and clear any remembered value for this exercise. For a later test that requires patient context, use only the synthetic UUID or phone number supplied for that test. Select **Start text**. In **User first** mode, the conversation waits for your message. **Agent first** instead requests an opening agent response when the conversation starts. **Check:** The session shows **Live** and a message composer. A blank conversation is expected until you send the first message in **User first** mode. ## 4. Send a Question and Inspect the Result Send this question to the reviewed test service: ``` What information would a scheduling team need before considering an appointment change? Do not book or change anything. ``` Press **Enter** to send; **Shift+Enter** inserts a new line. Wait for the answer before sending a follow-up. For this exercise, a useful answer identifies prerequisites such as the existing appointment, the requested change, available alternatives, and authority to make the change. Wording varies by service configuration. If the answer claims to have changed an appointment, stop and investigate the tool evidence with the implementation owner. Open **Timeline** to inspect the turn and available tool details. Open **Context Graph** to follow the displayed state. Outside the message field, `4` toggles Timeline and `2` toggles Context Graph. Missing details can reflect unavailable evidence; they are not proof that no tool ran. **Check:** Your message and a completed answer are visible. Record the expected result, observed answer, and any unexpected tool activity. An answer about scheduling is not evidence of a booking or of clinical quality. ## 5. End and Record the Conversation Choose **End** after the answer is complete and any unexpected work has been reconciled. Confirm the **Ended** state and check for an error banner. **New text** starts a separate conversation; use it only when you intend to begin another test. Record the workspace, service, configuration, test time, input, and observed result in your team's test record. When you need independent history and closure verification, inspect the conversation through [Operate > Runs](/developer-guide/guides/operate-and-improve.md) and its conversation detail, or use the [SDK starter](/developer-guide/guides/first-verified-conversation.md). The Console's end control closes the conversation; it does not erase retained history or reverse external changes. ## Troubleshooting | What you see | What to check next | | -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | The workspace is missing | Confirm the signed-in account, membership, and Console address with the workspace administrator. | | **No active services found**, or your service is missing | Choose **View Services** to check the agreed service's configuration, or **Load more services** when available. Ask the owner to resolve inactive or missing test configuration. | | **Service is not ready for testing** | The banner identifies a linked agent or Context Graph with no published versions. Have the configuration owner follow **Create agent version** or **Create context graph version**, then return to the test. | | Starting opens an Entity ID error | Clear the remembered value for this context-free exercise, or supply the agreed synthetic UUID or phone number. | | The session is live but no greeting appears | In **User first**, send the opening message. In **Agent first**, inspect any reported start error. | | Sending or ending reports an error | Preserve the workspace, service, time, and any conversation identifier. Inspect durable history and lifecycle before repeating the action; follow [Troubleshooting](/developer-guide/guides/troubleshooting.md). | ## Continue * [Build and Prove](/developer-guide/guides/build-and-prove.md) connects service configuration to repeatable testing and release. * [Verify an Integration Action](/developer-guide/guides/verify-an-integration-action.md) adds independent evidence from a configured test system. * [Playground and Interactive Testing](https://docs.concurrence.com/testing/testing/playground) explains voice mode, inspection, and related evaluation tools. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.concurrence.com/developer-guide/guides/first-console-conversation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.