Leave one workflow and your number. The AI identifies itself, asks a few focused questions and prepares a structured brief.
Prompts, voices, phone numbers, campaigns, tools, after-call workflows, users and keys sit in one operational view. Your team and your partners manage what they own, and any change to how an agent talks or acts is tested before it goes live.
Submit the workflow your team wants to improve and DRING calls you in two minutes to shape the right project with you. See the callback flow.
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 behavior 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 calling days and windows, retry delays, do-not-call marking and SIP rules. Start, pause and monitor from the same screen. Campaign rules below.
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. Contact lists below.
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. See in-call actions.
What happens once the call ends: analysis fields, then CRM updates, webhooks and team alerts, each step with its own outcome condition: green, yellow or red. See after-call workflows.
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.
Changes to how an agent talks or acts do not go live on save. Prompt edits and new in-call actions enter the same release pipeline: the test suite runs, the release criteria are checked, and the change goes live in stages.
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. Your invoice is built on the same numbers, so you can check it line by line.
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 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 is scoped separately when the partner model needs one.
The catalog holds tested templates by use case: order status, appointment booking, collections, qualification and more. From the panel, pick one or start from a blank agent, then adapt the opening line, prompt, voice and tool access to your brand and policies.
The calling window, call days, retry delays and attempt caps sit on the campaign screen, next to start and pause. Reach then works the list inside them.
An operator sets the window and the days a campaign may 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 keep one number from being dialed too often in a short time.
When a customer names a preferred time on the call, the agent sets it as the next call time, still inside the campaign's window. A do-not-call request is honored immediately: the contact leaves every campaign, not just the one that reached them.
Upload a contact list as a CSV, or sync it from your CRM through 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.
Send the form and DRING calls you in two minutes, says it is an AI and asks about your workflow. The team then follows up to show you the panel.