Leave one workflow and your number. The AI identifies itself, asks a few focused questions and prepares a structured brief.
Prompts, voices, telephony routes, campaigns, tools, post-call workflows, users and keys stay in one operational view. Teams and partners can manage the workflows they own, while controlled releases, CRM outcomes and human handover keep the customer experience accountable.
Hear Dring AI walk through a practical workflow, then submit the one your team wants to improve. Dring AI calls in about two minutes, identifies the need and helps our team shape the right project. Hear a Dring AI demo, see the callback flow or review the operations benchmark.
Pick a company and the panel shows its agents and everything they depend on. Partners see the companies they run; Dring sees all of them.
Start from a tested template for the use case, or build one from a blank agent: opening line, system prompt, end-call behaviour and the tools each agent may use. Speech recognition, language model and voice chosen per agent from the approved providers.
Inbound routing to an agent, outbound caller IDs, number provider and background sound. New numbers are requested from the panel and go live after telco setup.
Outbound lists with scheduling, calling days and windows, retry delays, do-not-call marking and SIP rules. Start, pause and monitor from the same screen.
Contact lists from a CSV upload or a CRM sync, grouped into segments, assigned to one or more campaigns, with do-not-call flags and a call history per contact.
What the agent can do during the call: knowledge search, price check, location lookup, policy retrieval, email, custom API requests with fallbacks. Bound to agents explicitly.
What happens after the call: analysis fields, then delivery by webhook or email, each step with its own outcome condition, green, yellow or red.
A voice library per language and brand. Bring your own voice from a supported provider with a voice ID, assign it per agent.
Your own API keys for speech, language and voice providers when your contract requires it, or Dring's managed keys by default.
Owner, operator and viewer roles per company. Recording download permission is a separate switch.
Keys for your integrations and a key-value store for the secrets tools need, never pasted into prompts.
Prompt and behaviour changes do not go live on save. They enter a release pipeline: the test suite runs, judges score, and the change is deployed in stages. Actions and workflow steps that carry no conversational risk apply immediately.
Two screens the operations team lives in: what was used, and what is running right now.
Minutes and conversations per company, per agent and per channel for any period. The same numbers your invoice is built on, so there are no surprises.
Concurrent calls in progress, by company and by line, with capacity headroom. Peak-hour inbound and a running outbound campaign side by side.
Partners work in the same Dring panel with account-level roles, reports and tested release controls. They can create customer workspaces from ready agent templates, manage lines and campaigns, and take each deployment live with Dring running telephony, orchestration and analysis behind it. A branded customer-facing layer can be scoped separately when the model requires it.
Every agent in the catalogue started as a tested template for its use case: order status, appointment booking, collections, qualification and more, each adapted to a brand's tone, policies and tools. A new agent follows the same path from the panel: pick a template, or start from a blank agent, and adapt the opening line, prompt, voice and tool access.
Every outbound campaign carries its own calling window, calling days and retry rules. Nothing dials outside them.
Set the calling window and the days a campaign is allowed to dial, per campaign. A retry rule per outcome decides what happens next: no answer, busy and voicemail each get their own delay before the next attempt, up to the attempt limit that campaign is given. A daily and a weekly cap on attempts keeps a single number from being dialed too often in a short time.
When a customer names a preferred time on the call, the agent sets that as the next call time, still inside the campaign's calling window. A do-not-call request is honoured immediately: the contact is removed from every campaign, not just the one that reached them.
Upload a contact list as a CSV, or sync it from your CRM through Dring Connect. HubSpot is the documented reference path; Salesforce, Zendesk, Freshdesk, Bitrix24, Zoho, Google Sheets and custom CRM environments are mapped to their real objects and permissions. Contacts are grouped into segments and assigned to one or more campaigns.
Submit context and consent for a callback. Dring AI calls in about two minutes, identifies itself and walks through the panel workflow with your team.