# Start building (/en/introduction/get-started/build-it-yourself)

> For AI agents: see the complete documentation index at [llms.txt](/llms.txt).

Most teams do not start by asking which Agora product to read first. They start by asking what kind of real-time problem they need to solve.

Use this page to map your product goal to the most useful documentation path.

## When to use this path [#when-to-use-this-path]

This is the right page when:

* you already know the product problem you want to solve
* you want to choose the right capability family before reading deep product docs
* you do not need an AI-assisted setup workflow first
* you want the shortest route from problem statement to relevant quickstart or product area

If you want an AI agent to help choose the route and bootstrap a starter, use [Start with AI](/en/introduction/start-with-ai) instead.

## Start from the problem you are solving [#start-from-the-problem-you-are-solving]

### Voice-first AI interaction [#voice-first-ai-interaction]

If users need to talk to an AI agent in real time, start with:

* [Conversational AI](/en/introduction/conversational-ai)
* [AI quickstart](/en/ai/get-started/quickstart)
* [Voice agent quickstart](/en/ai/choose-your-path/quickstart-coding)

This path is usually right for assistants, tutors, companions, service agents, and voice-enabled devices.

### Live voice, video, or interactive sessions [#live-voice-video-or-interactive-sessions]

If users need to join the same session and interact through live media, start with:

* [Real-Time Voice & Video](/en/introduction/realtime-audio-video)
* [Audio & Video](/en/realtime-media/rtc)
* [Voice & Video quickstart](/en/realtime-media/rtc/android/quick-start/build-from-scratch)

This path is usually right for calling, meetings, classrooms, social rooms, telehealth, and interactive livestreaming.

### Room messaging, state sync, or workflow coordination [#room-messaging-state-sync-or-workflow-coordination]

If the product depends on chat, presence, metadata, or event coordination, start with:

* [Messaging & Presence](/en/introduction/messaging-presence)
* [RTM / Signaling](/en/realtime-media/rtm)
* [IM / Chat](/en/realtime-media/im)

This path is usually right for in-room communication, control flows, collaborative state, and backend-triggered room actions.

### Cloud-side media workflows [#cloud-side-media-workflows]

If the media must be captured, processed, routed, or redistributed beyond the live session itself, start with:

* [Cloud Media Services](/en/introduction/cloud-media-services)
* [Cloud Recording](/en/realtime-media/cloud-recording)
* [Real-time Transcription & Translation](/en/realtime-media/speech-to-text)
* [Transcoding](/en/realtime-media/transcoding)
* [Server Media Processing](/en/realtime-media/rtc-server-sdk)

This path is usually right for archive, replay, moderation, server-side automation, and downstream content pipelines.

## Common combinations [#common-combinations]

Many production systems combine several of these paths:

* voice or video sessions plus [Messaging & Presence](/en/introduction/messaging-presence)
* AI interaction plus [Cloud Media Services](/en/introduction/cloud-media-services)
* live sessions plus [Cloud Media Services](/en/introduction/cloud-media-services)
* broadcast products plus [Cloud Media Services](/en/introduction/cloud-media-services)

## What to do next [#what-to-do-next]

If you are still evaluating the platform, read [About Agora](/en/introduction/about-agora) first. If you want the shared mental model before choosing a path, read [Core Concepts](/en/introduction/core-concepts). If you want an AI-assisted setup workflow, switch to [Start with AI](/en/introduction/start-with-ai).