Configure the agent
Choose its voice and languages, then define its Conversation Flow and call behavior.
HeyRik gives you the APIs and building blocks to create, connect, deploy, and improve sophisticated AI voice agents.
A HeyRik agent can answer inbound calls, place outbound calls, follow a structured conversation, use your knowledge, call your APIs, transfer to a person, and return the transcript and outcome to your application.
Define what a successful call should achieve. Then choose the agent, knowledge, number, and integrations needed to achieve it.
A call moves through four understandable stages.
Choose its voice and languages, then define its Conversation Flow and call behavior.
Upload documents or add URLs so answers come from approved information.
Assign a number for inbound calls or dispatch an outbound call through the API.
Read the transcript, recording, summary, cost, and extracted variables in your application.
Each part has one clear responsibility.
The AI that speaks and makes decisions during the call.
Real estate qualifierConversation FlowOrdered instruction sections that control how the agent behaves.
Ask budget → location → timelineKnowledge baseApproved facts the agent can use when answering questions.
Pricing PDF and refund policyPhone numberThe connection used to receive or place calls.
+91 business numberCustom APIA tool the agent can call during a conversation.
Check appointment availabilityCall resultThe record your application receives after the call.
Transcript, outcome, and extracted fieldsThe same platform primitives support different industries and outcomes.
Answer every inbound call, explain opening hours, collect the caller’s intent, book appointments, and route urgent requests.
Call new leads, understand requirements, qualify interest, capture structured fields, and schedule the right follow-up.
Identify the customer, answer from approved policies, look up information through a custom API, and create a ticket when needed.
Call a list of leads for reminders, surveys, renewals, or outreach, then export outcomes for your workflow.
This small example creates a support agent. The request defines its identity, opening line, and basic behavior.
curl -X POST https://server.heyrik.com/api/v1/agents \
-H "Authorization: Bearer $HEYRIK_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Support Agent",
"language": "en-IN",
"greeting": "Hi, thanks for calling Acme. How can I help?",
"config": {
"personality": "Friendly",
"prompt_sections": [
{
"order": 0,
"title": "Identity & Purpose",
"content": "You are Acme’s support agent. Resolve the caller’s question using approved company information."
},
{
"order": 1,
"title": "Guardrails",
"content": "Never invent policy details. If the answer is unavailable, offer a human follow-up."
}
]
}
}'{
"data": {
"id": "agc_9f2a1c30",
"name": "Support Agent",
"language": "en-IN",
"greeting": "Hi, thanks for calling Acme. How can I help?",
"config": {
"personality": "Friendly",
"prompt_sections": [
{ "order": 0, "title": "Identity & Purpose", "enabled": true },
{ "order": 1, "title": "Guardrails", "enabled": true }
]
},
"created_at": "2026-07-24T06:11:44.201Z"
}
}After a call finishes, your application can read the outcome and use it in the next workflow.
{
"data": {
"id": "call_1dd990f7",
"status": "completed",
"outcome": "resolved",
"summary": "Caller asked about the refund window. The agent explained the approved 14-day policy.",
"extracted_variables": { "order_id": "ORD-2048" },
"transcript_url": "https://…",
"recording_url": "https://…"
}
}Continue with the guide that matches what you need to build.