respondendo.app
  1. 1

    POST to the API

    Phone, agent and variables in a JSON. The response comes right away, with the call id.

  2. 2

    The call goes out

    It goes out from a number with the area code of the person, which raises the chance of an answer.

    ~1.2 s to ring
  3. 3

    The person answers

    The AI speaks with your script, using the variables, and listens to the reply like in a conversation.

  4. 4

    Tool called

    When it needs data from you, the AI calls your URL and goes on with the response.

  5. 5

    Call ends

    After hanging up, you get the recording, the turn by turn transcript and a summary.

  6. 6

    Result in the webhook

    A POST to your URL with the full result, ready to store in your system.

The request

A JSON and nothing else

With an agent created in the dashboard, the request has three fields. The variables go into the script wherever you wrote {{primeiro_nome}}.

  • Without an agent, send prompt, modo and voz in the request itself.
  • The response comes with the id and your balance after the reservation.

curl

curl -X POST "https://api-homologacao.respondendo.app/v1/ligacoes" \
  -H "Authorization: Bearer rsp_sua_chave" \
  -H "Content-Type: application/json" \
  -d '{
    "telefone": "5511988888888",
    "agente_id": 12,
    "variaveis": {
      "primeiro_nome": "Antônio",
      "visita": "quinta às 15h"
    }
  }'

// 202
{ "id": 512, "status": "em_andamento", "saldo": 93.470 }

Examples

What you can do with a call

Four common uses. In all of them the request is the same: only the agent script, the variables and the tools change.

Visit confirmation

The AI calls the day before, confirms the time and, if the person cannot make it, offers another free slot from your calendar.

Variables
primeiro_nome, visita
Tool
consultar_horarios
In the result
Confirmed, rescheduled or cancelled, with the new time in the summary.

Due date reminder

Politely reminds about the due date, answers questions about amount and date and, if asked, sends a new copy of the bill.

Variables
primeiro_nome, valor, vencimento
Tool
segunda_via
In the result
The date the person said they will pay.

Satisfaction survey

Calls after the service, asks two or three short questions and stores the score in your system during the conversation.

Variables
primeiro_nome, atendimento
Tool
registrar_nota
In the result
The score from 0 to 10 and the comment of the person.

Callback to new leads

Calls within minutes whoever filled in the form on your site, understands the interest and hands the contact to the sales rep.

Variables
primeiro_nome, interesse
Tool
registrar_interesse
In the result
The interest, the budget and the best time for the sales rep to call.

In practice

What happens in each case

Not every call is answered. Each situation has its own record, in the dashboard and in the result.

Nobody answered
The call ends as not answered and the result arrives with atendida: false.
Went to voicemail
The call is marked as voicemail and the result arrives with caixa_postal: true.
Busy or wrong number
The dashboard history shows the status: busy, rejected, number does not exist or carrier error.
Many at once
Each POST is one call, and they run in parallel up to the channel limit of your account. The POST response brings canais_permitidos and em_andamento.
Changed your mind
DELETE /v1/ligacoes/{id} removes the call from the queue or ends the one in progress.
Outside calling hours
Lists sent from the dashboard follow the calling hours you set: outside them they stop and resume the next day.