> For the complete documentation index, see [llms.txt](https://docs.videsk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videsk.io/es-dashboard/sucursales/crear-sucursal.md).

# Crear sucursal

A continuación te explicamos como crear una sucursal.

Una sucursal contiene un conjunto de POC (Point of Contact) y segmentos, los cuales pueden ser asignados posteriormente de haber creado una sucursal.

{% @arcade/embed url="<https://app.arcade.software/share/YI0awj2ZnNnd72O8AVg0>" flowId="YI0awj2ZnNnd72O8AVg0" %}

## Campos

### Nombre

Esta será el nombre de la sucursal y se retorna como valor mediante nuestra Rest API, por lo que podría mostrarse o no dependiendo de tu integración.

### ID

Este campo te permite definir un ID interno para tu sucursal de esta manera es más sencillo buscarla a través de nuestra Rest API.

### ID de integración

Este campo permite definir un ID que tu software QMS requiera utilizar o incluso para exportaciones a sistemas externos.

### Dirección

Este campo es opcional y se retorna como valor en nuestra Rest API, por lo que podría ser visible dependiendo de tus integraciones.

### Segmentos

Este campo permite seleccionar los segmentos que estarán asociados a esta sucursal.

{% hint style="warning" %}
Deberás asignar al menos 1 segmento antes de generar llamadas a través de POC.
{% endhint %}


---

# 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.videsk.io/es-dashboard/sucursales/crear-sucursal.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.
