The sentence everyone forgetsnow books itself.
“Try me after three on Thursday.” The caller names a time, the system works out what they meant in their own timezone, checks it is legal to ring then, and books it. Nobody transcribes an intention into a diary.
45
countries with calling hours
20
US states narrowing them
5
reasons to ask a human
“Try me after three on Thursday.”
- Parsed intentweekday reference + clock time
- Caller timezoneEurope/London
- Weekend checkThursday, no roll needed
- Calling hoursUnited Kingdom, 8:00 to 21:00
- Number checked+44 7700 900244, valid E.164
They told you exactly when to ring. Nobody wrote it down.
A caller naming a time is the strongest buying signal on the phone, and the easiest thing in the business to lose. It survives one busy afternoon only if something other than a person is holding it.
The model describes.The rules do the arithmetic.
Turning a phrase into a moment is done deliberately by rules, because date arithmetic is not something a language model should be trusted with. The model's job stops at saying what the caller expressed.
| What they say | How it resolves |
|---|---|
| "in two hours", "in fifteen minutes" | A duration measured from now. |
| "tomorrow", "Friday", "next week" | A calendar reference, read against the caller’s own timezone. |
| "the 15th" | An explicit date. |
| "later this afternoon", "tonight" | A daypart, resolved to a representative hour. |
| No time at all | Falls back to 11am rather than inventing precision nobody offered. |
Booked, held, or ignored.
Competitors present callback automation as binary: it worked, or it did not. The middle row is what makes it safe to leave running.
Having a real "I am not sure, a person should look at this" path, with five specific reasons rather than one vague one, is the difference between automation you supervise and automation you can leave alone. A system with only two outcomes has to guess, and it will guess on the calls that matter.
A Saturday you asked foris not a Saturday it chose.
If a caller says tomorrow and tomorrow is Saturday, the callback rolls to Monday. If a caller explicitly names Saturday, it is honoured. The system distinguishes a weekend that arrived by accident from a weekend somebody actually requested.
It is a small rule and it exists for an unglamorous reason: ringing a stranger on a Saturday they never requested is exactly how a good lead turns into a complaint.
Calling hours across 45 markets.
For each market the platform records the permitted window, the legal basis behind it, and the consent regime. Pick a market to see all three.
The finding that shaped the design: most countries have no telemarketing specific calling hours statute at all. Rather than invent a window or pretend the question had never been asked, "researched, and no statute fixes hours" is recorded as its own distinct answer, and those markets default conservatively. Where a US state narrows the federal window, the tighter of the two wins.
We do not claim blanket global compliance, because that claim would throw away the thing that makes this credible. What the system can do is tell you the legal basis for its window in a given country, and tell you honestly where no statute exists. Calling rules change, so treat this as our working reference rather than as legal advice for your business.
Three things it refuses to do.
Each of these exists because of something that actually happens on phone calls, not because of a tidy specification somebody wrote in advance.
The number has to be real
Extracted numbers are validated to E.164 length and rejected if they contain letters. This rule exists because a caller once answered "this one’s fine" and the words were very nearly booked as a phone number.
Suppression is respected
A number carrying a do not call or dead line disposition is never scheduled, however the callback was worded.
Past times are refused
A time that has already gone is sent for review rather than quietly rolled forward to a day nobody agreed to.
And then it starts again.
Where a callback schedules automatically, the loop closes without a person at any point. The callback the agent makes is itself transcribed, dispositioned and analysed, which feeds the same cycle.
What stops getting lost.
No callback forgotten
Captured out of the conversation itself, rather than out of somebody’s memory at the end of a shift.
Right time, right zone
Resolved against the caller’s local clock, not against whatever the office clock says.
Ambiguity goes to a human
Five specific reasons send a request to a person instead of booking a guess.
Legal where you dial
Calling hours enforced per market, each with the legal basis it rests on recorded alongside it.
What people ask about automated callbacks.
Yes. When a caller says "try me after three on Thursday", the request is extracted from the conversation, resolved to a real moment in the caller’s own timezone, checked against the calling hours for their market, and queued. The agent then dials at the appointed time, and that call is transcribed, dispositioned and analysed like any other. Nobody transcribes an intention into a diary at any point.
They told you when to ring.Now something remembers.
A short demo on the markets you dial into. We will walk through the calling hours for yours and show you what happens to an ambiguous request.
Book a demo- 01Voice AI Security Compliance ChecklistEssential security and compliance requirements for voice AI platforms. Protect customer data, meet regulatory demands, and audit vendor safeguards effectively.Business Operations
- 02How to Test AssemblyAI for Call Center ComplianceA practical checklist for testing AI voice compliance. Learn what to measure in week one, which vendor questions matter, and when to walk away.Business Operations
- 03Callback Automation AI Cost BreakdownWhat callback automation AI actually costs: per-call pricing, setup fees, hidden expenses, and a worked example showing total cost of ownership for a 50-person operation.Voice AI