Counted by the second
Usage is measured in seconds, not rounded-up minutes. A very short call rounds up to the agreed minimum.
Leave one workflow and your number. The AI identifies itself, asks a few focused questions and prepares a structured brief.
DRING covers nights, weekends and holidays. It confirms and reschedules on the call, sends exceptions to whoever is on duty and leaves the morning handover written.
After you submit the form, DRING calls in two minutes, identifies itself and qualifies the workflow.
Up to 81%: selected deployments, not a guaranteed saving. The other three: platform-wide.
Out-of-hours cover usually means an on-call phone, a voicemail box and a Monday catch-up. Each one leaks somewhere.
The line rings long after the shift ended. Whoever was calling hangs up and tries a competitor in the morning.
Nobody had time to call ahead before the office closed. The van, the room or the engineer is held for a customer who never turns up.
Monday starts by asking three people what happened. The parts nobody remembers are simply lost.
What happens to a call at 02:19, from the first ring to the note your team reads at seven.
Nights, weekends and public holidays are covered by the same agent, with no shift schedule to fill.
Confirmations, reschedules and status questions finish on the call, without a person on shift.
Anything the agent should not decide goes to the owner you set for that call type, with the summary, the reason and the next step.
Every call the night took is listed by outcome before your first person sits down.
The same agent answers for each site, so a call to the quiet depot is handled exactly like a call to the busy one.
Before launch you set, per call type, what the agent settles alone and where the rest goes at each hour. Each exception starts its SLA clock with an owner attached.
| Call at night | What the agent does | Where it lands |
|---|---|---|
| Delivery slot check | Confirms the slot, or moves it to a free one | Closed on the call |
| Reschedule request | Offers the open slots and books the new one | Closed on the call |
| Damaged goods report | Takes the order, the damage and a callback number | Ticket for the morning team, alert to the duty manager |
| Urgent site issue | Checks it against your urgency rules | Live transfer to the on-call number |
| Complaint about a delivery | Records it in the customer's own words | Case in your CRM for customer care |
Each call leaves the same record, with the summary, reason tags, sentiment and next action, in your CRM, a ticket or a webhook within seconds of hang-up.
One screen holds the whole night: what was answered, what closed on the call and what is waiting for a person.
Illustrative panel view. The figures on your screen come from your own lines.
Cover is billed on usage, not on shifts. Three rules decide what a quiet night and a busy one cost.
Usage is measured in seconds, not rounded-up minutes. A very short call rounds up to the agreed minimum.
Usage above your package is billed at the package's own unit rate, so a busy night costs the same per unit as a quiet one.
The saving is worked out against a human-only baseline agreed with you, so the comparison uses your own cost per contact.
Drivers call about open loads, rates and their profile whenever they are on the road. Calls after the office closed went unanswered, so no one logged them or could size that demand.
One inbound line answers every driver instantly, at any hour, with no queue. It works from the live load and rate data, captures profile details on the call, and passes rate negotiations to the team with the driver's context already written.
The after-hours calls are now answered and recorded, so the team can see when drivers actually call and plan the follow-up around it. Cover no longer depends on who is willing to keep a phone by the bed.
It does not sit until someone opens the inbox. If the case cannot wait, the call transfers to whoever you have on call, and that person sees the summary and the reason before picking up. If it can wait, the agent tells the caller what happens next. The outcome record then fires the rule you set for that call type: a ticket, a callback booked for the morning or an alert to the right team.
You do. Before launch, your team and DRING list the call types, what the agent may settle alone and what goes to a person, with the destination for each hour. The list lives in the agent's rules, and a change goes through a tested update before it reaches the line.
Yes, as long as the sites follow one process. The details each site needs, such as its hours, its address and who is on call, sit in the agent's knowledge and routing rules. An extra field on the outcome record can carry the site, so reporting splits by location. A site that works in a genuinely different way gets its own agent instead.
Yes, where the sites follow the same process. 62 languages are available and 10 are live today; yours is validated before launch. Each country's hours, holidays and on-call contacts sit in the agent's routing rules.