Separate the request
Routine maintenance follows a different approved flow from a current breakdown or emergency.
Synthetic appointment-booking example
The fictional call shows a deliberately bounded booking flow. Griffi asks whether this is routine maintenance or a breakdown, offers only suitable free slots and records the callback number and outcome.
Review your booking flowFictional, synthetically generated example call. Not a real customer statement.
Griffi: Good morning, Green and Sons Heating. This is Griffi, our digital assistant. How can I help?
Caller: Good morning, this is Mister Brown. I would like to book the annual service for my boiler, preferably next week.
Griffi: Is this routine maintenance only, or has the boiler currently broken down?
Caller: Routine maintenance only. The heating is working normally.
Griffi: I can offer Tuesday at nine or Thursday at two in the afternoon. Which works better?
Caller: Thursday at two works. My callback number is zero one seven one, two three four five six seven eight.
Griffi: Thank you. The service is booked for Thursday at two. The company will see your callback number and that there is no breakdown.
Routine maintenance follows a different approved flow from a current breakdown or emergency.
Griffi uses the categories, durations and availability approved by the company.
The appointment, contact details and no-breakdown note remain traceable in the case.
Recorded, not forgotten
Whether routine maintenance or a current breakdown — the classification opens the case.
Name and callback number for confirmation and questions.
Category, duration and time of the confirmed appointment — only from approved availability.
Confirmation, notes such as “no breakdown” and open next steps remain traceable.
Clear boundaries
The flow shown runs on the AI Phone module (€89 net per month) in addition to an n3tz base plan; it is already included in Premium. Rules, follow-up questions and handover paths are defined during setup.
All amounts are net plus statutory VAT. Full base plans, limits and billing detail are on the pricing page.
No. Only free slots from the approved categories, durations and availability are offered. If nothing fits, a traceable case or callback request is created instead of an invented promise.
Through the follow-up questions your company defines during setup. A current breakdown follows the emergency-service rule; planned maintenance follows the appointment flow.
From the calendar connected during setup and the approved time windows. Which calendar connection fits is reviewed during setup — there is no blanket promise for every system.
The appointment is written to the calendar and documented in the case. Configured SMS reminders — for example 24 and 2 hours beforehand — run automatically under the configured rules.
Yes, but not without proof. Griffi sends a code by SMS to the stored number. Only after correct confirmation does Griffi show, move or cancel the appointment.
Griffi offers the waiting list and records the name, contact and preferred day in the case. If a service area is stored, the postcode is also asked before booking.
It says openly that it is not sure, forwards the question to your team and confirms that someone will get back. Opening hours, prices or guarantees that are not stored are never invented.
Bring your current scheduling rules — together we review which steps Griffi takes over and where your team decides.