Step 1: count your calls for a week
Before configuring anything, measure. For five working days, note every call: the time, the reason, whether it was answered or missed, and whether it led anywhere. A sheet of paper next to the phone is enough. By the end of the week, you will know three things most businesses don't: how many calls you miss, at what times, and for what reasons. Those are the calls the agent will take first.
Step 2: gather your information
The agent only answers from what you give it. Prepare, in a simple document:
- your opening hours, closing days and holidays;
- your services, with their duration and, if you want the agent to quote them, their prices;
- your address, directions, parking;
- the five to ten questions you get asked all the time, and your answers;
- who does what in the team, and who should receive which type of request.
If you have an up-to-date website, a good part of this information is already there.
Step 3: set your rules
This is the first of the two steps that deserve time. For each type of request identified in step 1, decide:
- What the agent answers itself. Opening hours, services, procedure.
- What it notes for a call-back. And what information it must collect: name, number, vehicle, address, reason.
- What it transfers, and to whom. Define your emergencies in your own words ("water leak", "severe pain", "summons tomorrow") and the number to call, by day and by night.
- What it must never do. Quote an unapproved price, give an opinion, promise a deadline, disclose information about a file.
These rules fit on one page. They matter more than any technical setting.
Step 4: describe your business, AI generates a first agent
With Driing, you describe your business in a few sentences, as you would to a new recruit. From this, AI produces a first agent: a greeting in the company's name, answers to common questions, a flow for the main requests. This first draft is a working basis, not a final result. Read it through with your step 3 rules in front of you.
Step 5: adjust the flow in the editor
The visual editor shows the call as a diagram: greeting, reason, questions, action, wrap-up. Change the wording so it sounds like you, add the questions to ask, place the transfer rules. Two tips:
- Start with the three most frequent reasons for calling. The rest can wait until the second week.
- Write short. On the phone, a two-sentence answer beats a paragraph.
Step 6: test by calling your agent
This is the second step that deserves time. Call your agent the way your customers would, with a list of scenarios: a simple appointment, a question you know it can't answer, an emergency, a hurried caller who interrupts, a call in German. Have a colleague who wasn't involved in the set-up test it too. Note what doesn't sound right, fix it, call again. Three or four rounds are usually enough.
Check in particular that transfers go to the right numbers, and that the call summary contains what your team needs.
Step 7: forward your calls and brief the team
You keep your number. From your current line, set up call forwarding to the agent, using one of three options:
- Out of hours only. The most cautious option to start with: the agent replaces the voicemail in the evening and at the weekend.
- Overflow. The agent takes the call when the line is busy or after a certain number of rings.
- All calls. The agent answers first and transfers whatever needs transferring.
Brief your team: explain what the agent does, where the summaries arrive and who deals with them. Mention the agent in your privacy policy. During the Driing beta, we support you through each of these steps.
After going live
Read the call summaries every day for the first week, then every week. You will quickly spot the questions the agent can't answer: add the answers. You will also see the requests you hadn't anticipated: add a flow. A voice agent is never "finished": it improves as you feed it, and you are the one holding the spoon.