From request to recorded outcome

Think of an IntraCord service as an agreement about what should happen to a customer request. The assistant's instructions, channel assignment and connected systems together determine what it can complete.

Before the customer arrives

Prepare the assistant's task, a model setup and any reference documents. Attach the actions it may use and define the conditions for involving a colleague. A phone number's inbound assignment or a website embed selects the assistant that receives the conversation.

During the request

The assistant follows the conversation stages you configured. It uses the starting customer data, asks for missing details and can call configured business actions. Voice processing can use separate listening, reasoning and speaking services or a realtime speech model, depending on the selected setup.

The assistant only knows whether a business action succeeded if the connected system returns a usable result. Write the instructions so it confirms an action after that result, and offers a fallback when the system cannot complete it.

After the conversation

Review the conversation record, the values collected and any configured quality analysis. A webhook can deliver the result to another system. With API v2 you can also retrieve conversation inputs and results. These records let you check whether the service achieved its intended outcome.

Operate and test these boundaries separately: conversation design, channels, business data and deployment.