/solicitud. No account is required.
Submission flow
Enter your contact details
Fill in your full name, email address, and optionally your phone number, ID document, and company or department. The email address is the key used to look up your ticket later.
Classify your request
Select a ticket type (for example,
SOLICITUD or INCIDENTE) and enter a category. You can optionally add a subcategory and an subject line.Describe the problem
Write a detailed description of your issue (minimum 10 characters). The more detail you provide, the faster support can respond.
Submit the form
Click ENVIAR SOLICITUD. The portal sends the request to the API and displays a confirmation with your ticket label and SLA deadline.
Form fields
The following fields map to theTicketCreatePayload interface.
Full name of the person submitting the ticket. Minimum 3 characters.
Email address. Used to authenticate ticket lookups — you must provide the same email when tracking.
Ticket type. One of:
PETICION, QUEJA, RECLAMO, SUGERENCIA, INCIDENTE, SOLICITUD, CONSULTA. Determines the automatic priority assigned to the ticket.Category of the request (e.g.
Plataforma Académica).Detailed description of the problem or request. Minimum 10 characters.
Priority level:
BAJA, MEDIA, ALTA, or URGENTE. Set automatically based on the selected tipo.ID document number. Optional.
Phone number. Optional. Maximum 30 characters.
Whether the phone number supports WhatsApp. Defaults to
false.Company, faculty, or department. Optional. Maximum 150 characters.
Subcategory for more specific classification. Optional.
Brief subject line for the ticket. Optional. Maximum 200 characters.
Target area to route the ticket to. Optional. Defaults to
MESA.API endpoint
Example request
Response
On success, the API returns aTicketCreateResponse object.
Unique internal identifier (UUID) for the ticket. Used for direct API calls.
Human-readable ticket reference (e.g.
TK-2024-0001). Save this to track your ticket.Initial status of the ticket. Always
ABIERTO on creation.The ticket type as submitted.
The priority assigned to the ticket.
Number of hours within which the ticket should be resolved per SLA.
ISO 8601 timestamp of when the ticket was created.
ISO 8601 timestamp of the SLA deadline.
Confirmation message from the server.