Dramatization · AI-generated · fictional scenario
WerkScan for Dutch SMEs
Available now: WerkScan and interactive browser demonstration · Live phone automation is available only in a controlled pilot after written scope, testing and acceptance.
Werkborg maps one customer-contact workflow: the questions AI may handle, the point where a person takes over, and the systems a controlled pilot would need.
Every sector below has a written example flow: what the agent may answer from, what it may never decide, and the colleague it hands the call to. Pick the one that looks like your phone.
Explore industries
Healthcare & clinicsAppointment booking
Dental practicesAppointment booking
LegalLead qualification
Real estateViewing requests
AutomotiveService booking
HospitalityReservations
LogisticsOrder status
Home servicesEmergency dispatchDramatization · AI-generated · fictional scenario
Six steps, written down with you before the agent takes a single call. The fifth one is why the other five can be trusted.
Design and evidence phase · the inbound leg is not live yet · no availability promise
Your number and your telephony provider stay exactly where they are. Werkborg is designed to sit behind them over SIP.
The first sentence of every call states that the caller is speaking to an AI assistant, not a colleague.
No menu and no keypresses. The caller says why they rang and the agent works from that.
Checks what is free, writes the record, drafts the follow-up message — inside the systems you already run.
A price, a promise or a judgement it was never given: the agent says so and stops, instead of inventing a confident answer.
The call moves to a person with the reason, the details and the transcript already collected.
Two of them are what most callers meet today. The third is what Werkborg is being built to be — and the difference is not the voice, it is what happens when the caller says something the line did not expect.
| Common todayKeypress IVR menu | Common todayScripted voice bot | The Werkborg wayAI phone employee | |
|---|---|---|---|
| How the caller starts | Presses numbers through a fixed tree | Says one of a short list of intents it was trained on | Says why they rang, in their own words |
| When the caller goes off-script | Loops back to the menu, or waits | Fails, and the caller starts again | Asks what it still needs, confirms what it heard |
| What it takes to set up | A menu tree, and a recording per branch | A long, rigid configuration before launch | A written call flow: what it may answer, what it may never decide |
| What happens after the call | Nothing — the caller was routed, not heard | Inbound routing only, no follow-up and no context | A summary, a record, and the follow-up message drafted |
Werkborg is pre-launch, so none of these is a customer. They are the worked examples we write with a business before the agent takes a call: the beats of one shift, and the line where the agent hands over.
Discuss your workflowReception is still unlocking the doors. The line is already open, the caller wants a slot this week, and the agent works through the practitioners in order until it finds one.
The office closed six hours ago. The agent asks the three questions that decide whether this waits until morning, and pages the on-call engineer only when the answers say so.
A first-time caller with a case the firm may not be able to take. The agent captures the facts, runs the conflict check, and proposes a time with the partner who handles that work.
A conversation, not a menu.
The caller says why they rang. The agent asks what it still needs, confirms what it heard, and stops where it was told to stop.
Speech, understanding and telephony orchestrated so a call feels like a conversation, not a query
Outside opening hours, during peaks and when the team is already on another call, the line is not left ringing.
Dutch, English, German, French and more, chosen per caller or per number.
Handles interruptions, pauses and thinking-out-loud without talking over the caller.
WERKBORG / AGENT STUDIO
Your flow. Your knowledge. Your control.
Build the conversation step by step — greeting, questions, conditions, escalation — with guardrails on what the agent may promise.
Illustrative workflow — pilot configuration is agreed separately.
Approve the actions and handover rules before a controlled pilot.
Illustrative workflow — pilot configuration is agreed separately.
Choose the approved sources for each answer. Unknown questions go to a person.
Illustrative workflow — pilot configuration is agreed separately.
Run the agent through your own scenarios — awkward callers, missing data, background noise — and see the outcome before a customer hears it.
Transcripts and summaries for all calls, so quality review covers the whole line instead of a hand-picked sample.
Group calls by reason, outcome, language and hand-off so you can act on the questions that keep coming back.
Planned for a controlled pilot after the number routing, disclosure, handover and acceptance tests are complete.
Reminders, confirmations and follow-ups placed on your behalf, with consent respected.
The confirmation or the link goes out right after the call, so nothing depends on anyone remembering.
Trigger calls and receive structured results in the systems your team already uses.
Callers keep dialling the number on your door and your invoices; Werkborg answers behind it.
Werkborg is designed to sit alongside your existing telephony provider over SIP, so nothing has to be replaced first.
Route calls to Werkborg only when the team is busy, closed or on the road — or let it take the whole line.
Define exactly when a call goes to a person: urgency, subject, caller request or a failed answer.
Werkborg is being built for Dutch and European organisations: data minimisation by default, clear retention settings and a written record of what the agent did on every call.
Only the data your call flow needs is collected, with a documented purpose per field. Formal certifications are not claimed until they are audited.
Named accounts per colleague, with roles that decide who can hear recordings and who can change a flow.
Mask personal details in transcripts and summaries, per field, so support staff see only what they need.
Decide how long audio, transcripts and summaries are kept, and have them deleted automatically afterwards.
The agent states that it is an AI assistant and asks for consent where recording requires it.
We map your call flow with you, test it against your own scenarios and stay involved after the first live shift.
Werkborg is designed to run on European infrastructure; the current hosting region is documented per deployment.
Werkborg is built to work through the APIs and webhooks your calendar, CRM and telephony already expose.
No connection is listed here as live. Which ones are in place is confirmed per deployment, in writing, before the agent uses them.
Discuss your stackAn AI phone agent is software that answers or places phone calls on behalf of a business. It listens, understands what the caller wants, answers questions, performs actions such as booking an appointment, and hands the call to a colleague when that is the right outcome. Werkborg calls them phone employees because they work a shift on your line rather than replacing your team.
Answer inbound calls, place outbound calls, answer customer questions, create or move appointments, qualify leads, collect structured customer information, transfer to a colleague when appropriate, and produce a summary of the conversation afterwards.
Werkborg is built multilingual, with Dutch and English first and further European languages per agent. The language can follow the number that was dialled or switch when the caller does.
Yes. Werkborg is designed to sit behind your current number and telephony provider over SIP, so you can route the whole line, only out-of-hours traffic, or just the overflow to the agent.
Whenever your rules say so: an urgent subject, an explicit request for a colleague, a question the agent cannot answer from your material, or a step you decided a human must own. The colleague receives the context that was already collected.
Werkborg is built to work with the calendar, CRM and business systems you already use, through their APIs or webhooks. We confirm per deployment which connections are in place — we do not list integrations that are not live.
No. It takes the repetitive, high-volume part of the line — opening hours questions, appointments, order status, qualification — so your team can spend its time on conversations that need judgement.
An IVR asks the caller to press numbers and follow a fixed tree. A Werkborg agent lets the caller explain the reason for calling in their own words, answers or acts immediately, and routes the rest without a menu.
You decide what is stored and for how long. Werkborg is built for data minimisation: only the fields your call flow needs, with configurable retention and redaction of personal details in transcripts.
No. The demo is a demonstration interface. It does not place telephone calls and cannot be relied upon as a service. A live workflow is considered only after a written scope, testing and acceptance for that specific pilot.
Organisations with real phone traffic and appointment-driven work: clinics and dental practices, law firms, estate agents, automotive businesses, hotels and restaurants, logistics, technical and home services, and small businesses whose phone rings more often than they can answer.
Try the interactive browser demonstration, then start a WerkScan. We map your current call flow, agree what a controlled pilot may do and what always goes to a person, and test it against your own scenarios before any live call is considered.
