Per-call instructions

For calls you place yourself over the calling API, and for web sessions. Campaigns don’t take them.On a web session, the instructions and any variables ride in the token the browser gets. Don’t put secrets there.

Sending one

A complete call. The variables say who the farmer is. The highlighted line says what is different about today:

A late follow-up, dialed by hand

curl https://api.upliftai.org/v1/realtime-assistants/$ASSISTANT_ID/call \
  -H "Authorization: Bearer $UPLIFT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "toNumber": "+923001234567",
    "variables": {
      "crop": "cotton", "district": "Multan", "lastOrder": "May"
    },
    "additionalInstructions": "This is a late follow-up. Once you have confirmed you are speaking to the right person, apologize for the delay before anything else."
  }'

additionalInstructions takes up to 2,000 characters and lands right after the prompt. The only thing after it is the caller record, when you send variables. Nothing else about the assistant changes, and the text is not returned on any read. The call request reference has the rest of the body.

What to put in it

Steering, not facts. The prompt says who the assistant is and how it works. The instruction says what is different about this one call:

You spoke to them on Monday and they asked to be called back today. Open by saying you are calling back as promised, then continue with the order as usual.

Their last delivery arrived two days late. If they bring it up, apologize once and do not explain why. Then confirm this order as usual.

Facts about the caller, like the order number or the crop, belong in variables.

Getting started

Concepts

Assistants

Tools

Personalization

Calling

Campaigns

Webhooks

Testing

API Reference

Sending one

What to put in it

Keep it to a few lines

​Sending one

​What to put in it

​Keep it to a few lines

Sending one

What to put in it

Keep it to a few lines