> 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.md). # Guides Task guides for configuring, testing, operating, and governing Concurrence workflows, with prerequisites and evidence of completion. Use these guides to complete an implementation or operating task. Each identifies the required access and configuration, the steps to follow, and the evidence to inspect. Endpoint pages supply the underlying request and response contracts. ## Start Your First Conversation | Your starting point | Follow this guide | Finish with | | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | | You want to try the SDK without workspace access | [First Verified Conversation](/developer-guide/guides/first-verified-conversation.md), **Local walkthrough** | An evidence file from a credential-free fixture run, an expected rejection, and cleanup. | | You have Console access and a configured test service | [First Console Conversation](/developer-guide/guides/first-console-conversation.md) | A text answer, inspected execution details, and an ended session. | | You have a test service and Platform API credentials | [First Verified Conversation](/developer-guide/guides/first-verified-conversation.md), **Provisioned test service** | An answer read back from service history and verified closure. | ## Choose a Workflow | Task | Verified outcome | | ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | [Build and Prove](/developer-guide/guides/build-and-prove.md) | Reviewed service configuration, bounded test evidence, and promotion/recovery plan | | [Pass Context to Tool Parameters](/developer-guide/guides/conversation-context.md) | Service schema, selected state-to-tool binding, and verified context received by a test tool | | [Set Context on a Live Voice Call](/developer-guide/guides/live-call-context.md) | A verified value set on a live call from your backend and received by a context-bound tool, never by the model | | [Operate and Improve](/developer-guide/guides/operate-and-improve.md) | Located run, appropriate intervention, reconciliation, and a repeatable evaluation case | | [Connect Data to a Verified Action](/developer-guide/guides/data-to-verified-action.md) | Source record, queryable entity, agent access, and independently verified target outcome | | [Verify an Integration Action](/developer-guide/guides/verify-an-integration-action.md) | Authorized operation and independently confirmed target outcome | | [Test a Managed SMS Workflow](/developer-guide/guides/test-managed-sms.md) | Provisioned routing, send/delivery evidence, and suppression behavior | | [Integrate Channel Manager Through the API](/developer-guide/guides/integrate-channel-manager.md) | Your own runtime, scoped API access, signed inbound replies, reconciled delivery, and a controlled acceptance test | | [Govern a Deployment](/developer-guide/guides/govern-a-deployment.md) | Access, availability, region, and operational responsibilities recorded | | [Scribe: Capture to Finalized Note](/developer-guide/guides/scribe-capture-to-note.md) | Provider-owned session, reviewed artifact, and version-checked finalization | | [Troubleshoot an Integration](/developer-guide/guides/troubleshooting.md) | Failing boundary, reconciliation action, and escalation evidence | | [Compatibility and Retirements](/developer-guide/guides/compatibility-and-retirements.md) | Correct Classic path and release history | The guides cover Build, Evaluate, Operate, Improve, Data, and Govern tasks. The standard Console sidebar emphasizes Home, Build, Evaluate, Data, and Govern; additional permitted pages remain reachable through Console search. Each guide connects those entry points to the owning API and supported client instructions. Confirm [capability availability](https://docs.concurrence.com/platform-overview/capability-availability) before relying on a preview or managed channel. ## Build a Knowledge-Base Agent The knowledge-base playbooks below describe a particular build workflow. Confirm their API, data-access, and tooling prerequisites before applying them to your deployment. Start with [Getting Started](/developer-guide/getting-started.md) for the general Platform and Classic integration paths, then read the end-to-end playbook before its methodology deep dive. 1. [Build a Knowledge-Base Agent End to End](/developer-guide/guides/build-a-kb-agent-end-to-end.md) - the full path: load your data, assign roles, build the agent, and test it. 2. [Knowledge-Base Agent: Retrieval and Build Methodology](/developer-guide/guides/building-a-knowledge-base-agent.md) - the deep-dive behind the build step: the retrieval-architecture decision and the measurement-driven build loop, grounded in a controlled bake-off. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.concurrence.com/developer-guide/guides.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.