How Ringg works

Ringg is built from a few objects. An agent does the talking, a number connects it to the phone network, and a call, campaign or workflow decides who it talks to and when. Read this before building so the dashboard’s sections make sense; the dashboard tour shows where each one lives.

​

The core objects

​

How they connect

• A workspace owns its agents, numbers, knowledge bases, tools, campaigns and workflows. In a Ringg Space family, each Ringg Space owns its own; the primary keeps Logs, Analytics, Alerts and Settings for the whole family.
• An agent can use several knowledge bases and tools.
• An inbound agent answers on the number attached to it. An outbound agent has no fixed number: you pick a number or pool each time you place a call or start a campaign.
• A campaign combines one outbound agent, a number or pool, and a calling list.
• A workflow uses agents inside its steps, so one contact can get several conversations.
• Every call belongs to one agent. It shows in Logs, counts in Analytics, can be scored in Evals and can trigger Alerts.

​

The life of a call

Events reach your server twice: once when the call ends, and again when analysis is done.

1. Trigger. A test in the dashboard, an API request, a campaign row, a workflow step, a call to an attached number, a visitor in the web widget, or a WhatsApp message.
2. Agent and number. Ringg loads the agent. A voice call goes out from, or comes in on, a number.
3. Pre-call tools run before the call connects, so a CRM lookup is ready for the agent’s first sentence.
4. Conversation. The agent follows its prompt, looks things up in its knowledge base, and uses on-call tools such as a transfer or a booking API when the prompt says to.
5. Call ends. Ringg stores the transcript and, for voice, the recording.
6. Analysis. Ringg’s platform analysis (summary, key points, action items, a classification of the call) and your Advanced Analysis fields are extracted.
7. Post-call tools and events. Post-call tools push results to your systems. Event Subscription sends each event as it happens, from call_started to all_processing_completed.
8. Logs and Analytics. The call shows in Logs and rolls up into Analytics.

​

Dashboard and API

Everything can be built and run in the dashboard. The API covers agents, calls, campaigns, numbers, knowledge bases, call history, analytics and Ringg Spaces, so your backend can trigger calls and read results. Workflows and Alerts have no public API endpoints, and Evals are set up in the dashboard; use the dashboard for them.

​

Next steps