> 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.

## Learn by Building <a href="#implementation-path" id="implementation-path"></a>

Follow these ten guides in order to build one Platform workflow end to end, from a test service to a governed deployment. Each step ends with a result you carry into the next one, and each guide closes with a **You are here** footer that points to the next step. You can also enter at any step. The tables below match guides to your starting point.

Before step 1, confirm the assigned [region and service hosts](https://docs.concurrence.com/developer-guide/getting-started/regions-and-endpoints.md) and choose [credentials](https://docs.concurrence.com/developer-guide/getting-started/credentials.md). For the mental model behind the steps, read [How a Call Works](https://docs.concurrence.com/platform-overview/how-a-call-works).

{% stepper %}
{% step %}

### 1. Create a test service

[Create a Test Service](https://docs.concurrence.com/developer-guide/guides/create-a-test-service.md): author an agent and Context Graph, pin their versions on a service, and read the selection back.

**Result:** recorded component IDs, selected versions, a verified test service, and a cleanup owner.
{% endstep %}

{% step %}

### 2. Run your first verified conversation

[First Verified Conversation](https://docs.concurrence.com/developer-guide/guides/first-verified-conversation.md): run the starter against fixtures or your test service, read the answer back from history, and close the conversation.

**Result:** an evidence file with an inspected answer and verified closure.
{% endstep %}

{% step %}

### 3. Run your first Console conversation

[First Console Conversation](https://docs.concurrence.com/developer-guide/guides/first-console-conversation.md): start a text conversation on the same service in the Console and inspect its execution details.

**Result:** a text answer, inspected tool evidence, and an ended session.
{% endstep %}

{% step %}

### 4. Add a tool

[Pass Context to Tool Parameters](https://docs.concurrence.com/developer-guide/guides/conversation-context.md): declare accepted context on the service and bind it to a tool parameter in the active Context Graph state.

**Result:** a tool that receives a verified value from your application.
{% endstep %}

{% step %}

### 5. Verify an integration action

[Verify an Integration Action](https://docs.concurrence.com/developer-guide/guides/verify-an-integration-action.md): exercise an external write through its test operation and a conversation, then confirm the outcome at the target.

**Result:** independent evidence of the intended change, or an explicit unresolved outcome with a reconciliation owner.
{% endstep %}

{% step %}

### 6. Add escalation and safety

[Add Escalation and Safety](https://docs.concurrence.com/developer-guide/guides/escalation-and-safety.md): configure caller verification, forwarding, and an escalation path, and test the safety behavior on your runtime.

**Result:** tested verification, transfer, and emergency cases on the test service.
{% endstep %}

{% step %}

### 7. Build and prove with simulations

[Build and Prove](https://docs.concurrence.com/developer-guide/guides/build-and-prove.md): test representative cases with simulations, review the evidence, and promote selected versions with a recovery plan.

**Result:** acceptance evidence, a selected configuration, and an agreed release decision.
{% endstep %}

{% step %}

### 8. Run a voice session in your app

[Run a Voice Session in Your App](https://docs.concurrence.com/developer-guide/guides/app-voice-session.md) (beta): get a one-use ticket from your backend and stream audio between your app and a realtime voice service.

**Result:** a voice session from your own app, recorded like a call.
{% endstep %}

{% step %}

### 9. Operate and improve

[Operate and Improve](https://docs.concurrence.com/developer-guide/guides/operate-and-improve.md): find a run, intervene where supported, reconcile incomplete effects, and turn a failure into a test case. Use [Troubleshoot an Integration](https://docs.concurrence.com/developer-guide/guides/troubleshooting.md) when a request or outcome needs investigation.

**Result:** a traceable run, an appropriate intervention, and a repeatable evaluation case for the next change.
{% endstep %}

{% step %}

### 10. Govern a deployment

[Govern a Deployment](https://docs.concurrence.com/developer-guide/guides/govern-a-deployment.md): record access, provisioning, regional boundaries, and operating responsibilities before a customer workflow goes live.

**Result:** a deployment record your team reviews before each material change.
{% endstep %}
{% endstepper %}

## Start Your First Conversation

| Your starting point                                                 | Follow this guide                                                                                                                               | Finish with                                                                              |
| ------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| You want to try the SDK without workspace access                    | [First Verified Conversation](https://docs.concurrence.com/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 an authoring credential and test workspace, but no service | [Create a Test Service](https://docs.concurrence.com/developer-guide/guides/create-a-test-service.md)                                           | Agent, graph, version pins, and service readback evidence.                               |
| You have Console access and a configured test service               | [First Console Conversation](https://docs.concurrence.com/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](https://docs.concurrence.com/developer-guide/guides/first-verified-conversation.md), **Provisioned test service** | An answer read back from service history and verified closure.                           |

## More Guides

These guides sit beside the path. Use them when your workflow needs the capability.

### Context and Data

| Task                                                                                                                | Verified outcome                                                                                                             |
| ------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| [Set Context on a Live Voice Call](https://docs.concurrence.com/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               |
| [Connect Data to a Verified Action](https://docs.concurrence.com/developer-guide/guides/data-to-verified-action.md) | Tested data meaning, queryable record, verified agent access, and target outcome, including correction and concurrency cases |

### Deliver Through a Channel

| Task                                                                                                                             | Verified outcome                                                                                                                      |
| -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| [Test a Managed SMS Workflow](https://docs.concurrence.com/developer-guide/guides/test-managed-sms.md)                           | For a Concurrence agent on a workspace service: provisioned routing, send/delivery evidence, and suppression behavior                 |
| [Launch an SMS Outreach Campaign](https://docs.concurrence.com/developer-guide/reference-guides/launch-sms-outreach-campaign.md) | For your own backend on the Channel Manager API: a controlled message, delivery read, signed reply, opt-out check, and go-live record |

### Test Voice Agents

| Task                                                                                                  | Verified outcome                                                                                                                              |
| ----------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| [Run Arbiter Voice Tests](https://docs.concurrence.com/developer-guide/guides/arbiter-voice-tests.md) | With provisioned Arbiter access: an applied suite, black-box calls to an approved phone target, an exit-code gate, and JSON and JUnit reports |

### Govern and Operate

| Task                                                                                                                | Verified outcome                                                                                                   |
| ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| [Set Up Organization SSO](https://docs.concurrence.com/developer-guide/guides/organization-sso.md)                  | An approved user signs in to the intended workspace and an unauthorized user is refused                            |
| [Build Your Own Operator Console](https://docs.concurrence.com/developer-guide/guides/build-an-operator-console.md) | Beta: a signed-in operator who takes over a text conversation or phone call from your own screen and hands it back |
| [Troubleshoot an Integration](https://docs.concurrence.com/developer-guide/guides/troubleshooting.md)               | Failing boundary, reconciliation action, and escalation evidence                                                   |

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](https://docs.concurrence.com/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](https://docs.concurrence.com/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](https://docs.concurrence.com/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.

## Reference Guides

The **Reference Guides** group holds guides for specific integrations and compatibility questions outside the main path:

* [Classic Authentication](https://docs.concurrence.com/developer-guide/reference-guides/authentication.md) - the Classic API key exchange.
* [Integrate Channel Manager Through the API](https://docs.concurrence.com/developer-guide/reference-guides/integrate-channel-manager.md), [Launch an SMS Outreach Campaign](https://docs.concurrence.com/developer-guide/reference-guides/launch-sms-outreach-campaign.md), [Reconcile a Channel Manager Attempt](https://docs.concurrence.com/developer-guide/reference-guides/reconcile-channel-manager.md), [Send Email With a Channel Manager Template](https://docs.concurrence.com/developer-guide/reference-guides/channel-manager-email-templates.md), and [Connect a Channel Manager Voice Receiver](https://docs.concurrence.com/developer-guide/reference-guides/channel-manager-voice-receiver.md) - run your own runtime on Concurrence channels.
* [Compatibility and Retirements](https://docs.concurrence.com/developer-guide/reference-guides/compatibility-and-retirements.md) - the correct Classic path and release history.


---

# 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=<question>&goal=<user_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.
